October 2023 - mkgmap-dev - The mkgmap lists

Commit r4916: sortResource_v3.patch (with updated date in comment) by Ticker Berkin
by svn commit 13 Oct '23

13 Oct '23

Version mkgmap-r4916 was committed by gerd on Fri, 13 Oct 2023 sortResource_v3.patch (with updated date in comment) by Ticker Berkin "Last year it was reported that string ordering with the '#' character was incorrect. This was because, in the sort/cp*.txt files, the relevant line with the '#' was taken as a comment." The patch also required a change in a unit test which tests the version number. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4916

1 0

Fix and augment sort definitions
by Gerd Petermann 12 Oct '23

12 Oct '23

Hi Ticker, see https://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3948 https://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3949 the sortResource.patch reverts these changes. In Mapsource the results are a bit better with your patch. I'll try again with my Oregon later. Gerd

3 15

Contour lines without elevation. What shoul mkgmap do?
by Gerd Petermann 11 Oct '23

11 Oct '23

Hi all, in a private mail I was informed that mkgmap crashes when polish input contains no label for types which are considered as contour line data like this [POLYLINE] Type=0x20 Data0=(51.5300781,-0.0988259), (51.5305501,-0.0989852), (51.5311576,-0.0992174) [END] The same data was handled without problem before r4907. As a quick hack I've added a null check to restore the old behaviour, but I wonder if it would be better to stop with an error message or maybe ignore contour line data when no elevation is given in the label? I guess the same problem can happen with OSM data when a style uses the line types 0x20 .. 0x25 . Should I add checks to warn when these line types are used without a proper label that can be elevation data? Gerd

5 4

Re: [mkgmap-dev] Contour lines without elevation. What shoul mkgmap do?
by Thomas Morgenstern 11 Oct '23

11 Oct '23

For my understanding is a missing elevation -value clearly a error. mkgmap shouldgive a hint and rejekt this line. 0x20...0x22 without value is not compatible with Garmin. See also Usermanual for cgpsmapper . regards thomas

1 0

Commit r4915: Polish format (*.mp) Don't crash with NullPointerException when a contour line has no label
by svn commit 11 Oct '23

11 Oct '23

Version mkgmap-r4915 was committed by gerd on Wed, 11 Oct 2023 Polish format (*.mp) Don't crash with NullPointerException when a contour line has no label This is a quick hack to restore the old behaviour before r4907. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4915

1 0

Compiling INFO.XML file
by helter skelter 10 Oct '23

10 Oct '23

Hello guys When I create the map for Basecamp, I get a folder under ProgramData\Garmin\Maps with a INFO.XML file inside. There are many fields, but I am able to fill only some of them. Could you please tell me what options I need to use in Mkgmap to fill these fields ? <Name>OSM map</Name> <DataVersion>100</DataVersion> <DataFormat>Original</DataFormat> ... <SubProduct> <Name>series name</Name> ... <BaseMap>osmmap</BaseMap> ... </SubProduct> Are they really important for Basecamp map or for the Garmin one ? Here are the options I am actually using: --mapname= --family-id= --copyright-file= --country-name= --index --series-name= --description= --overview-mapname= --style-file= --style= --keep-going --output-dir= --nsis --tdbfile --remove-short-arcs --merge-lines --draw-priority= --show-profiles= --gmapsupp --gmapi -c Many thanks Cheers Diego ________________________________ Da: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> per conto di mkgmap-dev-request(a)lists.mkgmap.org.uk <mkgmap-dev-request(a)lists.mkgmap.org.uk> Inviato: domenica 8 ottobre 2023 11:00 A: mkgmap-dev(a)lists.mkgmap.org.uk <mkgmap-dev(a)lists.mkgmap.org.uk> Oggetto: mkgmap-dev Digest, Vol 183, Issue 7 Send mkgmap-dev mailing list submissions to mkgmap-dev(a)lists.mkgmap.org.uk To subscribe or unsubscribe via the World Wide Web, visit https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev or, via email, send a message with subject or body 'help' to mkgmap-dev-request(a)lists.mkgmap.org.uk You can reach the person managing the list at mkgmap-dev-owner(a)lists.mkgmap.org.uk When replying, please edit your Subject line so it is more specific than "Re: Contents of mkgmap-dev digest..."

3 2

Gaps in surfaces
by Forstner Michael 08 Oct '23

08 Oct '23

Hello, in some areas, gaps may appear (see attachment). In OSM, however, the surfaces are connected and the nodes have the same coordinates. There should be no rounding errors. It will therefore be a bug in mkgmap. I ask for correction. Thank you! Best regards, Michael

3 19

Commit r4914: no_hp-overflow_v2.patch by Ticker Berkin (with modified javadoc and updated unit tests):
by svn commit 08 Oct '23

08 Oct '23

Version mkgmap-r4914 was committed by gerd on Sun, 08 Oct 2023 no_hp-overflow_v2.patch by Ticker Berkin (with modified javadoc and updated unit tests): Improve conversion between degrees and mapunit or high precision values. This fixes spurious artifacts (gaps or zig-zagging) and typically reduces RGN size slightly. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4914

1 0

Commit r4913: adapt test values to reflect recent changes. RGN sizes decreesed a bit with the changes in r4909
by svn commit 07 Oct '23

07 Oct '23

Version mkgmap-r4913 was committed by gerd on Sat, 07 Oct 2023 adapt test values to reflect recent changes. RGN sizes decreesed a bit with the changes in r4909 http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4913

1 0