logo separator

[mkgmap-dev] Shouldn't both options --gmapi and --nsis imply --tdbfile?

From Gerd Petermann gpetermann_muenchen at hotmail.com on Tue Feb 5 09:13:06 GMT 2019

Hi all,

I still don't dare to change the option handling in mkgmap completely. My understanding is that we have two groups of users:
- One large group uses mkgmap since long and has all kinds of scripts which expect exactly the current behaviour.
Thus I consider backward compatibility very important.
- One small group (the newbies) try to create a map on their own and those are lost with all the options needed to get a good map.
I think those users would also not profit if we suddenly change all kinds of defaults because they will find even more confusing hints and

Maybe there is someone who volunteers to create a small beginners guide?
A very simple one woud be this:
Recommended options to create a map for car routing with full address search:
--gmapi --gmapsupp --nsis --index --split-name-index --bounds=bounds.zip --housenumbers  --route --check-roundabouts --add-pois-to-areas --link-pois-to-ways --process-destination --process-exits

Just reading Tickers comment it seems that we created almost the same list here, but I would not recommend to use --remove-ovm-work-files.
In fact I thought about removing this option as it is likely to cause trouble when you try to compile the map in multiple steps.

The default for --add-boundary-nodes-at-admin-boundaries is (and was) 2 since the merge into trunk.


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Dienstag, 5. Februar 2019 09:54
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Shouldn't both options --gmapi and --nsis imply --tdbfile?


I think it is reasonable that mkgmap, when explicitly being used to
generate GMAPSUPP.IMG doesn't generate PC files unless other options
imply that a PC image is also wanted - it does take extra time and a
lot of memory. Options --gmapi or --tdbfile imply PC files are wanted
and should cause generation of PC indexes if --index is on.

My thoughts on the default values of options:

When new features are introduced, they should be OFF by default -
experts who follow the development can turn them on if they want to
experiment. A while later, when the feature has settled down and is
thought to be generally good, the default should be changed to ON.

Some candidates for now being ON by default


maybe also --check_roundabout*, but I'm not sure of the default values
for these and the help text doesn't say

About now would be the time for changing:
--add-boundary-nodes-at-admin-boundaries= from 0 to 2


On Mon, 2019-02-04 at 18:12 -0500, EthnicFood IsGreat wrote:
> >
> > Message: 1
> > Date: Sun, 03 Feb 2019 09:15:33 -0500
> > From: Greg Troxel <gdt at lexort.com>
> > To: Gerd Petermann <GPetermann_muenchen at hotmail.com>
> > Cc: "mkgmap-dev at lists.mkgmap.org.uk" <
> > mkgmap-dev at lists.mkgmap.org.uk>
> > Subject: Re: [mkgmap-dev] Shouldn't both options --gmapi and --nsis
> >     imply   --tdbfile?
> >
> >
> > Gerd Petermann <GPetermann_muenchen at hotmail.com> writes:
> >
> > > I never understood why adding option --gmapsupp suppresses the
> > > creation of the pc index file(s). Is it really only because the
> > > current implementation requires more memory?
> > I don't understand either, and it feels like a bug.
> >
> > I have long been in favor of having the defaults make the map that
> > a
> > user of a reasonably modern device (oregon, etrex 30, etc.) would
> > want,
> > if they understood the options.  It seems like index/route should
> > be on
> > by default, and there can be --no-index for devices where that
> > causes
> > trouble.
> >
> >
> >
> > ------------------------------
> >
> >
> +1
> Mark
> _______________________________________________
> mkgmap-dev mailing list
> 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

More information about the mkgmap-dev mailing list