[mkgmap-dev] FW: Routing parameters

Sat May 16 11:04:48 BST 2015

From: gpetermann_muenchen at hotmail.com
To: daveswarthout at gmail.com
Subject: RE: [mkgmap-dev] Routing parameters
Date: Sat, 16 May 2015 12:02:22 +0200

Hi Dave,

not sure what the problem is.
The subst filters are just used to remove some blanks or semicolons.
The rest is more or less "a list of alternative expressions separated with a vertical bar",
you can search for that term in the style manual:
http://www.mkgmap.org.uk/doc/pdf/style-manual.pdf

I've never tried these options because I use my GPS only for cycling,
but my understanding is that the types 0x08 and 0x09 are special
as they instruct the Garmin device to use the name of the road for the 
destination hint, and these rules are used to fill this name with useful
information.

Does that help?

Gerd

From: daveswarthout at gmail.com
Date: Fri, 15 May 2015 17:51:13 -0700
To: mkgmap-dev at lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Routing parameters

Yes, as you can see above, I  understand the intent of those two options. But if someone could further explain what's happening in the rule, I would be most appreciative. 
I'm guessing the first part assigns a name or ref if one appears in the tagging but understanding the logic of the series of "subst" filters following that is, for a newbie, quite challenging.
On Fri, May 15, 2015 at 12:17 PM, GerdP <gpetermann_muenchen at hotmail.com> wrote:
Hi Dave,

please check the documentation for --process-destination and

--process-exits:

http://www.mkgmap.org.uk/doc/options

If I got this right, these option mark exits so that Garmin knows where

they are where they lead.

Gerd

Dave Swarthout wrote

> I am curious to know how mkgmap handles the display of and text to speech

> aspects of motorway junctions. It's hard to test for this without actually

> creating a route and then driving it to see and hear what the Garmin is

> doing with the data or to discover where it gets the information from.

>

> I'm assuming that whatever one puts in the exit_to=* tag gets displayed

> and

> spoken by the Garmin "assistant". Does mkgmap ever use the destination=*

> tag, and if so under what circumstances?

>

> I found this rule in the lines style sheet, but I do not understand it

> well

> enough to help me answer my question

>

> (highway=motorway_link | highway=trunk_link) & mkgmap:exit_hint=true &

> mkgmap:dest_hint=true

>   { name '${destination:ref|subst: =>} ${destination|subst:;=> |subst:/=>

> }' |

>          '${ref|subst: =>} ${destination|subst:;=> |subst:/=> }' |

>          '${destination|subst:;=> |subst:/=> }' |

>          'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' |

> highway=road

>          '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}'

>        }

>

>

> As always, thanks in advance to any help you can provide.

>

> Dave

>

> --

> Dave Swarthout

> Homer, Alaska

> Chiang Mai, Thailand

> Travel Blog at http://dswarthout.blogspot.com

>

> _______________________________________________

> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

--

View this message in context: http://gis.19327.n5.nabble.com/Routing-parameters-tp5844762p5844766.html

Sent from the Mkgmap Development mailing list archive at Nabble.com.

_______________________________________________

mkgmap-dev mailing list

mkgmap-dev at lists.mkgmap.org.uk

http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- 
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev 		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150516/1a524e6f/attachment.html>