[mkgmap-dev] How to label maps generated by mkgmap -r3742

Tue Jan 10 19:09:36 GMT 2017

So if ALWAYS use --gmapsupp and template.args, should all of my options be
listed AFTER template.args and BEFORE --gmapsupp?
Example :
c template.args master_thin.txt <<OPTIONS>> --gmapsupp

On Tue, Jan 10, 2017 at 8:33 AM, Gerd Petermann <
GPetermann_muenchen at hotmail.com> wrote:

>
> Hi Greg,
>
> options.txt groups options by meaning. The order of options is important
> in that way that you can do something like this:
> java -jar mkgmap.jar --style=s1 1234*.osm.pbf  --description=2nd_style
> --style=s2 1235*.osm.pbf
> For the files 1234*.osm.pbf the style s1 is used and option  description
> is "not visible", for the files 1235*.osm.pbf the style s2 is used
> and description is "2nd_style".
> This concept is broken when it comes to options like "index","gmapsupp",
> "tdbfile", and others which are always processed after
> the *.pbf files so that they always "see" the last setting of an option.
> I hope that makes it clearer?
>
> The file template.args is just a generated file which uses these rules,
> you can create your own file as well.
> I'll think about a hint reg. template.args.
>
> Gerd
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
> greg crago <gregcrago at gmail.com>
> Gesendet: Dienstag, 10. Januar 2017 17:11:04
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] How to label maps generated by mkgmap -r3742
>
> I want to make sure I understand how the ORDER of the OPTIONS are to used.
> I was using the "options.txt" file to determine the order of the options.
> Is that correct?
>
> Why exactly did you recommend putting the --description AFTER the -c
> template.args option?
>
> Can you add a note to "options.txt" and using SPLTTER (template.args)
> OVERWRITES --mapname, --description, and --input-file?
>
> I have --area-name and I cannot see it anywhere in BaseCamp or my GPS.
> I used --x-mapeset-name=blabla and I cannot see it anywhere in BaseCamp or
> my GPS.
>
> Greg
>
> On Mon, Jan 9, 2017 at 10:49 PM, Gerd Petermann <
> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>>
> wrote:
> The java code shows that the options area-name and mapset-name are
> evaluated.
> The latter one doesn't appear in the help file, so it is an undocumented
> option and
> you can only use it with --x-mapeset-name=blabla
>
> GMapTool shows the value, but I did not try where it appears on the device
> or what effect it has.
>
> Gerd
>
>
> greg crago wrote
> > Thank you.
> >
> > java ... mkgmap.jar ... -c template.args master_thin.txt
> --description=XYZ
> > --gmapsupp
> >
> > Worked on BaseCamp and on Garmin GPS.
> >
> > The only thing that would be nice would be a FAMILY description on the
> > GPS.
> > Right now, Garmin City Navigator Shows a MAPNAME and in a smaller font
> > another name (family name?)
>
>
>
>
>
> --
> View this message in context: http://gis.19327.n8.nabble.
> com/How-to-label-maps-generated-by-mkgmap-r3742-tp5888897p5889072.html
> Sent from the Mkgmap Development mailing list archive at Nabble.com.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
> _______________________________________________
> 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/20170110/6063c173/attachment.html>