Keep left/right to xxx

Hi. What are the rules when Garmin instructs to keep right/left to some_road? I know that turn left/right instruction comes if the angle between two nodes is big enough. The reason I'm asking is the situation at: http://www.openstreetmap.org/?lat=60.20587&lon=24.93416&zoom=17&layers=B000F... If I come from south via Ratapihankatu and my route takes me to east on Koskelantie, I get no instructions from the GPS unit. In this case, it would be good to get the "keep right for..." instruction. I have tried (with local file) adjusting the angle where ratapihantiesplits in to two, but only got "turn right" instruction once the angle was big enough. Just that it's not intersection requiring a turn, just a lane change...

Hi Jani,
What are the rules when Garmin instructs to keep right/left to some_road? I know that turn left/right instruction comes if the angle between two nodes is big enough. The reason I'm asking is the situation at:
http://www.openstreetmap.org/?lat=60.20587&lon=24.93416&zoom=17&layers=B000F... If I come from south via Ratapihankatu and my route takes me to east on Koskelantie, I get no instructions from the GPS unit. In this case, it would be good to get the "keep right for..." instruction.
I have tried (with local file) adjusting the angle where ratapihantiesplits in to two, but only got "turn right" instruction once the angle was big enough. Just that it's not intersection requiring a turn, just a lane change...
Yes, instructions are not our strong point at the moment. Some work is obviously required there. It would be great if we could sort the instructions for roundabouts, lane changes, etc. I feel some more late nights coming on! Cheers, Mark

0> In article <20090304190155.3fcd1907@crow>, 0> Mark Burton <URL:mailto:markb@ordern.com> ("Mark") wrote: Mark> Yes, instructions are not our strong point at the moment. Some Mark> work is obviously required there. It would be great if we could Mark> sort the instructions for roundabouts, lane changes, etc. I feel Mark> some more late nights coming on! If you're looking at this, don't forget exits. OSM has exit numbers in the form highway=motorway_junction, ref=*|name=*, and I think there must be a way to see these in instructions. I tried /-------- | highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } \-------- but that didn't make any difference to my directions. Hope that tiny datum is helpful!

Toby said:
I tried
/-------- | highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } \--------
but that didn't make any difference to my directions. Hope that tiny datum is helpful!
Yes it's just one short step away from making a POI that will be visible on the map. highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2000 resolution 16] It's probably not the whole answer because when I tried it out in mapsource, the exit name wasn't mentioned in the routing instructions. It would be good if someone tried out routing via a motorway exit using a map generated with the above addition to points to see if a real GPS mentions the exit by name or not - I suspect it won't but maybe we'll be lucky. It's probably worth adding a rule to generate the POIs for exits anyway. Cheers, Mark

Mark Burton wrote:
highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2000 resolution 16]
It's probably not the whole answer because when I tried it out in mapsource, the exit name wasn't mentioned in the routing instructions.
It would be good if someone tried out routing via a motorway exit using a map generated with the above addition to points to see if a real GPS mentions the exit by name or not - I suspect it won't but maybe we'll be lucky.
Tried that on my Nuvi 250 (first with 0x2000 and then 0x2700) neither of those seem to have any effect. However, changing highway=motorway_link from 0x01 to 0x09 (meaning "Highway exits and connecting ramps" (according to http://www.malsingmaps.com/wiki/index.php/POI_and_Road_object_Reference)) triggers some additional instructions (e.g. keep right onto <motorway-name/ref>). - Michel

Hi Michel,
Mark Burton wrote:
highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2000 resolution 16]
It's probably not the whole answer because when I tried it out in mapsource, the exit name wasn't mentioned in the routing instructions.
It would be good if someone tried out routing via a motorway exit using a map generated with the above addition to points to see if a real GPS mentions the exit by name or not - I suspect it won't but maybe we'll be lucky.
Tried that on my Nuvi 250 (first with 0x2000 and then 0x2700) neither of those seem to have any effect.
Well, not much effect it's true. As far as I can see they make the exit visible but it's not yet findable.
However, changing highway=motorway_link from 0x01 to 0x09 (meaning "Highway exits and connecting ramps" (according to http://www.malsingmaps.com/wiki/index.php/POI_and_Road_object_Reference)) triggers some additional instructions (e.g. keep right onto <motorway-name/ref>).
That's worth having. We may as well also change the code for trunk_link to be the same. Cheers, Mark

Mark Burton wrote:
Hi Michel,
Mark Burton wrote: However, changing highway=motorway_link from 0x01 to 0x09 (meaning "Highway exits and connecting ramps" (according to http://www.malsingmaps.com/wiki/index.php/POI_and_Road_object_Reference)) triggers some additional instructions (e.g. keep right onto <motorway-name/ref>).
That's worth having. We may as well also change the code for trunk_link to be the same.
My test routing (using osm2mp.pl and mkgmap r967) from E6 (motorway) into Hwy3214 (primary) via Exit602 (motorway_link) motorway_link=0x09 - mapsource instruction = "Exit left onto ramp onto Hwy3214" - MobileXT = "Exit left on Hwy3214", "Continue on sliproad to Hwy3214" motorway_link=0x0B (default setting in osm2mp.pl) - mapsource = "Bear left onto Exit602" - MobileXT = "Exit left on Exit602" I prefer motorway_link=0x0B but not sure if other garmin devices give the same instruction. regards, nyem

Toby Speight wrote:
0> In article <20090304190155.3fcd1907@crow>, 0> Mark Burton <URL:mailto:markb@ordern.com> ("Mark") wrote:
Mark> Yes, instructions are not our strong point at the moment. Some Mark> work is obviously required there. It would be great if we could Mark> sort the instructions for roundabouts, lane changes, etc. I feel Mark> some more late nights coming on!
If you're looking at this, don't forget exits. OSM has exit numbers in the form highway=motorway_junction, ref=*|name=*, and I think there must be a way to see these in instructions.
I tried
/-------- | highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } \--------
but that didn't make any difference to my directions. Hope that tiny datum is helpful! _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I have been told to leave a motorway at the correct junction number twice, both times at the same junction. Heading north on the M6 I was told to leave at j33 (the lowercase j is deliberate). I can see nothing different about this junction to any other that would indicate why this happened I can only report that it did http://www.openstreetmap.org/?lat=53.9837&lon=-2.7833&zoom=14&layers=B000FTF At the time I had asked the GPS to take me to Lancaster so this was not a pre-programmed route. I can't say for sure which version of mkgmap the map was created with as it's a few weeks ago and I haven't been back since so it may well still give me the notification. I'd forgotten about it until I read this message. Paul

Toby Speight wrote:
0> In article <20090304190155.3fcd1907@crow>, 0> Mark Burton <URL:mailto:markb@ordern.com> ("Mark") wrote:
Mark> Yes, instructions are not our strong point at the moment. Some Mark> work is obviously required there. It would be great if we could Mark> sort the instructions for roundabouts, lane changes, etc. I feel Mark> some more late nights coming on!
If you're looking at this, don't forget exits. OSM has exit numbers in the form highway=motorway_junction, ref=*|name=*, and I think there must be a way to see these in instructions.
I tried
/-------- | highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } \--------
but that didn't make any difference to my directions. Hope that tiny datum is helpful! _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Scratch that. I see that it's the next link after the link from the motorway that has the M6j33 reference. Sorry again Paul
participants (6)
-
Jani Patanen
-
Mark Burton
-
Michel Marti
-
nyem
-
Paul
-
Toby Speight