Part of PR 307 crossing the Whiteshell River (White Lake) is rendering as a thin line (trail?) instead of a green road. This is happening in multiple locations. Whiteshell Provincial Park, Manitoba, Canada. I’m using Mapuploader to create my maps. Using iD editor the lines are tagged highway=secondary. The section in question also has Bicycle Route (North Whiteshell Trail), Hiking Route (North Whiteshell Trail), Road Route (PR 307) and Road Route (La Verendrye Trail) under Relations. I have not done any of the mapping / tagging in this area. Vehicle routing along PR 307 does not work. The North Whiteshell Trail, La Verendrye Trail and PR307 are all tagged under one line. Is this correct or should should there be 3 seperate lines? Thanks.
I don’t know the answer but for others looking at this, this seems to be at 50.0552,-95.5171 : OpenStreetMap
What tool are you using for the routing, and what start and end positions? Because it seems to work in the routers integrated in openstreetmap.org, for example https://www.openstreetmap.org/directions?engine=graphhopper_car&route=50.03683%2C-95.49857%3B50.06898%2C-95.59547
1 Like
Your co-ordinates are correct for my example. Same situation at N50.14202° W95.68811°, N50.06727° W95.57333°, N50.03403° W95.50838°, N49.74644° W95.21677°
Raw data from geofabrik…Mapuploader to create img file…add to Basecamp. Using Mkgmap default style. Garmin Basecamp for routing. Basecamp creates Direst route instead of vehicle route between start and end positions.
Start Position: N49.74612° W95.21544°
End Position: N50.17186° W95.69781°
I have added Garmin and Mkgmap tags to this thread so hopefully more people familiar with those can see it.
(It wasn’t really obvious from your initial message text that that’s what you’re asking about, except for people familiar with the screenshot style, but they would have to find and open the message to see the screenshot.)
1 Like
Based on the examples, it certainly seems to be the case that whenever a hiking route relation is present, Mapuploader generates a hiking trail instead of a road.
I would guess that this caused by a limitation of the Garmin map format to support routes, so the OSM data for roads and routes need to be flattened into one entity, and the fact that almost all other “roads” (highway=path, highway=trail, etc) with hiking routes are flattened to hiking trails, so that’s potentially how the authors of Mapuploader built their logic – which would probably be too simplistic.
The only counter-point to this guesswork of mine is that a small segment in the hiking route relation is depicted as a road on the Garmin map. I can’t explain why this breaks the pattern.
If my guess is somewhere near the truth, the issue would need to be raised with the Mapuploader publishers to have them correct the way OSM data is interpreted.