[mkgmap-dev] Named bridges not displaying

Thu May 21 16:54:38 BST 2015

Thanks for the clarifications.

I do want to see the bridge names, so apparently the label:1 option is the
correct one.

Believe me, I really appreciate the work that has been done, and continues
o get done, on mkgmap. Understanding the Garmin format without being an
insider or having some sort of a functional spec must be extremely
difficult. Kudos to you and all the other folks who support and enhance
mkgmap.

If I ever get familiar enough with the program to be of help in clarifying
the documentation, I will volunteer my time to do that. But at my present
level of understanding, I'm afraid I wouldn't be of much help.

Dave

On Wed, May 20, 2015 at 10:42 PM, Gerd Petermann <
gpetermann_muenchen at hotmail.com> wrote:

> Hi Dave,
>
> I agree that the rules to set a "name" are very confusing, esp. when it
> comes to roads. I guess one reason is that it took a while to discover
> that a map object can have 4 labels,
> another point is that we don't try to explain the Garmin format in this
> manual, instead we presume that the reader knows the details of the
> Garmin format quite well.
> Maybe it would help to add a chapter with links to
> the corresponding manuals and wiki pages.
> If you have the time, please propose improvements, the sources are
> almost normal text files.
>
> Reg. your questions:
> Why not addabel ?
> I thought you want to see the bridge name in the map. If that is the case,
> you have
> to set mkgmap:label:1 . If you want to be able to find the bridge in
> address search,
> you can use addlabel without problems.
>
> Why doesn't set name='${bridge:name}' work?
> Because it sets the tag name to a new /different value. If it is not
> followed
> by a rule that uses this value to set mkgmap:label:* you will not see a
> change.
>
> Gerd
>
> ------------------------------
> From: daveswarthout at gmail.com
> Date: Wed, 20 May 2015 12:09:55 -0700
> Subject: Re: [mkgmap-dev] Named bridges not displaying
> To: gpetermann_muenchen at hotmail.com
>
>
> Thank you very much. That worked like a charm.
>
> As for the style manual,
>
> 4.3.6. name
> This sets the first label of the element but only if it is not already
> set. This is a helper action. The same
> effect can be produced with different notations as it is shown in the
> following example where all three
> lines have the same effect.
>    {name '${name} (${ref})' | '${ref}' | '${name}'}
>    {add mkgmap:label:1='${name} (${ref})' | '${ref}' | '${name}'}
>    mkgmap:label:1!=* {set mkgmap:label:1='${name} (${ref})' | '${ref}' |
> '${name}'}
>
> How one would determine that this is a situation when one must assign a
> mkgmap label is beyond me. I could have read that description a thousand
> times and not figured out what to do. What's missing is WHY one would use
> the name directive in this way. And then, some information about the use of
> mkgmap:label:1 in these circumstances would be helpful too.
>
> In scanning the manual I noticed another directive, addlabel which would
> assign the next available label level. Why didn't you use that? I'm
> thinking it's because you already knew the tags for these two bridges so
> you knew mkgmap:label:1 was not being used. But wouldn't addlabel be a
> "safer" way to go about this in the general case?
>
> One last question: During my struggles I tried using the set command, {set
> name='${bridge:name}' }, to replace the name of the section of highway that
> crosses the bridge with the bridge name but it didn't work. Could you
> venture a reason for that?
>
>
>
> On Wed, May 20, 2015 at 10:02 AM, Gerd Petermann <
> gpetermann_muenchen at hotmail.com> wrote:
>
> Hi Dave,
>
> the name action has no effect when mkgmap:label:1 is already
> set. You may move your rule before those
> that use the highway name, or you can use
> bridge=* & bridge:name=* {set mkgmap:label:1= '${bridge:name}'; echotags
> ""}
>
> See style manual section 4.3.6
>
> Gerd
>
> ------------------------------
> From: daveswarthout at gmail.com
> Date: Wed, 20 May 2015 09:49:43 -0700
> To: mkgmap-dev at lists.mkgmap.org.uk
> Subject: [mkgmap-dev] Named bridges not displaying
>
>
> Thanks for all the good effort on the exit_to and destination issues.
> Everything is working well for me now.
>
> I discovered another problem that might be simple to fix, or maybe there's
> something that I'm doing wrong. There are two named bridges in my current
> area but the names do not display on my maps.
>
> I placed this rule in my lines style file:
>
> bridge=* & bridge:name=* {name '${bridge:name}'; echotags ""}
>
> here is the stderr output
>
> 221689337 - [highway=tertiary,ref=CR 48,mkgmap:label:2=Lower Smith River
> Road (CR 48),bridge=yes,name=Lower Smith River Road,bridge:name=Jack Franz
> Bridge,surface=asphalt,mkgmap:street=Lower Smith River Road,mkgmap:label:1=
> CR48 Lower Smith River Road,ele=1]
> 336150197 - [highway=residential,mkgmap:street=Goodpasture
> Road,mkgmap:label:1=Goodpasture
> Road,covered=yes,bridge=yes,bridge:name=Goodpasture Bridge,name=Goodpasture
> Road]
>
> The bridge name does not appear on the compiled maps.
>
> Any ideas or suggestions?
>
> Dave
> --
> 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
>
>
>
>
> --
> 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
>

-- 
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150521/011177fb/attachment-0001.html>