Combining maps with differerent charset/code page into one mapset - Supress Warnings -
I use to add readily compiled contourline files to my maps. They are in --latin1 and don't have any information that would be needed to appear in the search index. I will then always get warnings like the following - even though the maps seem to work fine in Mapsource, Basecamp and on my GPS.. /WARNING: input file 73630000.img has different code page 1252// //WARNING: input file 73630000.img has different charset type 10// //WARNING: input files have different code pages// / (e.g. ftp://ftp5.gwdg.de/pub/misc/openstreetmap/openmtbmap/odbl/mtbmonaco.exe - just unzip the .exe - it's lzma packed. there is one "map data" file 63630000.img - one contourlines file 73730000.img - and then a "mapsetx" set of files which excludes the 73730000.img, one "mapsetc" set of files which includes the 7373000.img (well and then one mapsetz which is for installing the contourlines as separate contourlines only map)) Sometimes on bigger maps - mkgmap even crashes while running due to the codepage/charset option - e.g. if I create a map of Europe... Dunno really why this crashes.. start /low /b /wait java -jar -Xms6000M -Xmx10300M c:\openmtbmap\mkgmap.jar %max-jobs% %generate-sea% %precomp-seaxx% %style-file% --nsis %indx% %levels% --adjust-turn-headings --add-pois-to-areas --reduce-point-density=3.4 --reduce-point-density-polygon=6 --housenumbers --link-pois-to-ways --ignore-turn-restrictions --polygon-size-limits="24:16, 23:14, 22:12, 21:11, 20:10, 19:9, 18:8, 17:7, 16:6, 15:5, 14:4, 13:3, 12:2, 11:0, 10:0" --description=openmtbmap_%abr% %showprofile% %locationxx% --route --country-abbr=%abr% --country-name=%country% --mapname=%FID%0000 --family-id=%FID% --product-id=1 --series-name=openmtbmap_%country%_%date% --family-name=mtbmap_%abr%_%date% --tdbfile --overview-mapname=mapsetx --keep-going --area-name="%country%_%date%_openmtbmap.org" -c c:\openmtbmap\maps\template.%countryx% 7*.img>NUL Where could I switch off the warning (in code) -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi Felix
I will then always get warnings like the following - even though the maps seem to work fine in Mapsource, Basecamp and on my GPS.. /WARNING: input file 73630000.img has different code page 1252// //WARNING: input file 73630000.img has different charset type 10// //WARNING: input files have different code pages// / (e.g. ftp://ftp5.gwdg.de/pub/misc/openstreetmap/openmtbmap/odbl/mtbmonaco.exe - just unzip the .exe - it's lzma packed.
In that file it seems that both the .img files have the same code-page and sort-order, so when I specify --code-page=1252 there is no warning.# It certainly could happen though, and as long as there are no symbols in the file with the wrong code-page/sort-order then the map will still work.
Sometimes on bigger maps - mkgmap even crashes while running due to the codepage/charset option - e.g. if I create a map of Europe... Dunno really why this crashes..
What is the crash that you get? If it is because of mismatched code-pages then it is not unexpected, that's why there is a warning. It is just a warning rather than an error, because sometimes there will not be a problem - perhaps I should make it an error. ..Steve
I'll run that through tomorrow or Tuesday and document it better... To bad there is nothing easy to convert the codepage in the map (even though of course contourlines only map has no actual data for search). On 22.06.2014 19:25, Steve Ratcliffe wrote:
Hi Felix
I will then always get warnings like the following - even though the maps seem to work fine in Mapsource, Basecamp and on my GPS.. /WARNING: input file 73630000.img has different code page 1252// //WARNING: input file 73630000.img has different charset type 10// //WARNING: input files have different code pages// / (e.g. ftp://ftp5.gwdg.de/pub/misc/openstreetmap/openmtbmap/odbl/mtbmonaco.exe - just unzip the .exe - it's lzma packed.
In that file it seems that both the .img files have the same code-page and sort-order, so when I specify --code-page=1252 there is no warning.# It certainly could happen though, and as long as there are no symbols in the file with the wrong code-page/sort-order then the map will still work.
Sometimes on bigger maps - mkgmap even crashes while running due to the codepage/charset option - e.g. if I create a map of Europe... Dunno really why this crashes..
What is the crash that you get?
If it is because of mismatched code-pages then it is not unexpected, that's why there is a warning. It is just a warning rather than an error, because sometimes there will not be a problem - perhaps I should make it an error.
..Steve
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Sorry for the late answer. I did not yet manage to recompile the Europe map again, but all other geofabrik samples work fine. So I do think the error was somewhere else... As for the warning - please see my other post. I could not yet find any problems related to mixing maps. I still have to check out why for some people the maps show up locked on their device (I will ask them to try out several things like leaving out the contourlines so the mapset/gmapsupp is one single codepage). As soon as I/we can track down the problem of why maps don't appear on some GPS units or why they appear to be locked (on a completely hard reset GPS with no other maps) I think the warning should be taken away if no gmapsupp.img is compiled. As for gmapsupp.img - well there are clearly some bugs as unicode maps do not list on older garmin GPS units in case they are created by mkgmap.jar while they do work as intended (meaning limited with no codepage characters working at all) on old devices. So my advice is for general map compilation. Continue to use --latin1 for all maps in countries where roman/latin script is predominant. Use unicode for maps with other codepages even if there are users which might have old generation devices. Well and I'm not sure yet what to do for countries like China, Korea, Japan where the unicode implementation is currently (well I did not check it out myself really) not yet working because they use characters instead of alphabet... On 22.06.2014 19:25, Steve Ratcliffe wrote:
Hi Felix
I will then always get warnings like the following - even though the maps seem to work fine in Mapsource, Basecamp and on my GPS.. /WARNING: input file 73630000.img has different code page 1252// //WARNING: input file 73630000.img has different charset type 10// //WARNING: input files have different code pages// / (e.g. ftp://ftp5.gwdg.de/pub/misc/openstreetmap/openmtbmap/odbl/mtbmonaco.exe - just unzip the .exe - it's lzma packed.
In that file it seems that both the .img files have the same code-page and sort-order, so when I specify --code-page=1252 there is no warning.# It certainly could happen though, and as long as there are no symbols in the file with the wrong code-page/sort-order then the map will still work.
Sometimes on bigger maps - mkgmap even crashes while running due to the codepage/charset option - e.g. if I create a map of Europe... Dunno really why this crashes..
What is the crash that you get?
If it is because of mismatched code-pages then it is not unexpected, that's why there is a warning. It is just a warning rather than an error, because sometimes there will not be a problem - perhaps I should make it an error.
..Steve
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
participants (2)
-
Felix Hartmann -
Steve Ratcliffe