|
While trying to navigate by car to Tenaya Lodge, California (https://www.openstreetmap.org/#map=18/37.47295/-119.63505), I experienced route calculation errors both when navigating to the Lodge, and when planning a route away from it while sitting in one of the Lodge rooms. I think I have traced the problem to the short closed way representing the paving around the outside swimming pool. The router has to move the start or end of the proposed route on to a mapped road, and it seems that the router on my Garmin Etrex-30 was choosing the swimming pool paving as the nearest road, and then failing to find any connecting roads. Navigating to Tenaya was achieved by moving the destination point to one of the service roads; navigating away was achieved by standing outside. I would welcome advice on the best way to eliminate this problem. The simplest solution would be to delete the path surrounding the pool, leaving just the water mapped, but I am reluctant to delete another mapper's work if anyone can suggest a better method. |
|
The best solution is to add a footway connection between the pedestrian area around the pool and the nearby service road. This way you can navigate from and to the pool without problems. Are you familiar with this location? On aerial imagery it looks like there is a footway to the west of the pool. I have been there for two nights; that's all. The pool and the surrounding area are separated from the service roads by a metal fence, with some lockable pedestrian gates to the roads. I don't remember the full path layout or the exact line of the fence, but I think I have enough information to implement your suggestion, and no doubt another mapper could improve on my efforts.
(13 Jun '19, 10:29)
Madryn
1
I have connected the path surrounding the pool to the main road system, and made it clear that both are footpaths only.
(17 Jun '19, 19:06)
Madryn
Unless I miss something the path has been a footway for the past five years. So while this solution might fix the current routing issues I find it worthwhile also notifying the router manufacturer. Firstly they shouldn't route on a footway if in car mode and secondly they should exclude small routing islands like this path from the routing graph. There's also still something odd about the changes you made. You created a relation for the paved area but missed adding the pool as an inner way. If you have the relation you could also remove the highway tag from the outer way (unless you left it there as a safeguard for routers not understanding relations or areas).
(18 Jun '19, 09:22)
TZorn
It is not necessary to create a relation to fix this routing error. Just add a footway from the road to the pedestrian area. There is no need to add another footway around the pedestrian area either.
(18 Jun '19, 09:26)
scai ♦
I did not deliberately create a relation, neither did I deliberately remove one. If I remember correctly, ID showed the path around the pool as some sort of highway. Thinking that I had found the problem, I tried to change it to a footpath. Clearly that has not had the desired effect, or has had unwanted side effects. Perhaps someone could revert my changes in this area, so that I can attempt to make the minimum necessary change (a short footpath link from the pool surround to the road system)? I do not know how to do that myself. As regards telling the router manufacturer, I was using an Etrex 30, which I suspect Garmin would no longer be interested in updating, as it is quite an old model.
(21 Jun '19, 19:39)
Madryn
I removed the relation. One could have left it in there and added the pool as an inner member but the aerial imagery I found was not good enough for me to really judge the correct extend on the ground. It appears to me that there are additional pools and multiple ways. So I just left it with the simple way around the pool. Additionally, I removed the descriptive names from the pool and the main access road.
(24 Jun '19, 08:49)
TZorn
showing 5 of 6
show 1 more comments
|
