Steve,
indeed the names are absolutely correct when calling with
--overview-mapname.
Checking the outcoming directory structure aswell as the xml file shows
all fine regarding file names:
<?xml version="1.0" encoding="UTF-8"?>
<MapProduct xmlns="http://www.garmin.com/xmlschemas/MapProduct/v1";>
<Name>Freizeitkarte_LUX 16.12</Name>
<DataVersion>100</DataVersion>
<DataFormat>Original</DataFormat>
<ID>6442</ID>
<IDX>Freizeitkarte_LUX.mdx</IDX>
<MDR>Freizeitkarte_LUX_mdr</MDR>
<TYP>6442.TYP</TYP>
<SubProduct>
<Name>Freizeitkarte_LUX 16.12</Name>
<ID>1</ID>
<BaseMap>Freizeitkarte_LUX</BaseMap>
<TDB>Freizeitkarte_LUX.tdb</TDB>
<Directory>Product1</Directory>
</SubProduct>
</MapProduct>
I'm just wondering about DataVersion being 100 eventhough I call mkgmap
with --product-version="1612". Shouldn't that version go into that
DataVersion also ? A gmap archive structure created with jmc_cli does
fill DataVersion with the 'correct' number, btw.
As promised here the xml file from the City Navigator:
Info.xml
<?xml version="1.0" encoding="utf-8"?>
<MapProduct xmlns="http://www.garmin.com/xmlschemas/MapProduct/v1";>
<Name>City Navigator Europe NTU 2016.30</Name>
<InstallationID>1</InstallationID>
<DataVersion>1930</DataVersion>
<DataFormat>NT</DataFormat>
<ID>4037</ID>
<IDX>CNEuroNTU_2016_30.mdx</IDX>
<MDR>CNEuroNTU_2016_30_mdr</MDR>
<TRF>CNEuroNTU_2016_30_trf.trf</TRF>
<TYP>I0000FC5.TYP</TYP>
<SubProduct>
<Name>City Navigator Europe NTU 2016.3</Name>
<ID>1</ID>
<BaseMap>CNEuroNTU_2016_30</BaseMap>
<TDB>CNEuroNTU_2016_30.tdb</TDB>
<Directory>Product1</Directory>
<Notice>eula.txt</Notice>
<MapLogosPath>Logos</MapLogosPath>
</SubProduct>
</MapProduct>
Info_v2.xml:
<?xml version="1.0" encoding="utf-8"?>
<MapProduct xmlns="http://www.garmin.com/xmlschemas/MapProduct/v2";>
<Name>City Navigator Europe NTU 2016.30</Name>
<InstallationID>1</InstallationID>
<DataVersion>1930</DataVersion>
<DataFormat>NT</DataFormat>
<ID>4037</ID>
<Files>
<File id="IDX">CNEuroNTU_2016_30.mdx</File>
<File id="MDR">CNEuroNTU_2016_30_mdr</File>
<File id="TRF">CNEuroNTU_2016_30_trf.trf</File>
<File id="TYP">I0000FC5.TYP</File>
</Files>
<SubProduct>
<Name>City Navigator Europe NTU 2016.3</Name>
<ID>1</ID>
<BaseMap>CNEuroNTU_2016_30</BaseMap>
<Directory>Product1</Directory>
<Files>
<File id="TDB">CNEuroNTU_2016_30.tdb</File>
<File id="NoticeUtf8">eula.txt</File>
</Files>
</SubProduct>
<MapLogosPath>Logos</MapLogosPath>
</MapProduct>
Thanks and regards
Patrik
On 15.12.2016 09:05, Patrik Brunner wrote:
I'll give it another try latest tomorrow. Could be that I'm not using
--overview-mapname in the call.... I was just copying the snippets
from the creation of the gmapsupp without too much additional
brainwork and checks.
Regarding City Navigator: I'm quite sure it didn't contain spaces, but
I'll doublecheck when I have access to the machine with the City
Navigator installed and send you the complete content of the XML
file.... also latest tomorrow.
Cheers
Patrik
*Gesendet:* Mittwoch, 14. Dezember 2016 um 23:03 Uhr
*Von:* "Steve Ratcliffe" <[email protected]>
*An:* "Development list for mkgmap" <[email protected]>
*Betreff:* Re: [mkgmap-dev] Adding the gmapi format.
Hi
> I would prefer having the top directory named differently/choosable....
> why not using the basemap name ? or just a free choosable name ?
OK I thought this might merit some discussion.
The top level directory is currently controlled by --overview-mapname.
So it is the same as the basemap name.
It should, based on looking at what the Garmin MapConverter
does, use family-name instead.
The scripts/gmapi-builder.py script uses the product name, which would
not work in the case where there is more than one product in a family.
I don't know if anyone actually does that.
> And: to have another convincing reason: Official City Navigator Europe
> NTU 2016.30 is using the basename 'CNEuroNTU_2016_30' for the gmap
> folder and subcomponents.
What is the family name for that map? It should be in the first
<Name> element in the Info.xml file.
Does it have spaces or underscores or is different altogether?
..Steve
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
