[Patch] set map-version in img header
Hi all, the attached patch implements new option map-version: --map-version=major.minor The map version is written into the header of each *.img file at offset 8 and 9. Defailt is 0.0. Both major and minor values must be between 0 and 255 (including). Example: --map-version=1.7 (same as --map-version=01.07) A binary based on r3753 is here: http://files.mkgmap.org.uk/download/326/mkgmap.jar I seem to have no Garmin software that displays this version, so I don't know for sure what the meaning is. Please suggest better option name or description if you know more. Gerd
Hi Gerd, your patch seems to working correctly, see attached screenshot form chartplotter. I have noticed, that product-version uses other format, product-version=120 is interpreted as 1.20 by Map Product Manager. Currently product version goes to TDB and info.xml, I think it can be used for gmapsupp.img header too, unless anyone knows distinction between these 2 values. Putting version into tiles and preview probably isn't useful, but does no harm anyway. -- Best regards, Andrzej
Hi Andrzej, thanks for the feedback. I'll have a 2nd look at --product-version. The default value is documented as 1 but in the java code the value 100 is used. So, I can probably use major = productVersion / 100; minor = productVersion % 100; Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Dienstag, 17. Januar 2017 14:44:25 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi Gerd, your patch seems to working correctly, see attached screenshot form chartplotter. I have noticed, that product-version uses other format, product-version=120 is interpreted as 1.20 by Map Product Manager. Currently product version goes to TDB and info.xml, I think it can be used for gmapsupp.img header too, unless anyone knows distinction between these 2 values. Putting version into tiles and preview probably isn't useful, but does no harm anyway. -- Best regards, Andrzej
Hi Gerd, you could correct description for --product-version in help. Something like: default value is 100 which indicate version 1.00. -- Best regards, Andrzej
Hi Gerd, I could not test it on my GPS, yet. But your option works well for my map on Homeport. I set option --map-version=17.01 and Homeport shows v17.01 GMapTool also reports correct version: Datei: G:/garmin/gmapsupp.img, Länge 1940029440 Header: 17.01.2017 18:09:28, DSKIMG, XOR 00, V 17.01, Ms 0 Mapset: OpenSeaMap_EuCentral Fat: 400h - 600h - 80000h, Block 32768 Maps: 322, Subdateien 962 One more question: Could your perhaps also implement an option --marine to set marine header? Currently I have to patch headers using this tool: https://github.com/OpenSeaMap/garmin/tree/master/gmarine But this is slow. It would be much better to have an option for that. Thanks Von: Gerd Petermann Gesendet: Sonntag, 15. Januar 2017 09:47 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] [Patch] set map-version in img header Hi all, the attached patch implements new option map-version: --map-version=major.minor The map version is written into the header of each *.img file at offset 8 and 9. Defailt is 0.0. Both major and minor values must be between 0 and 255 (including). Example: --map-version=1.7 (same as --map-version=01.07) A binary based on r3753 is here: http://files.mkgmap.org.uk/download/326/mkgmap.jar I seem to have no Garmin software that displays this version, so I don't know for sure what the meaning is. Please suggest better option name or description if you know more. Gerd
Hi rheinskipper1000, thanks for testing. Reg. --marine option: Looks simple enough, so yes, that can be done. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Dienstag, 17. Januar 2017 20:26:02 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi Gerd, I could not test it on my GPS, yet. But your option works well for my map on Homeport. I set option --map-version=17.01 and Homeport shows v17.01 GMapTool also reports correct version: Datei: G:/garmin/gmapsupp.img, Länge 1940029440 Header: 17.01.2017 18:09:28, DSKIMG, XOR 00, V 17.01, Ms 0 Mapset: OpenSeaMap_EuCentral Fat: 400h - 600h - 80000h, Block 32768 Maps: 322, Subdateien 962 One more question: Could your perhaps also implement an option --marine to set marine header? Currently I have to patch headers using this tool: https://github.com/OpenSeaMap/garmin/tree/master/gmarine But this is slow. It would be much better to have an option for that. Thanks Von: Gerd Petermann<mailto:GPetermann_muenchen@hotmail.com> Gesendet: Sonntag, 15. Januar 2017 09:47 An: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: [mkgmap-dev] [Patch] set map-version in img header Hi all, the attached patch implements new option map-version: --map-version=major.minor The map version is written into the header of each *.img file at offset 8 and 9. Defailt is 0.0. Both major and minor values must be between 0 and 255 (including). Example: --map-version=1.7 (same as --map-version=01.07) A binary based on r3753 is here: http://files.mkgmap.org.uk/download/326/mkgmap.jar I seem to have no Garmin software that displays this version, so I don't know for sure what the meaning is. Please suggest better option name or description if you know more. Gerd
Hi, I suggest to call this option --custom or --mpc, instead of --marine. The patch sets some value in TRE header, which are used by custom maps created by Garmin's Map Product Creator. Current values used by mkgmap (1,3,17) are like in City Navigator maps. Values for custom map (1,4,23) are quite universal, work for hiking, car and marine GPS. Real marine maps uses again some other values, for example (0,6,29). I think mkgmap can switch to values (1,4,23) for default and maybe support option --city-navigator or --car-route to set values (1,3,17). -- Best regards, Andrzej
Thank you for clarifying this. An option to set these bytes to 1,4,23 would be sufficient for me. Of course I don´t mind the name of the option. Thanks in advance for implementing. Von: Andrzej Popowski Gesendet: Dienstag, 17. Januar 2017 20:58 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, I suggest to call this option --custom or --mpc, instead of --marine. The patch sets some value in TRE header, which are used by custom maps created by Garmin's Map Product Creator. Current values used by mkgmap (1,3,17) are like in City Navigator maps. Values for custom map (1,4,23) are quite universal, work for hiking, car and marine GPS. Real marine maps uses again some other values, for example (0,6,29). I think mkgmap can switch to values (1,4,23) for default and maybe support option --city-navigator or --car-route to set values (1,3,17). -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi, the attached patch changes the TRE header to 1,4,23 as supposed by Andrzej. A binary based on r3759 is here: http://files.mkgmap.org.uk/download/328/mkgmap.jar I did not test if it has an effect on routing or anything else. If I here no complains I'll commit the change next monday. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 11:07:01 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Thank you for clarifying this. An option to set these bytes to 1,4,23 would be sufficient for me. Of course I don´t mind the name of the option. Thanks in advance for implementing. Von: Andrzej Popowski<mailto:popej@poczta.onet.pl> Gesendet: Dienstag, 17. Januar 2017 20:58 An: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, I suggest to call this option --custom or --mpc, instead of --marine. The patch sets some value in TRE header, which are used by custom maps created by Garmin's Map Product Creator. Current values used by mkgmap (1,3,17) are like in City Navigator maps. Values for custom map (1,4,23) are quite universal, work for hiking, car and marine GPS. Real marine maps uses again some other values, for example (0,6,29). I think mkgmap can switch to values (1,4,23) for default and maybe support option --city-navigator or --car-route to set values (1,3,17). -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Permanent change instead of option? This is OK for me, but AFAIK it can change routing behaviour. So option would be saver. Von: Gerd Petermann Gesendet: Donnerstag, 19. Januar 2017 16:10 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, the attached patch changes the TRE header to 1,4,23 as supposed by Andrzej. A binary based on r3759 is here: http://files.mkgmap.org.uk/download/328/mkgmap.jar I did not test if it has an effect on routing or anything else. If I here no complains I'll commit the change next monday. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 11:07:01 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Thank you for clarifying this. An option to set these bytes to 1,4,23 would be sufficient for me. Of course I don´t mind the name of the option. Thanks in advance for implementing. Von: Andrzej Popowski<mailto:popej@poczta.onet.pl> Gesendet: Dienstag, 17. Januar 2017 20:58 An: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, I suggest to call this option --custom or --mpc, instead of --marine. The patch sets some value in TRE header, which are used by custom maps created by Garmin's Map Product Creator. Current values used by mkgmap (1,3,17) are like in City Navigator maps. Values for custom map (1,4,23) are quite universal, work for hiking, car and marine GPS. Real marine maps uses again some other values, for example (0,6,29). I think mkgmap can switch to values (1,4,23) for default and maybe support option --city-navigator or --car-route to set values (1,3,17). -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
OK, here is v2 which implements option --custom: --custom Write a different TRE header (1,4,23) instead of (1,3,17). Useful for marine maps. Binary: http://files.mkgmap.org.uk/download/329/mkgmap.jar The description is quite cryptic, so please suggest something better. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 17:03:01 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Permanent change instead of option? This is OK for me, but AFAIK it can change routing behaviour. So option would be saver. Von: Gerd Petermann<mailto:GPetermann_muenchen@hotmail.com> Gesendet: Donnerstag, 19. Januar 2017 16:10 An: Development list for mkgmap<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, the attached patch changes the TRE header to 1,4,23 as supposed by Andrzej. A binary based on r3759 is here: http://files.mkgmap.org.uk/download/328/mkgmap.jar I did not test if it has an effect on routing or anything else. If I here no complains I'll commit the change next monday. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 11:07:01 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Thank you for clarifying this. An option to set these bytes to 1,4,23 would be sufficient for me. Of course I don´t mind the name of the option. Thanks in advance for implementing. Von: Andrzej Popowski<mailto:popej@poczta.onet.pl> Gesendet: Dienstag, 17. Januar 2017 20:58 An: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, I suggest to call this option --custom or --mpc, instead of --marine. The patch sets some value in TRE header, which are used by custom maps created by Garmin's Map Product Creator. Current values used by mkgmap (1,3,17) are like in City Navigator maps. Values for custom map (1,4,23) are quite universal, work for hiking, car and marine GPS. Real marine maps uses again some other values, for example (0,6,29). I think mkgmap can switch to values (1,4,23) for default and maybe support option --city-navigator or --car-route to set values (1,3,17). -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Oops, please ignore v2, it was incomplete. Attached is v3 and here is the binary: http://files.mkgmap.org.uk/download/330/mkgmap.jar Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Donnerstag, 19. Januar 2017 17:29:04 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header OK, here is v2 which implements option --custom: --custom Write a different TRE header (1,4,23) instead of (1,3,17). Useful for marine maps. Binary: http://files.mkgmap.org.uk/download/329/mkgmap.jar The description is quite cryptic, so please suggest something better. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 17:03:01 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Permanent change instead of option? This is OK for me, but AFAIK it can change routing behaviour. So option would be saver. Von: Gerd Petermann<mailto:GPetermann_muenchen@hotmail.com> Gesendet: Donnerstag, 19. Januar 2017 16:10 An: Development list for mkgmap<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, the attached patch changes the TRE header to 1,4,23 as supposed by Andrzej. A binary based on r3759 is here: http://files.mkgmap.org.uk/download/328/mkgmap.jar I did not test if it has an effect on routing or anything else. If I here no complains I'll commit the change next monday. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 11:07:01 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Thank you for clarifying this. An option to set these bytes to 1,4,23 would be sufficient for me. Of course I don´t mind the name of the option. Thanks in advance for implementing. Von: Andrzej Popowski<mailto:popej@poczta.onet.pl> Gesendet: Dienstag, 17. Januar 2017 20:58 An: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, I suggest to call this option --custom or --mpc, instead of --marine. The patch sets some value in TRE header, which are used by custom maps created by Garmin's Map Product Creator. Current values used by mkgmap (1,3,17) are like in City Navigator maps. Values for custom map (1,4,23) are quite universal, work for hiking, car and marine GPS. Real marine maps uses again some other values, for example (0,6,29). I think mkgmap can switch to values (1,4,23) for default and maybe support option --city-navigator or --car-route to set values (1,3,17). -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, version 3 works correctly - gmapsupp.img created by mkgmap is directly recognized by chartplotter, no need to patch img. -- Best regards, Andrzej
Hi Andrzej, thanks for testing, I still hesitate because I don't fully understand the meaning of those 3 bytes. The last change was with r1003 (!): http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=1003 Log Message: Reduce off-track distance required to trigger route re-calculation. Changing the magic value in the TRE header from 0xd0401 to 0x110301 reduces the distance you have to wander off-track before the GPS notices and re-calculates the route. I found some hints here: http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/TRE_Subfile_Format I think we talk about the bytes at offset 43-46, esp. 43 and 44: 0x040 3 display priority 0x043 1 0x11; distance for start route recalculation 0x044 1 0x03; draw priority (overrules DP if set inside tdb) Wouldn't it be better to have two distinct options for these values? And what does "Draw Priority" mean in opposite to "Display Priority" which is at offset 0x40 ? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Donnerstag, 19. Januar 2017 20:14:46 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi Gerd, version 3 works correctly - gmapsupp.img created by mkgmap is directly recognized by chartplotter, no need to patch img. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, I call these values TRE parameters. They are 3 bytes at offsets 0x43, 0x44, 0x45. I'm not sure, what is the real meaning of parameters. Same guesses are that it indicate routable/non routable map, general display priority, some parameters for navigation, general map type. Info about faster routing probably comes form cgpsmapper. Table on OSM wiki looks wrong. Byte 0x40 is priority, I don't know if 3 byte is used, single byte works for me. Beside this priority, TRE parameters influence priority too, but differently on different GPS. It is like some GPS display City Navigator map over topo, regardless of draw priority in byte 0x40. On Garmin maps byte 0x43 gets values 0 or 1, Byte 0x44 gets values 3-4-6, byte 0x45 some values in range 1-43. Wiki shows it in reversed order. Last byte decide if map is visible in chartplotters, so probably define map type. My idea is simply to copy values from original Garmin's map. So now mkgmap is using City Navigator parameters and option sets custom MPC map ( https://developer.garmin.com/map-product-creator/overview/ ). You could set 3 values in option directly, but I'm not sure if it will help. Probably anybody who want to manipulate these values is able to use GMapTool or other patching programs to change it in img. -- Best regards, Andrzej
Hi Andrzej, thanks for the hints, I've changed the description of the option a little bit but kept the java code for r3764. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Freitag, 20. Januar 2017 11:40:50 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi Gerd, I call these values TRE parameters. They are 3 bytes at offsets 0x43, 0x44, 0x45. I'm not sure, what is the real meaning of parameters. Same guesses are that it indicate routable/non routable map, general display priority, some parameters for navigation, general map type. Info about faster routing probably comes form cgpsmapper. Table on OSM wiki looks wrong. Byte 0x40 is priority, I don't know if 3 byte is used, single byte works for me. Beside this priority, TRE parameters influence priority too, but differently on different GPS. It is like some GPS display City Navigator map over topo, regardless of draw priority in byte 0x40. On Garmin maps byte 0x43 gets values 0 or 1, Byte 0x44 gets values 3-4-6, byte 0x45 some values in range 1-43. Wiki shows it in reversed order. Last byte decide if map is visible in chartplotters, so probably define map type. My idea is simply to copy values from original Garmin's map. So now mkgmap is using City Navigator parameters and option sets custom MPC map ( https://developer.garmin.com/map-product-creator/overview/ ). You could set 3 values in option directly, but I'm not sure if it will help. Probably anybody who want to manipulate these values is able to use GMapTool or other patching programs to change it in img. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Option --map-version does not work anymore in this release. Von: Gerd Petermann Gesendet: Donnerstag, 19. Januar 2017 18:11 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Oops, please ignore v2, it was incomplete. Attached is v3 and here is the binary: http://files.mkgmap.org.uk/download/330/mkgmap.jar Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Donnerstag, 19. Januar 2017 17:29:04 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header OK, here is v2 which implements option --custom: --custom Write a different TRE header (1,4,23) instead of (1,3,17). Useful for marine maps. Binary: http://files.mkgmap.org.uk/download/329/mkgmap.jar The description is quite cryptic, so please suggest something better. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 17:03:01 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Permanent change instead of option? This is OK for me, but AFAIK it can change routing behaviour. So option would be saver. Von: Gerd Petermann<mailto:GPetermann_muenchen@hotmail.com> Gesendet: Donnerstag, 19. Januar 2017 16:10 An: Development list for mkgmap<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, the attached patch changes the TRE header to 1,4,23 as supposed by Andrzej. A binary based on r3759 is here: http://files.mkgmap.org.uk/download/328/mkgmap.jar I did not test if it has an effect on routing or anything else. If I here no complains I'll commit the change next monday. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von rheinskipper1000@gmx.de <rheinskipper1000@gmx.de> Gesendet: Donnerstag, 19. Januar 2017 11:07:01 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Thank you for clarifying this. An option to set these bytes to 1,4,23 would be sufficient for me. Of course I don´t mind the name of the option. Thanks in advance for implementing. Von: Andrzej Popowski<mailto:popej@poczta.onet.pl> Gesendet: Dienstag, 17. Januar 2017 20:58 An: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, I suggest to call this option --custom or --mpc, instead of --marine. The patch sets some value in TRE header, which are used by custom maps created by Garmin's Map Product Creator. Current values used by mkgmap (1,3,17) are like in City Navigator maps. Values for custom map (1,4,23) are quite universal, work for hiking, car and marine GPS. Real marine maps uses again some other values, for example (0,6,29). I think mkgmap can switch to values (1,4,23) for default and maybe support option --city-navigator or --car-route to set values (1,3,17). -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi, use product-version instead, it puts version into header of gmapsupp.img. Works correctly in patch version 3. -- Best regards, Andrzej
Thank you. --product-version=1701 produces v17.01 on my GPS. --custom also works fine. Now I can make maps for marine devices without using additional tools. Von: Andrzej Popowski Gesendet: Donnerstag, 19. Januar 2017 20:35 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] [Patch] set map-version in img header Hi, use product-version instead, it puts version into header of gmapsupp.img. Works correctly in patch version 3. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Andrzej Popowski -
Gerd Petermann -
rheinskipper1000＠gmx.de