[mkgmap-dev] Problems with -- gmapi (and possibly --gmapsupp also)

Wed Feb 8 10:42:09 GMT 2017

Hi Patrik

> Folder structure looks the same as with for example jmc_cli.

I'm sorry but I still do not understand the problem.

If you create a map normally and then convert it with the garmin
converter does that gmapi map work?

The same map converted with mkgmap --gmapi, you are saying does
not work.

So if the first one works, but the second doesn't, then there must be
a difference between the two maps.

The only differences I know of are:

1. We do not create the top level osmmap.gmapi directory.
2. There are differences in the white space in the Info.xml file.

Or there is a difference in your case that I am not aware of.

If the problem is the first, then it is easy enough to fix.
I can't believe that it is the second, but you never know..

If there is another difference I need to know what it is.
If you could create a small map that does not work that you
could upload that would be helpful.

..Steve

> It doesn't make a difference if I call mkgmap --gmapsupp with the
> overview parameters (--overview-mapname=... --overview-mapnumber=...),
> in no case I have overview maps.
> The only difference is how the files are named inside the gmap directory
> structure, either with the choosen names or with the default names.
>
> Below shown call of mkgmap is the version without overview options...
>
> Cheers
> Patrik
>
> On 06.02.2017 23:33, Steve Ratcliffe wrote:
>> Hi Patrik
>>
>>> I've just noticed that the quite new option --gmapi does not work
>>> properly regarding overview maps:
>>> - I first build the img files where all is correct, overview maps are
>>> properly built and set at the different needed locations (*.tdb file,
>>> elsewhere ?)
>>> - running mkgmap with the option --gmapi (complete output shown below)
>>> causes that the overview maps are not anymore shown in BaseCamp
>>
>> How does the gmapi map differ from one created using the script or
>> Garmin's conversion tool?
>>
>>
>>> BTW: Something similar happens probably with --gmapsupp: there are now
>>> overview maps visible on the GPS itself.
>>
>> The gmapsupp does not contain a base map.  I suppose if you actually
>> included it on the command line then it would be added, but you should
>> not do that.
>>
>> ..Steve
>>> Here the call of mkgmap and its output:
>>>
>>>     java -Xmx1536M -Dfile.encoding=UTF-8 -jar
>>> D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/tools/mkgmap/mkgmap.jar
>>> --max-jobs=2 --index --code-page=1252 --gmapi
>>> --license-file=Freizeitkarte_LUX.license --product-id=1
>>> --family-id=6442 --family-name="Freizeitkarte_LUX"
>>> --series-name="Freizeitkarte_LUX" --description="Freizeitkarte_LUX
>>> (Release 17.02)" --product-version="6442" 6442*.img 6442.TYP
>>> --tdbfile --show-profiles=1
>>>     Time started: Sun Feb 05 16:10:10 CET 2017
>>>     Number of MapFailedExceptions: 0
>>>     Number of ExitExceptions: 0
>>>     Time finished: Sun Feb 05 16:10:12 CET 2017
>>>     Total time taken: 1858ms
>>>
>>> Am I doing something wrong or is this a 'defect' in the newly
>>> implemented gmapi option ?
>>>
>>> Thanks for helping
>>> Patrik
>>>
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev