You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at bikedata.cyclestreets.net, it seems that this is a TFL data issue, not necessarily an import issue (although maybe checks could be added for traffic humps on main roads). It may be a duplicate of RWG183017 to the NE?
update:
removed it in case it messes up routing, ideally it would be re-added at the correct location
The text was updated successfully, but these errors were encountered:
https://www.openstreetmap.org/node/10275696019 traffic hump RWG183005 definitely doesn't exist at this location (on a main road).
Looking at bikedata.cyclestreets.net, it seems that this is a TFL data issue, not necessarily an import issue (although maybe checks could be added for traffic humps on main roads). It may be a duplicate of RWG183017 to the NE?
update:
removed it in case it messes up routing, ideally it would be re-added at the correct location
The text was updated successfully, but these errors were encountered: