Closed hoream-telenav closed 6 years ago
From @jothirnadh on November 6, 2017 5:11
Data team at Mapbox also gone through this issue while trying to improve navigation data in OpenStreetMap. I did some research on the reason for causing this issue and wrote a diary post on this. Would be great to know your views as well in this case.
This is where we tracked our Portland transit lane relation breakage issue for further reference.
From @mihaii-telenav on December 7, 2017 9:0
We've extracted all the bus routes using this overpass query and we ran then through the Relation Analyzer and we proceeded to fix the ones that are broken. Here's an overview of the ones we found to be broken and were fixed.
Bus relations (the changesets mentioned below are the ones that completed the editing process on the relation):
2 bus relations were skipped because the route was going through a construction zone and the community left a comment on the relations.
Bike relations (the changesets mentioned below are the ones that completed the editing process on the relation):
4 bike relations were skipped because there wasn't enough information to update them. In order to be updated, local knowledge is the best option.
I've sent a message to Greg to ask for further info regarding the relations that we've skipped.
From @drkludge on December 10, 2017 20:51
Here are some random observations.
4499233 512829821 W forward 360
4499233 241138363 W forward 361
4499233 527586905 W forward 362
4499233 436944787 W forward 363
4499233 408592759 W forward 364
4499233 436944788 W forward 365
4499233 408813167 W forward 366
4499233 408813155 W forward 367
4499233 408592761 W forward 368
I used either a vim regex pattern that transformed the Osmosis relation members back into an .osm file format or removed the role name if the route was mostly intact.
:'a,'b s/^\([0-9]*\)^I\([0-9]*\)^I\(.\)^I\(.*\)^I.*$/ <member type='way' ref=
'\2' role='' \/>/
The ^I
is a tab character.
The 'a
and 'b
are vim range markers. The markers were required to carefully make the changes in the selected area of the .osm file.
:'a,'b s/'backward'/''/
Note that you also have to make a change to the route in Josm before saving the file or add action='modify'
to the relation tag.
<relation id='4498932' action='modify' timestamp='2017-11-21T14:54:06Z' ...
Greg from Phoenix got in touch through email and OSM message about broken transit relations in Phoenix caused by our road edits. This ticket tracks the fixing effort.
List of all bus relations in Arizona (not all are in Phoenix)
Spreadsheet with OSM Relation Analyzer links
OSMI link