false positive on mapillary image detector - cycle infrastructure is tagged already #1011
Comments
matkoniecz
changed the title
|
Does |
Yes |
|
I would add values Also, I would recommend this as the image processing is quite poor and catches also cycleway signs denoting lanes (and white text on blue shops signs and logos of motorway payment scheme in Poland - but that is harder to avoid false positives in such cases :) ) |
|
Ehm, may I vote against this? Lane is significantly different from tracks, to my knowledge not signposted normally. The sign pictured seems to be a clear false positive detection of Mapillary. (Same as oneway tags aren't indicating cycling infrastructure, but detecting them as such will miss actual missing cycling tracks) (Also, cycleway:left/right=opposite_* has no meaning) |
|
It might be more convenient to teach Mapillary about those False Positives. Did something similar for NL a while ago. |
|
I prefer avoiding false positives by making more matching than necessary. It also should be tolerant to alternative and old mapping rules (like cycleway:left/right=opposite_*). |
|
Perhaps it's possible to exclude a.o. The Netherlands from these oneway exceptions then? Almost all our residential roads have oneway-exclusions, and since these connect to the roads with bicycle tracks... Or, perhaps a better idea: make the less-strict one for level "medium" and the more strict (current) one for level "low" |
* frodrigo/master: Add public jupyter setup Review docker volumes Switch Docker to Postgres 13 and PostGIS 3.0 Fix docker-compose.yml for osmose container Add default Jupyter config Update JOSM MapCSS #1013 Update to new data in analyser_merge_public_equipment_FR_toulouse_toilets Update data definition in analyser_merge_parking_FR_bm Update data definition in analyser_merge_street_number_bordeaux Fix Administrative_INSEE_Name.py init for new sax plugin load Init plugins from constructor Remove unused pugin.end() Revert 'Remove plugins load from __enter__' Withelist from landuse=water to natual=water #265 More cycle infrastructure in mapillary-traffic-signs.mapping.json #1011 value_replace also for array in analyser_merge_traffic_signs
|
http://osmose.openstreetmap.fr/en/errors/?item=8470 |
|
Including highway=* + bicycle=designated results in not showing erroneus tagging: highway=footway + bicycle=designated (this combination is not treated as cycleway in most routing engines |
|
@masterofnoroad bad tag combination should be deal in other analyser, like this one |
|
Note https://josm.openstreetmap.de/ticket/17901 https://josm.openstreetmap.de/ticket/9250 and related issues and commits. JOSM started to complain about |
http://osmose.openstreetmap.fr/pl/error/90514ca3-8c94-2d44-ba19-d4ce5392b0a5
OSM way with
cycleway:left=opposite_laneandoneway:bicycle=nohttps://www.openstreetmap.org/way/25367091The text was updated successfully, but these errors were encountered: