Posts for this topic...
-
Post your comments.... Sign In to Post
-
Stephen R Thursday 07 Mar 2024 23:16:56
I left a comment on the changeset that added the locked gate, the OSM contributor who added it has now changed the path to show you can walk past the gate. Presumably at some point PAR will pick up the change. Still no idea on the other problem area from my second comment.
-
Stephen R Wednesday 06 Mar 2024 20:02:29
Thanks for the links Mark.
Regarding the first area with the three-way path, checking OSM I can see that there's a locked gate next to the junction so I assume that's the problem with routing. Without being in the area I don't know whether that's accurate or not (hopefully not since the Weavers' Way passes over that path).
Regarding the second area with the unroutable path, checking OSM that path is specified as access=yes and highway=bridleway so I see no obvious reason why PAR refuses to use it unless it's working with a different set of data (that path hasn't been edited for 7 years so it seems unlikely). Maybe a bug in PAR or perhaps I'm missing something.
-
Mark Worthington Tuesday 05 Mar 2024 21:22:28
Yes, these are generally errors in the underlying OSM database ....
A local workaround are easy to do, just simply turn Auto-Plot off and select the footpath of interest then turn Auto-Plot back on.
See Auto-Plot Access across Car Park areas "and
How To Make Changes to OpenStreetMap Maps
Hope this helps -
Stephen R Tuesday 05 Mar 2024 13:02:33
I found another path that can't be routed over and this time it's not where two paths meet so perhaps that's not the issue? There's a byway at UK grid ref TL 5848 6748, clicking on it with Auto Pilot enabled will never place the marker on the actual path only on nearby roads. It's the dashed green path shown below:
-
Stephen R Tuesday 05 Mar 2024 10:05:53
Occasionaly I find a place on the map where two paths meet that PAR refuses to route across. An example I just found is at UK grid ref TG 3064 2749, there's a 3-way junction that cannot be routed over:
Is this an error with the OSM data that I could potentially fix (if so how would I do that, I have no experience editing OSM), or is it a problem with PAR?
- 1
