Using exit refs in routing directions
Hello list, Is there any way to get mkgmap to embed exit refs (where they exist) in the routing directions, so that instead of getting: "Exit right onto ramp" you get "Take exit 32 right onto ramp" or something similar? Is this something that official Garmin maps can do? -- Charlie
If you use the default style, it should be automatic (if it's a ramp, then the name of the street behind will be, so it is exit to Street B, instead of drive on Street A). On 14.07.2011 12:05, Charlie Ferrero wrote:
Hello list,
Is there any way to get mkgmap to embed exit refs (where they exist) in the routing directions, so that instead of getting: "Exit right onto ramp" you get "Take exit 32 right onto ramp" or something similar?
Is this something that official Garmin maps can do?
Using the default style, I get the same thing: "Exit right onto ramp". If I changed the OSM data so that the ramp was named "Exit 32" then of course the directions would say "Exit right onto Exit 32", but I was hoping that the ref=32 from the highway=motorway_junction could be used, irrespective of how the ramp was labelled. On 14/07/2011 14:07, Felix Hartmann wrote:
If you use the default style, it should be automatic (if it's a ramp, then the name of the street behind will be, so it is exit to Street B, instead of drive on Street A).
On 14.07.2011 12:05, Charlie Ferrero wrote:
Hello list,
Is there any way to get mkgmap to embed exit refs (where they exist) in the routing directions, so that instead of getting: "Exit right onto ramp" you get "Take exit 32 right onto ramp" or something similar?
Is this something that official Garmin maps can do?
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1390 / Virus Database: 1516/3763 - Release Date: 07/13/11
On 14.07.2011 12:12, Charlie Ferrero wrote:
Using the default style, I get the same thing: "Exit right onto ramp". If I changed the OSM data so that the ramp was named "Exit 32" then of course the directions would say "Exit right onto Exit 32", but I was hoping that the ref=32 from the highway=motorway_junction could be used, irrespective of how the ramp was labelled. Is the ramp two sections??
For me (with my style), ramps do work with the name of the next street segment behind. Not sure what happens if the ramp is several sections (I suppose the first real street behind should be used). 0x09 needs to be used! Doublecheck if that type is really used. Other types wont work (not so sure about 0x08, which might work too).
On 14/07/2011 14:07, Felix Hartmann wrote:
If you use the default style, it should be automatic (if it's a ramp, then the name of the street behind will be, so it is exit to Street B, instead of drive on Street A).
On 14.07.2011 12:05, Charlie Ferrero wrote:
Hello list,
Is there any way to get mkgmap to embed exit refs (where they exist) in the routing directions, so that instead of getting: "Exit right onto ramp" you get "Take exit 32 right onto ramp" or something similar?
Is this something that official Garmin maps can do?
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1390 / Virus Database: 1516/3763 - Release Date: 07/13/11
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Felix Hartmann schrieb am 14.07.2011 12:16:
Is the ramp two sections??
For me (with my style), ramps do work with the name of the next street segment behind. Not sure what happens if the ramp is several sections (I suppose the first real street behind should be used). 0x09 needs to be used! Doublecheck if that type is really used. Other types wont work (not so sure about 0x08, which might work too).
I get the same results. I have thought about a mkgmap extension, which would split the ramps automatically into two ways, to get the name of the exit into the routing direction and not the name of the following street. Gruss Torsten
Am 2011-07-14 13:36, schrieb Torsten Leistikow:
Felix Hartmann schrieb am 14.07.2011 12:16:
Is the ramp two sections??
For me (with my style), ramps do work with the name of the next street segment behind. Not sure what happens if the ramp is several sections (I suppose the first real street behind should be used). 0x09 needs to be used! Doublecheck if that type is really used. Other types wont work (not so sure about 0x08, which might work too). I get the same results. I have thought about a mkgmap extension, which would split the ramps automatically into two ways, to get the name of the exit into the routing direction and not the name of the following street.
Gruss Torsten _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
This is the same problem I have. If you have a solution for this problem, please let me know. Cheers, Martin
On Thu, Jul 14, 2011 at 6:16 AM, Felix Hartmann <extremecarver@gmail.com>wrote:
For me (with my style), ramps do work with the name of the next street segment behind.
This has been a problem to me. Here it is not uncommon that the ramp will use a few yards of another street before getting to the actual street with the name of the exit. E.g. if you look at http://www.openstreetmap.org/?lat=42.35119&lon=-83.04703&zoom=17&layers=Mdri... south on I-75 and having to exit at exit 52. With default style you get "Exit to Hastings Street" nevertheless that exit is signed "52 - Mack Avenue" It would be good indeed to have a mechanism to use motorway_junction name/exit_to and ref in the guidance text.
On 07/14/2011 03:07 AM, Felix Hartmann wrote:
If you use the default style, it should be automatic (if it's a ramp, then the name of the street behind will be, so it is exit to Street B, instead of drive on Street A).
It would be nice if the default style read the values from the highway=motorway_junction node at the start of the ramp when available, otherwise you get examples like Tulsa, OK where, no matter what exit you take from Skelly Bypass (I 44), it tells you to "exit right to Skelly Drive." There are no exits named Skelly Drive on the Skelly Bypass, it's more or less assumed that everyone knows it's the local access versus express lanes of the same overall roadway. Thus, having names, exit_to's or refs from motorway_junction would be a lot more useful.
On Fri, Jul 15, 2011 at 06:42:14PM -0700, Paul Johnson wrote:
It would be nice if the default style read the values from the highway=motorway_junction node at the start of the ramp when available
Is there a style language construct for copying attributes from way nodes to the way? I am not aware of one. If we implemented one, then we could move my tweak for adding mkgmap:dead-end-check=no to oneways whose start or end node carry a fixme key. Best regards, Marko
On 14/07/2011 11:05, Charlie Ferrero wrote:
Hello list,
Is there any way to get mkgmap to embed exit refs (where they exist) in the routing directions, so that instead of getting: "Exit right onto ramp" you get "Take exit 32 right onto ramp" or something similar?
Is this something that official Garmin maps can do? I think mkgmap needs some additional magic to incorporate exits in exactly the same way as Garmin does in the commercial maps. I have been experimenting with ways of improving the routing directions without any major changes to mkgmap and have been making some progress.
Firstly I am using destination=* and dest_ref=* on the ramps. This allows tagging to reflect what is useful for routing without getting into any conflicts about what the exit is *really* called. Some people tag the exit road itself with the exit number, whereas others tag it with the ref-value from the motorway itself or from the road it leads onto. Giving the direction information its own tags allows for clear semantics. To get these tags into the map I have a customised mkgmap style which overrides ref and name with dest_ref and destination respectively. This is an excerpt from my "lines" file: # Set highway names to include the reference if there is one # note: display_name is what the gps will show in the route instructions (highway ~ '.*_link') & exit:to=* {set name='${exit:to}'} (highway = motorway) & destination=* {set name='${destination}'} (highway ~ '.*_link') & destination=* {set name='${destination}'} (highway ~ '.*_link') & destination_ref=* {set ref='${destination_ref}'} (highway ~ '.*_link') & dest_ref=* {set ref='${dest_ref}'} Thereafter the standard rules take over. Net result is that I get "keep right on A123 Townsville" which corresponds to the big signs approaching the exit and above the lanes. This is not exactly the same as "Take exit 32, on right, towards Townsville" which is the sort of thing you can get out of the Garmin with the commercial maps, but it makes the instructions *much* easier to follow. What I am looking for now is a magic incantation to influence mappers into tagging consistently without overloading the semantics of existing keys or unnecessarily creating new ones. Colin
participants (8)
-
Charlie Ferrero -
Colin Smale -
Felix Hartmann -
Marko Mäkelä -
Martin -
Nakor Osm -
Paul Johnson -
Torsten Leistikow