<html><head></head><body><p dir="ltr">Hi</p>
<p dir="ltr">Yes good point that is likely the problem.</p>
<p dir="ltr">Creating the overview map is a second stage thing<br></p>
<p dir="ltr">Steve</p>
<br><br><div class="gmail_quote">On 8 February 2017 20:40:07 GMT+00:00, Gerd Petermann <GPetermann_muenchen@hotmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi Patrik,<br /><br />I think the overview map might be missing because your cfg file contains option<br />remove-ovm-work-files<br />I guess the --gmapi option doesn't try to find/identify an existing overview map.<br /><br />Gerd<br /><hr /><br />Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Patrik Brunner <patrik.brunner@gmx.net><br />Gesendet: Mittwoch, 8. Februar 2017 21:33:53<br />An: mkgmap-dev@lists.mkgmap.org.uk<br />Betreff: Re: [mkgmap-dev] Problems with -- gmapi (and possibly --gmapsupp also)<br /><br />Steve,<br /><br />in the process of building all different flavors of map (imagedir,<br />gmapsupp, gmapi) first the img files are built and afterward collected<br />together. The creation is done by calling mkgmap as follows (cfg file<br />attached):<br /><br />java -Xmx1536M -Dfile.encoding=UTF-8 -jar D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/tools/mkgmap/mkgmap.jar --max-jobs=2 -c
Freizeitkarte_LUX.cfg --check-styles<br />Time started: Wed Feb 08 21:07:23 CET 2017<br />Found one style in D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/work/Freizeitkarte_LUX_fr/style/fzk<br />finished check-styles<br />Number of MapFailedExceptions: 0<br />Number of ExitExceptions: 0<br />Time finished: Wed Feb 08 21:08:04 CET 2017<br />Total time taken: 40429ms<br /><br />After the the result is ok, the resulting map shown in BaseCamp (images<br />installed via Registry) does show the overview map. As far as I know the<br />overview map (as well as the flag to show the heigth profiles) are<br />stored in the tdb file, correct ?<br /><br />Later in the normal process I call jmc_cli to convert the images into<br />gmapi format. This does not seem to screw the overview map (inside the<br />tdb file put into the gmap folder structure) and also shows the height<br />profiles.<br /><br />But if I use the new functionality of mkgmap to convert the images into<br />gmapi
format the height profiles and the overview map got lost. The tdb<br />and some other files (map files, but not the tile files) have a new<br />change time.<br />The missing heigth profiles could be fixed by just adding<br />--show-profiles=1 to the call, but I was not able to get the overview<br />map running. The actual call is:<br /><br />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)" --overview-mapname="Freizeitkarte_LUX" --overview-mapnumber=64420000 --product-version="1702" 6442*.img 6442.TYP --tdbfile --show-profiles=1<br />Time started: Wed Feb 08 21:22:06 CET 2017<br />Number of MapFailedExceptions: 0<br />Number of ExitExceptions: 0<br />Time finished: Wed Feb 08
21:22:08 CET 2017<br />Total time taken: 1702ms<br /><br />I was also trying to call it without the overview options which results<br />also in a map without overview map, but just with different (default)<br />filenames inside the gmap directory structure.<br />Calling it without --tdbfile also didn't help.<br /><br />Any ideas ? Am I doing something wrong due to lack of understanding or<br />does mkgmap behave wrongly ?<br /><br />Thanks and regards<br />Patrik<br /><br />On 08.02.2017 11:42, Steve Ratcliffe wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><br /> Hi Patrik<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Folder structure looks the same as with for example jmc_cli.<br /></blockquote><br /> I'm sorry but I still do not understand the problem.<br /><br /> If you create a map normally and then convert it with
the garmin<br /> converter does that gmapi map work?<br /><br /> The same map converted with mkgmap --gmapi, you are saying does<br /> not work.<br /><br /> So if the first one works, but the second doesn't, then there must be<br /> a difference between the two maps.<br /><br /> The only differences I know of are:<br /><br /> 1. We do not create the top level osmmap.gmapi directory.<br /> 2. There are differences in the white space in the Info.xml file.<br /><br /> Or there is a difference in your case that I am not aware of.<br /><br /> If the problem is the first, then it is easy enough to fix.<br /> I can't believe that it is the second, but you never know..<br /><br /> If there is another difference I need to know what it is.<br /> If you could create a small map that does not work that you<br /> could upload that would be helpful.<br /><br /> ..Steve<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">
It doesn't make a difference if I call mkgmap --gmapsupp with the<br /> overview parameters (--overview-mapname=... --overview-mapnumber=...),<br /> in no case I have overview maps.<br /> The only difference is how the files are named inside the gmap directory<br /> structure, either with the choosen names or with the default names.<br /><br /> Below shown call of mkgmap is the version without overview options...<br /><br /> Cheers<br /> Patrik<br /><br /> On 06.02.2017 23:33, Steve Ratcliffe wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"> Hi Patrik<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> I've just noticed that the quite new option --gmapi does not work<br /> properly regarding overview maps:<br /> - I first build the img files where all is correct, overview maps are<br /> properly built and set at the different
needed locations (*.tdb file,<br /> elsewhere ?)<br /> - running mkgmap with the option --gmapi (complete output shown below)<br /> causes that the overview maps are not anymore shown in BaseCamp<br /></blockquote><br /> How does the gmapi map differ from one created using the script or<br /> Garmin's conversion tool?<br /><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> BTW: Something similar happens probably with --gmapsupp: there are now<br /> overview maps visible on the GPS itself.<br /></blockquote><br /> The gmapsupp does not contain a base map. I suppose if you actually<br /> included it on the command line then it would be added, but you should<br /> not do that.<br /><br /> ..Steve<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> Here the call of mkgmap and its output:<br /><br /> java -Xmx1536M
-Dfile.encoding=UTF-8 -jar<br /> D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/tools/mkgmap/mkgmap.jar<br /><br /> --max-jobs=2 --index --code-page=1252 --gmapi<br /> --license-file=Freizeitkarte_LUX.license --product-id=1<br /> --family-id=6442 --family-name="Freizeitkarte_LUX"<br /> --series-name="Freizeitkarte_LUX" --description="Freizeitkarte_LUX<br /> (Release 17.02)" --product-version="6442" 6442*.img 6442.TYP<br /> --tdbfile --show-profiles=1<br /> Time started: Sun Feb 05 16:10:10 CET 2017<br /> Number of MapFailedExceptions: 0<br /> Number of ExitExceptions: 0<br /> Time finished: Sun Feb 05 16:10:12 CET 2017<br /> Total time taken: 1858ms<br /><br /> Am I doing something wrong or is this a 'defect' in the newly<br /> implemented gmapi option ?<br /><br /> Thanks for helping<br /> Patrik<br /><br /><br /><hr /><br /> mkgmap-dev mailing list<br /> mkgmap-dev@lists.mkgmap.org.uk<br /> <a
href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></blockquote><br /><br /><hr /><br /> mkgmap-dev mailing list<br /> mkgmap-dev@lists.mkgmap.org.uk<br /> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br /></blockquote><br /><hr /><br /> mkgmap-dev mailing list<br /> mkgmap-dev@lists.mkgmap.org.uk<br /> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br /></blockquote><br /><hr /><br /> mkgmap-dev mailing list<br /> mkgmap-dev@lists.mkgmap.org.uk<br /> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br /></blockquote><br /><hr /><br />mkgmap-dev mailing list<br />mkgmap-dev@lists.mkgmap.org.uk<br /><a
href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br /></pre></blockquote></div></body></html>