Hi, I have created a new exit_hints branch which may adds a new interesting workaround feature. When driving on a motorway my Garmin does not give me a hint on which exit I should leave. It just tells me the name of the street connected to the motorway_link but this isn't helpful because this name isn't shown on any sign on the motorway. It would be more helpful if the Garmin tells me the number and the name of the exit. That's what I am trying in the exit_hints branch. How is that achieved? It is activated if the option --process-destination is set. There is an exit node: highway=motorway_junction ref=53 name=Unna-Ost A motoway_link starts at this exit node. highway=motorway_link ... some more tags ... E================= The motorway_link is now cut into three parts: E11122233333333333 Part 1 and 3 are tagged with the same tags of the original motorway_link. Part 2 is tagged additionally with mkgmap:exit_hint=true mkgmap:exit_hint_ref=53 mkgmap:exit_hint_name=Unna-Ost In the style file there are two additional rules in the lines file: # Name the hint part with the name and the ref of the exit highway=motorway_link & mkgmap:exit_hint=true { delete display_name; name 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' | 'Exit ${mkgmap:exit_hint_name}' } # Use the motorway code for the hint part so that the GPS displays the name as hint where to leave the motorway highway=motorway_link & mkgmap:exit_hint=true { add oneway = yes; add bicycle = no; add foot = no; } [0x01 road_class=3 road_speed=2 resolution 20] Please try and comment if you find it useful or if you have ideas how to realize it in a better way! It is not yet complete: If a motoway_link uses reverse oneway direction the code may fail? Have fun! WanMil
On 12/18/12 11:23 AM, WanMil wrote:
Hi,
I have created a new exit_hints branch which may adds a new interesting workaround feature.
have you looked at the exit_to tag? in the US, we're generally using exit_to to contain the text from the exit sign prior to the actual exit, so if it exists, it should match the local signage. richard
On 12/18/12 11:23 AM, WanMil wrote:
Hi,
I have created a new exit_hints branch which may adds a new interesting workaround feature.
have you looked at the exit_to tag? in the US, we're generally using exit_to to contain the text from the exit sign prior to the actual exit, so if it exists, it should match the local signage.
richard
Yes, I've seen that. This is also on the TODO list :-) WanMil
On 12/18/12 12:18 PM, WanMil wrote:
have you looked at the exit_to tag? in the US, we're generally using exit_to to contain the text from the exit sign prior to the actual exit, so if it exists, it should match the local signage.
Yes, I've seen that. This is also on the TODO list :-)
ok. it has some value simply due to the fact that we've been busy populating it.
richard
On 12/18/12 12:18 PM, WanMil wrote:
have you looked at the exit_to tag? in the US, we're generally using exit_to to contain the text from the exit sign prior to the actual exit, so if it exists, it should match the local signage.
Yes, I've seen that. This is also on the TODO list :-)
ok. it has some value simply due to the fact that we've been busy populating it.
richard
Hi Richard, I've added support for exit_to tagging. The exit_to tags are available in the hint part with the tag mkgmap:exit_hint_exit_to WanMil
Thanks for this great feature WanMil! At exits it works as expected, One thing though. Not all motorway_junction nodes are related to exits. In some cases they are used for the name of interchanges (like 'Kreuz Bielefeld<http://www.openstreetmap.org/?lat=51.94222&lon=8.545&zoom=16&layers=M>"). At this moment Mapsource shows 'exit Kreuz Bielefeld' and not the destination. Is there a way to make a distinction, possibly by the difference that exits always lead to lower grade highways? Cheers, Johan 2012/12/20 WanMil <wmgcnfg@web.de>
On 12/18/12 12:18 PM, WanMil wrote:
have you looked at the exit_to tag? in the US, we're generally using
exit_to
to contain the text from the exit sign prior to the actual exit, so if it exists, it should match the local signage.
Yes, I've seen that. This is also on the TODO list :-)
ok. it has some value simply due to the fact that we've been busy populating it.
richard
Hi Richard,
I've added support for exit_to tagging. The exit_to tags are available in the hint part with the tag mkgmap:exit_hint_exit_to
WanMil
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thanks for testing. In case the destination is tagged on the motorway_link you can easily add that to the exit_hint way name: highway=motorway_link & mkgmap:exit_hint=true { delete display_name; name 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' ${destination} | 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' | 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_exit_to}' | 'Exit ${mkgmap:exit_hint_exit_to}' | 'Exit ${mkgmap:exit_hint_name}' | 'Exit ${mkgmap:exit_hint_ref}' } But in most cases the text is too long and is therefore not displayed. And not all motorway_links are tagged with destination at its beginnig (that's the case in Kreuz Bielefeld). I will try to analyze if the exit leads to lower grade highways. Anyhow with the current implementation you will get the hint to leave on exit number NN at Kreuz XXX. And just after exiting you get the destination as hint. But for some case that might be too late.... WanMil
Thanks for this great feature WanMil! At exits it works as expected, One thing though. Not all motorway_junction nodes are related to exits. In some cases they are used for the name of interchanges (like 'Kreuz Bielefeld <http://www.openstreetmap.org/?lat=51.94222&lon=8.545&zoom=16&layers=M>"). At this moment Mapsource shows 'exit Kreuz Bielefeld' and not the destination. Is there a way to make a distinction, possibly by the difference that exits always lead to lower grade highways?
Cheers, Johan
2012/12/20 WanMil <wmgcnfg@web.de <mailto:wmgcnfg@web.de>>
> On 12/18/12 12:18 PM, WanMil wrote: >>> >>> have you looked at the exit_to tag? in the US, we're generally using exit_to >>> to contain the text from the exit sign prior to the actual exit, so if >>> it exists, >>> it should match the local signage. >>> >>> Yes, I've seen that. This is also on the TODO list :-) >>> > ok. it has some value simply due to the fact that we've been busy > populating it. > > richard >
Hi Richard,
I've added support for exit_to tagging. The exit_to tags are available in the hint part with the tag mkgmap:exit_hint_exit_to
WanMil
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
And not all motorway_links are tagged with destination at its beginnig (that's the case in Kreuz Bielefeld). That's correct, a lot of destination data is still missing in OSM. But, the situation is improving
This afternoon in live testing I found what seems to be a bug. Exits from a parallel lane, tagged as motorway_link, didn't show up with the exit_hint. Maybe the code does not know to which motorway_link of the y-branch the exit_hint has to be put on. Is it possible to assign the exit_hint to the motorway_link which is going to the right? Cheers, Johan 2012/12/21 WanMil <wmgcnfg@web.de>
Thanks for testing.
In case the destination is tagged on the motorway_link you can easily add that to the exit_hint way name: highway=motorway_link & mkgmap:exit_hint=true { delete display_name; name 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' ${destination} | 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' | 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_exit_to}' | 'Exit ${mkgmap:exit_hint_exit_to}' | 'Exit ${mkgmap:exit_hint_name}' | 'Exit ${mkgmap:exit_hint_ref}' }
But in most cases the text is too long and is therefore not displayed. And not all motorway_links are tagged with destination at its beginnig (that's the case in Kreuz Bielefeld).
I will try to analyze if the exit leads to lower grade highways. Anyhow with the current implementation you will get the hint to leave on exit number NN at Kreuz XXX. And just after exiting you get the destination as hint. But for some case that might be too late....
WanMil
Thanks for this great feature WanMil! At exits it works as expected, One thing though. Not all motorway_junction nodes are related to exits. In some cases they are used for the name of interchanges (like 'Kreuz Bielefeld <http://www.openstreetmap.org/?lat=51.94222&lon=8.545&zoom=16&layers=M "). At this moment Mapsource shows 'exit Kreuz Bielefeld' and not the destination. Is there a way to make a distinction, possibly by the difference that exits always lead to lower grade highways?
Cheers, Johan
2012/12/20 WanMil <wmgcnfg@web.de <mailto:wmgcnfg@web.de>>
> On 12/18/12 12:18 PM, WanMil wrote: >>> >>> have you looked at the exit_to tag? in the US, we're generally using exit_to >>> to contain the text from the exit sign prior to the actual exit, so if >>> it exists, >>> it should match the local signage. >>> >>> Yes, I've seen that. This is also on the TODO list :-) >>> > ok. it has some value simply due to the fact that we've been busy > populating it. > > richard >
Hi Richard,
I've added support for exit_to tagging. The exit_to tags are available in the hint part with the tag mkgmap:exit_hint_exit_to
WanMil
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto: mkgmap-dev@lists.mkgmap.org.uk> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
This afternoon in live testing I found what seems to be a bug. Exits from a parallel lane, tagged as motorway_link, didn't show up with the exit_hint. Maybe the code does not know to which motorway_link of the y-branch the exit_hint has to be put on. Is it possible to assign the exit_hint to the motorway_link which is going to the right?
I set the exit_hint only on exits directly from motorways because hints on parallel lines should be created from the destination tags. So have a look on the following junction: ===E==================================== \ / -------e---------------------- \ \destination=Berlin === motorway --- motorway_link E exit node on motorway e exit node on motorway_link So and exit_hint is created only for E because after you have passed E the Garmin should tell you the correct destination which is usually written on the signs in the motorway junction (in Germany...). If an exit hint would also be created for e you would see the destination only after passing e and that's too late. The motorway junctions if have analyzed did have the same tags on E and e so there is no additional information. WanMil
Good drawing, that's exactly what I meant. Still I'm not totally convinced. If both E and e do have a motorway_junction node, why shouldn't the code be applied to both motorway_links? Now I saw the typical Garmin behaviour on e to show the name of the lower grade road at the end of the motorway_link, which wasn't very informative. Cherio, Johan 2012/12/21 WanMil <wmgcnfg@web.de>
This afternoon in live testing I found what seems to be a bug. Exits from a parallel lane, tagged as motorway_link, didn't show up with the exit_hint. Maybe the code does not know to which motorway_link of the y-branch the exit_hint has to be put on. Is it possible to assign the exit_hint to the motorway_link which is going to the right?
I set the exit_hint only on exits directly from motorways because hints on parallel lines should be created from the destination tags.
So have a look on the following junction:
===E==================================== \ / -------e---------------------- \ \destination=Berlin
=== motorway --- motorway_link E exit node on motorway e exit node on motorway_link
So and exit_hint is created only for E because after you have passed E the Garmin should tell you the correct destination which is usually written on the signs in the motorway junction (in Germany...). If an exit hint would also be created for e you would see the destination only after passing e and that's too late. The motorway junctions if have analyzed did have the same tags on E and e so there is no additional information.
WanMil _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Johan, in Germany it's typical this way, if there is an 'e' and not only an 'E': ===E==================================== \ / -------e1-------e2------------ \ \ \ \ E: City1, City2 e1: City1 e2: City2 So the GPS should tell you something like: "leave motorway to City1, City2" and then "leave now to City1". Henning
That sounds logical, this is also quite common in Holland. The question then is this in my opinion: how will mkgmap create maps for situations like this, informing users: "leave now to City1"? Cheers, Johan Ps after a discussion last August on the Dutch forum it was decided -for Holland- that long parrallel highways with several exits should be tagged as highway=motorway instead of motorway_link, which is also a solution in this case Op vrijdag 21 december 2012 schreef Henning Scholland (osm@aighes.de) het volgende:
Hi Johan, in Germany it's typical this way, if there is an 'e' and not only an 'E':
===E==================================== \ / -------e1-------e2------------ \ \ \ \
E: City1, City2 e1: City1 e2: City2
So the GPS should tell you something like: "leave motorway to City1, City2" and then "leave now to City1".
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <javascript:;> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Yes, but the leave now to City1 should be realized by the destination tag. I know it is not tagged everywhere. But tagging of exits in motorway junctions is at least inconsistent. One of my test junctions was Kreuz Kamp-Lintfort (http://www.openstreetmap.org/?lat=51.48782&lon=6.58276&zoom=16&layers=M). On this junction using e1 and e2 for the new exit hint feature was very irritating and could better be modelled with the destination tag. WanMil
That sounds logical, this is also quite common in Holland. The question then is this in my opinion: how will mkgmap create maps for situations like this, informing users: "leave now to City1"?
Cheers, Johan
Ps after a discussion last August on the Dutch forum it was decided -for Holland- that long parrallel highways with several exits should be tagged as highway=motorway instead of motorway_link, which is also a solution in this case
Op vrijdag 21 december 2012 schreef Henning Scholland (osm@aighes.de <mailto:osm@aighes.de>) het volgende:
Hi Johan, in Germany it's typical this way, if there is an 'e' and not only an 'E':
===E==================================== \ / -------e1-------e2------------ \ \ \ \
E: City1, City2 e1: City1 e2: City2
So the GPS should tell you something like: "leave motorway to City1, City2" and then "leave now to City1".
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <javascript:;> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 18.12.2012 17:23, schrieb WanMil:
I have created a new exit_hints branch which may adds a new interesting workaround feature.
[..]
Please try and comment if you find it useful or if you have ideas how to realize it in a better way!
Works very well already, good work! One minor issue: The logic does not differentiate between real exits and motorway junctions. So, on motorway junctions the exit hint overrides the (maybe more useful) destination-hint. Idea : store the destination road type (the first highway following the _link ways) to a tag like mkgmap:exit_hint_dest_hw = motorway / trunk / primary / etc. Then in the style one could filter out the motorway junctions and give the exit hint only for real exists. Chris
Am 18.12.2012 17:23, schrieb WanMil:
I have created a new exit_hints branch which may adds a new interesting workaround feature.
[..]
Please try and comment if you find it useful or if you have ideas how to realize it in a better way!
Works very well already, good work!
One minor issue:
The logic does not differentiate between real exits and motorway junctions. So, on motorway junctions the exit hint overrides the (maybe more useful) destination-hint.
Idea : store the destination road type (the first highway following the _link ways) to a tag like mkgmap:exit_hint_dest_hw = motorway / trunk / primary / etc.
Then in the style one could filter out the motorway junctions and give the exit hint only for real exists.
Chris
Hi Chris, I will check if that can be realized in a useful way. I fear there could be problems with complex motorway junctions and motorway junctions that also contain exits. WanMil
Am 18.12.2012 17:23, schrieb WanMil:
It is activated if the option --process-destination is set.
I suggest a suboption for this: --process-destination=dest,exit because not everyone may like the appearance[1] of the links (motorway_link -> motorway -> motorway_link) Chris [1] <http://up.picr.de/12912767ci.jpg>
It is activated if the option --process-destination is set.
I suggest a suboption for this:
--process-destination=dest,exit
because not everyone may like the appearance[1] of the links (motorway_link -> motorway -> motorway_link)
That's not necessary. The motorway parts only appear if you use special rules for the mkgmap:exit_hint=true parts. WanMil
Chris
participants (5)
-
Chris66 -
Henning Scholland -
Johan C -
Richard Welty -
WanMil