<div dir="ltr"><div>Just another idea....</div><div><br></div><div>Is it possible to make the car park a (pseudo) node that is on all the paths that connect to the car park?</div><div><br></div><div>John Thorn<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 28 Jul 2020 at 12:00, <<a href="mailto:mkgmap-dev-request@lists.mkgmap.org.uk">mkgmap-dev-request@lists.mkgmap.org.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send mkgmap-dev mailing list submissions to<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:mkgmap-dev-request@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-request@lists.mkgmap.org.uk</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:mkgmap-dev-owner@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-owner@lists.mkgmap.org.uk</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of mkgmap-dev digest..."<br>
Today's Topics:<br>
<br>
1. Re: default style lines enhancements (Ticker Berkin)<br>
2. Virtual paths (ael)<br>
<br><br><br>---------- Forwarded message ----------<br>From: Ticker Berkin <<a href="mailto:rwb-mkgmap@jagit.co.uk" target="_blank">rwb-mkgmap@jagit.co.uk</a>><br>To: mkgmap development <<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><br>Cc: <br>Bcc: <br>Date: Tue, 28 Jul 2020 10:58:30 +0100<br>Subject: Re: [mkgmap-dev] default style lines enhancements<br>Hi all<br>
<br>
In some major walking areas there are networks of paths with a few car<br>
parks around the edge, normally set 100m or so into the park/woods. The<br>
free maps one can obtain show suggested trails and these trails often<br>
cross multiple car parks. The maps probably don't show a path within<br>
the car park and there is no physical manifestation of it.<br>
<br>
Without "paths around car park", if I try to use my device to generate<br>
a walking route to some feature in the area (or back to the start), it<br>
will probably generate a route that leaves the area, gets onto the<br>
closest road, and re-enters elsewhere. Or it might give a "Route<br>
Calculation Error" because paths closest to the start or end are not<br>
connected to the rest of the network.<br>
<br>
With the data as it stands, for sensible routes in the above situation<br>
and others as expressed in my earlier email, mkgmap needs to generate<br>
footways that join up all ways that lead into the car park with a<br>
footway. With the current technology this can be done with<br>
circumference footway and mkgmap:set_{semi_/un}connected_type provide a<br>
really good way of not doing this where the footway won't solve any<br>
routing issue and might cause routing island problems.<br>
<br>
I wouldn't object if OSM mappers joined all paths and the entrance<br>
road/parking aisles within the car park and maybe there should be a<br>
policy to do this and then there is no problem.<br>
<br>
However, there is a good argument that the correct OSM mapping is to<br>
show paths exactly as they are and not have to invent and add 'virtual'<br>
bits of footpath just to keep routing engines working sensibly because<br>
"mkgmap expects it like that".<br>
<br>
Other things that have been mentioned:<br>
<br>
- What about a path that runs up to or along the side of a car park but<br>
there is no access between them, eg an enclosed car park with a road<br>
along-side. I'd say that this is just incorrect mapping if the car park<br>
shares a node with the road but there is a barrier between.<br>
<br>
- If starting within the car park, the route might tell you to walk<br>
around the edge rather that direct to the highway. Yes and no; it will<br>
plot a route to the closest edge and then to the best exit for the<br>
final destination; It should be obvious to the GPS user that they can<br>
just walk directly to the best exit. Without the change the only option<br>
you might get is onto the road network which could be entirely wrong.<br>
<br>
Ticker<br>
<br>
<br>
<br><br><br>---------- Forwarded message ----------<br>From: ael <<a href="mailto:witwall3@disroot.org" target="_blank">witwall3@disroot.org</a>><br>To: <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><br>Cc: <br>Bcc: <br>Date: Tue, 28 Jul 2020 11:44:52 +0100<br>Subject: [mkgmap-dev] Virtual paths<br>On Tue, Jul 28, 2020 at 10:58:30AM +0100, Ticker Berkin wrote:<br>
> road/parking aisles within the car park and maybe there should be a<br>
> policy to do this and then there is no problem.<br>
> <br>
> However, there is a good argument that the correct OSM mapping is to<br>
> show paths exactly as they are and not have to invent and add 'virtual'<br>
> bits of footpath just to keep routing engines working sensibly because<br>
> "mkgmap expects it like that".<br>
<br>
Not just mkgmap. It is a general problem. Maybe OSM should introduce<br>
a new relation "connected"? That is one or more ways and/or points could<br>
be members implying that it is possible to navigate (perhaps directly)<br>
between any of them. That would solve many of the problems for all<br>
routers. This idea needs expansion: a tag on the relation would specify<br>
the mode of transport, although I guess this would be mainly foot.<br>
Likewise, some sort of seasonal tag would be useful. But most of those<br>
already exist for ways, so I suppose those could be just be applied to<br>
the relation as well.<br>
<br>
Just musing out loud. If it seems sensible, maybe a proposal on the<br>
tagging list?<br>
<br>
ael<br>
<br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></blockquote></div>