oneway:bicycle=yes seems not to be digested
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Radkarte |
Fix Released
|
High
|
luckyguess |
Bug Description
From what I saw in the code I assume that oneway:bicycle=yes seems not to be digested yet.
This affects my Garmin Oregon using http://
Some time ago a contributor mass edited combined foot/cycleways in Munich by exchanging all oneway=* with bicycle:oneway=* (assuming that oneway=* also affects routing for pedestrians...). That broke routing in that area for me and I discovered the mistankenly used bicycle:oneway=* instead of oneway:bicycle=*.
After those tags were fixed routing still broke on formerly working routes:
- when calculating a ~12 km long route from e.g. 48.1182,11.4444 to 48.1631,11.5688 my Garmin now reports a route calculation error, in both directions.
- I also observed strange micro-routing while on a way which was calculated properly before that mass edit, e.g. my Garmin asked me to take the cycleway on the left side of the road which I knew had an information tagged to route 'oneway'.
I tested this latter region by adding oneway=yes to the existing oneway:bicycle=yes and discovered that now routing worked again properly in that area. I can provide links to some example changesets if necessary.
Cheers,
Carl
Thanks for the hint, a small patch is already committed and I will create a new set of map files in the next hours.