[mkgmap-dev] License File <mapid>000_license.txt

Mon Apr 20 08:59:31 BST 2020

Hi Mike,

my thinking is that mkgmap produces a map format that is outaged, therefore outaged tools can be good tools.
I think you don't find Basecamp easily because Garmin considers it is also outaged ;)
I don't know if there is something which you can do with Mapsource but not with Basecamp. I see it more the other way around.
I don't know anything useful that you can do with Basecamp which you cannot do with Mapsource. Maybe route planning?
I've given up to plan routes with the maps produced by mkgmap, the online OSM bicycle routers are much better since years.
I prefer Mapsource because
- Basecamp shows a lot of options which have no effect or don't work well with the non-NT maps.
- it starts much faster.
- I think that the search is easier to use.
OTOH I use both tools to verify/debug mkgmap output.
Anyway, I don't mind to remove Mapsource from the docu about options.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Mike Baggaley <mike at tvage.co.uk>
Gesendet: Sonntag, 19. April 2020 16:12
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] License File <mapid>000_license.txt

Hi Gerd,

you are of course able to choose your preferred tool out of MapSource or
BaseCamp, but I think the documentation should refer to Basecamp as that is
Garmin's current product  (that they seem to like to hide away - I can't
find any way to navigate to it from the Garmin home page). MapSource was
discontinued in 2010 as far as I am aware. I have no maps in NT format and
only use BaseCamp (I primarily use it with my mkgmap created map). I
consider MapSource to be a very poor relation. Is there something I'm
missing that can be done in MapSource that cannot be done in BaseCamp (I
don't have an old GPS requiring a serial connection)? To me, continually
referring to a superseded product in the documentation makes it appear that
mkgmap is out of date in the same way that it would if it referred to
Windows 3.1 or 95.

There was no mention of indexes being used for POI search previously. Does
this need adding? Does it just improve the performance of POI search?

I agree that a separate page about tuning would be a good place to describe
what to do if you run out of memory.

For --nsis, I took the folders directly from the source code in the order
they are specified there, however, I now realise the first one opens a file,
the second one opens a resource. I assume the file open will be relative to
the current directory, but don't know where java looks for its resources.
If you have to experiment to find out where to put the files, this indicates
a shortcoming in the documentation. Perhaps someone with knowledge of this
area can tweak the documentation patch to provide some more information?

Regards,
Mike

-----Original Message-----
From: Gerd Petermann [mailto:gpetermann_muenchen at hotmail.com]
Sent: 19 April 2020 08:30
To: 'Development list for mkgmap' <mkgmap-dev at lists.mkgmap.org.uk>
Subject: Re: [mkgmap-dev] License File <mapid>000_license.txt

Hi Mike,

reg. Mapsource/Basecamp: I prefer to use Mapsource because I think it works
better with the maps produced by mkgmap. Basecamp is probably better when
you have maps in NT format.

reg. --index:
- AFAIK it is not about address search only, it also improves POI searches.
- The hint about "Note that this will require roughly twice as much memory"
was added for those who run into memory problems when creating maps for
large areas with maybe 1000+ tiles, esp. with a 32bit JRE. It is indeed
confusing when you don't know the problem. Maybe we should add a different
documentation about tuning where we could mention typical problems and known
work arounds. It is probably not obvious that you can execute mkgmap with
e.g
java -Xmx6G -jar mkgmap.jar ... -c template.args
java -Xmx6G -jar mkgmap.jar ... --index --gmapsupp *.img
java -Xmx6G -jar mkgmap.jar ... --index --gmapi *.img
to create the indexed mapsets in separate steps

reg. --nsis: AFAIK it first looks for the template files in directory
resources\installer, if not found it uses the default templates. The
distribution comes with
a examples\installer directory containing these defaults. It requires some
experiments to find out where the directory resources\installer has to be
when you start mkgmap with a script.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Mike
Baggaley <mike at tvage.co.uk>
Gesendet: Samstag, 18. April 2020 19:58
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] License File <mapid>000_license.txt

Hi Gerd, now I understand where the file came from, I don't propose any
changes to the code, but attached is a patch to the documentation that adds
some information to assist users in making use of the --nsis option.

I have also replaced most of the occurrences of MapSource with BaseCamp as
MapSource was superseded 10 years ago by BaseCamp.

Also simplified the --index documentation - I think the information about
two indexes and sending a map to the GPS that is  currently included is
confusing and unnecessary, but you may not agree.

Cheers,
Mike

-----Original Message-----
From: Gerd Petermann [mailto:gpetermann_muenchen at hotmail.com]
Sent: 17 April 2020 05:15
To: 'Development list for mkgmap' <mkgmap-dev at lists.mkgmap.org.uk>
Subject: Re: [mkgmap-dev] License File <mapid>000_license.txt

Hi Mike,

see also content of directory mkgmap\resources\installer. I know that Minko
uses his own version of the file license_template.txt for the OFM maps.
Also Thorsten Kukuks scripts seem to create these files in his scripts.

If we change something here we have to do it with great care.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Mike
Baggaley <mike at tvage.co.uk>
Gesendet: Freitag, 17. April 2020 00:21
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] License File <mapid>000_license.txt

Answering my own question - I have realised that this is created by the
--nsis option, which I had mistakenly got in my config file, and is used by
the NSIS installer rather than the maps themselves. However, it seems
illogical to me that this should not use the contents of --license-file.

Cheers,
Mike

-----Original Message-----
From: Mike Baggaley [mailto:mike at tvage.co.uk]
Sent: 16 April 2020 19:34
To: 'Development list for mkgmap' <mkgmap-dev at lists.mkgmap.org.uk>
Subject: License File <mapid>000_license.txt

Hi all, I notice that mkgmap creates a file named <mapid>000_license.txt
that contains the following text:

Map data (c) OpenStreetMap and its contributors
http://www.openstreetmap.org/copyright

This map data is made available under the Open Database License:
http://opendatacommons.org/licenses/odbl/1.0/.
Any rights in individual contents of the database are licensed under the
Database Contents License: http://opendatacommons.org/licenses/dbcl/1.0/
Map created with mkgmap-r4473M

This does not seem to be displayable in either Basecamp or Mapsource and
does not contain the txt from my --license-file option. Can anyone explain
what this file is for and whether there is a registry setting to get
Basecamp/Mapsource to display it? Also whether there is a reason it does not
contain the text from the --license-file option?

Cheers,
Mike

_______________________________________________
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
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev