osmose-backend icon indicating copy to clipboard operation
osmose-backend copied to clipboard

Part of osmose that runs the analysis, and send the results to the frontend.

Results 260 osmose-backend issues
Sort by recently updated
recently updated
newest added

I got a bunch of level 1 errors recently - https://github.com/osm-fr/osmose-backend/blob/34efa0287acfea481d36bf34452cf6662a3f5349/plugins/TagFix_MultipleTag.py#L42 The table here https://wiki.openstreetmap.org/wiki/Key:fence_type recommends it the other way around, or rather, if I understand correctly, fence_type and material...

Downloading data from mapillary for analysers to merge objects/street signs takes excessively long. For example china_heilongjiang fetches over 170.000 tiles for each analyser. Tibet 250k. Even with 4-5 requests per...

The analyser `analyser_merge_public_transport_FR_stif` is no more working because the data source is no more available at https://data.iledefrance-mobilites.fr/explore/dataset/referentiel-arret-tc-idf/information/?sort=fichier @nlehuby there is a replacement data source or we need to remove it...

bug
ready
open-data

Would it make sense to rank issues by location? Currently, Osmose has three priority levels for its findings. Of corse, every place is important for _someone,_ but a data problem...

Is it possible to have a validator which checks the correct tagging of crossings? For example in the screenshot below, the node that's on the road should have `highway=crossing +...

enhancement

Some additional keys with the value "yes" should be specified further, changed or removed. Example(s): `location`(, `construction`; deprecated, replace by `construction=minor`, or `construction:*`) ([Browse MapRoulette](https://maproulette.org/browse/challenges?query=%3Dyes)) (Irrelevant: `area`)

enhancement
JOSM MapCSS

_(Incorrect capitalization check may already be implemented)_ ### Fix short keys Example Key “a” (combinations mean “aa”, “ab”, ..) Find suspicious keys (any character(s) + combinations if possible) All optional...

enhancement

Osmose Ref 1 - 9001(3)/9001001 20f90fa3-2f9e-6dee-2b84-d4da0701f533 Details link 1- http://osmose.openstreetmap.fr/en/issue/20f90fa3-2f9e-6dee-2b84-d4da0701f533 Osmose Ref 2 - 2110(2)/21101 873976ad-8dce-10c0-3cc6-a968806d3688 Details link 2 - http://osmose.openstreetmap.fr/en/issue/873976ad-8dce-10c0-3cc6-a968806d3688 Way - https://www.openstreetmap.org/way/1039608533 This is a way that is...

https://osmose.openstreetmap.fr/en/issue/0e751dbe-2f95-6ff7-e6da-b2b18880063d is an "Almost junction" between [W 803435089](https://www.openstreetmap.org/way/803435089) and [N 2195816129](https://www.openstreetmap.org/node/2195816129). However, it can easily be seen that the node is already part of the way, so I see no...

bug
question
osm-data

I would like to add certain cases of [One feature, one OSM element](https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element) to Osmose, related to > An [area](https://wiki.openstreetmap.org/wiki/Area) object with a [point](https://wiki.openstreetmap.org/wiki/Point) object inside, both with the same...

enhancement