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

Tue Feb 5 08:54:07 GMT 2019

Hi

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

--gmapsupp
--index
--location-autofill=is_in,nearest
--route
--add-pois-to-area
--link-pois-to-ways
--process-exits
--process-destination
--remove-ovm-work-files

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

Regards
Ticker

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