- mkgmap-dev - The mkgmap lists

Commit r4903: fix typo in comment, no functional change
by svn commit 30 May '22

30 May '22

Version mkgmap-r4903 was committed by gerd on Mon, 30 May 2022 fix typo in comment, no functional change http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4903

1 0

Re: [mkgmap-dev] Name Capitalisation with Mkgmap
by dfjkman＠gmail.com 26 May '22

26 May '22

Hi John, I think you may be right. Strangely my Etrex 32x gets Shiwa Ng’andu correct but Mchingi is still ‘Scottish’. I did some investigating with a commercially available map from Tracks4Africa for Garmin devices produced about a year ago and found that in BaseCamp Shiwa Ng’andu is displayed incorrectly but Mchingi, the town in Malawi, is displayed correctly. Tracks4Africa maps are produced using information provided by users, mainly South African, who upload gps tracks and POIs from their overland trips and as a result I have found many errors in place name spelling, Mchingi is a case in point, the actual POI is spelt correctly but the traced residential area around is spelt Machingi. For those interested the ‘M’ of Mchingi is pronounced ‘mm’. According to the copyright info in the Tracks4Africa map the map is created using gps-mapper. Kind regards, Dave From: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> On Behalf Of John Thorn Sent: 25 May 2022 19:58 To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 166, Issue 11 Hi Folks, I think it is Basecamp trying to be clever, thinking it is a Scottish name. I traced an item : McDuffs Monument in the .mp file; MCDUFFS MONUMENT in the compiled .img file from MKGMAP but displayed as McDuffs Monument in Basecamp. Kind regards, John On Wed, 25 May 2022 at 18:08, <mkgmap-dev-request(a)lists.mkgmap.org.uk <mailto:mkgmap-dev-request@lists.mkgmap.org.uk> > wrote: Send mkgmap-dev mailing list submissions to mkgmap-dev(a)lists.mkgmap.org.uk <mailto:mkgmap-dev@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 <mailto:mkgmap-dev-request@lists.mkgmap.org.uk> You can reach the person managing the list at mkgmap-dev-owner(a)lists.mkgmap.org.uk <mailto:mkgmap-dev-owner@lists.mkgmap.org.uk> When replying, please edit your Subject line so it is more specific than "Re: Contents of mkgmap-dev digest..." Today's Topics: 1. Name Capitalisation with Mkgmap (dfjkman(a)gmail.com <mailto:dfjkman@gmail.com> ) ---------- Forwarded message ---------- From: <dfjkman(a)gmail.com <mailto:dfjkman@gmail.com> > To: <mkgmap-dev(a)lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> > Cc: Bcc: Date: Wed, 4 May 2022 09:29:40 +0200 Subject: [mkgmap-dev] Name Capitalisation with Mkgmap Hi, I have noticed that in maps I compile of Zambia some of the place names have incorrect capitalization. I complied a map using the most basic options with both splitter and mkgmap to make sure it had nothing to do with any of my styles or options, the commands were as follows: java -jar -Xmx2g ` C:\Users\Dave\Documents\Maps\Utils\splitter\splitter.jar ` "C:\Users\Dave\Documents\Maps\Data\zambia-latest.osm.pbf" ` --output=pbf ` --output-dir="C:\Users\Dave\Documents\Maps\Temp\Split_files" Java -jar -Xmx7g ` C:\Users\Dave\Documents\Maps\Utils\mkgmap\mkgmap.jar ` --gmapi ` --output-dir="C:\Users\Dave\Documents\Maps\Temp\Output Map" ` -c "C:\Users\Dave\Documents\Maps\Temp\Split_files\template.args" I have attached screenshots from BaseCamp to indicate the problem. The first is just over the border in Malawi, the Mchingi Forest Reserve, which is shown as McHingi, the ‘H’ should not be capitalised. There is also a town named Mchingi not shown and a mountain with the same name not mapped in OSM. The second is of a place in Zambia called Shiwa Ng’andu, shown as Shiwa Ng’Andu, again the ‘A’ should not be capitalised, the apostrophe here indicates how the word Ng’andu is pronounced, a glottal stop. There used to be more examples of the glottal stop apostrophes in Zambian place names such as the town M’kushi but it seems that this practice is being dropped and the town name is now officially spelt Mkushi as is the district and river. In both these cases I have checked and the OSM data is correct, so I am not sure if it is something hard coded in mkgmap or there is a way to correct it with options. Thanks, Dave _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

2 1

Re: [mkgmap-dev] mkgmap-dev Digest, Vol 166, Issue 11
by John Thorn 25 May '22

25 May '22

Hi Folks, I think it is Basecamp trying to be clever, thinking it is a Scottish name. I traced an item : McDuffs Monument in the .mp file; MCDUFFS MONUMENT in the compiled .img file from MKGMAP but displayed as McDuffs Monument in Basecamp. Kind regards, John On Wed, 25 May 2022 at 18:08, <mkgmap-dev-request(a)lists.mkgmap.org.uk> wrote: > 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..." > Today's Topics: > > 1. Name Capitalisation with Mkgmap (dfjkman(a)gmail.com) > > > > ---------- Forwarded message ---------- > From: <dfjkman(a)gmail.com> > To: <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Bcc: > Date: Wed, 4 May 2022 09:29:40 +0200 > Subject: [mkgmap-dev] Name Capitalisation with Mkgmap > > Hi, > > > > I have noticed that in maps I compile of Zambia some of the place names > have incorrect capitalization. I complied a map using the most basic > options with both splitter and mkgmap to make sure it had nothing to do > with any of my styles or options, the commands were as follows: > > > > java -jar -Xmx2g ` > > > C:\Users\Dave\Documents\Maps\Utils\splitter\splitter.jar ` > > > "C:\Users\Dave\Documents\Maps\Data\zambia-latest.osm.pbf" ` > > --output=pbf ` > > > --output-dir="C:\Users\Dave\Documents\Maps\Temp\Split_files" > > > > Java -jar -Xmx7g ` > > C:\Users\Dave\Documents\Maps\Utils\mkgmap\mkgmap.jar ` > > --gmapi ` > > --output-dir="C:\Users\Dave\Documents\Maps\Temp\Output Map" > ` > > -c > "C:\Users\Dave\Documents\Maps\Temp\Split_files\template.args" > > > > I have attached screenshots from BaseCamp to indicate the problem. > > > > The first is just over the border in Malawi, the Mchingi Forest Reserve, > which is shown as McHingi, the ‘H’ should not be capitalised. There is also > a town named Mchingi not shown and a mountain with the same name not mapped > in OSM. > > > > The second is of a place in Zambia called Shiwa Ng’andu, shown as Shiwa > Ng’Andu, again the ‘A’ should not be capitalised, the apostrophe here > indicates how the word Ng’andu is pronounced, a glottal stop. There used to > be more examples of the glottal stop apostrophes in Zambian place names > such as the town M’kushi but it seems that this practice is being dropped > and the town name is now officially spelt Mkushi as is the district and > river. > > > > In both these cases I have checked and the OSM data is correct, so I am > not sure if it is something hard coded in mkgmap or there is a way to > correct it with options. > > > > Thanks, > > Dave > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

1 0

generate-sea option and faster-mp changes
by Ticker Berkin 13 May '22

13 May '22

Hi Gerd I've just rebuilt britain-and-ireland-latest.osm.pbf with the current trunk and find that many tiles on the coast have flooded rectangles. The coastline is all correct and these flooded area are normally well inland and unrelated to where the coastline crosses the tile boundary. I use option --generate-sea="multipolygon,extend-sea-sectors,close-gaps=750" and this worked fine up to about a year ago - I've only just noticed the problem. Cutting this from a suitable area (Wales, UK, Britain, Europe etc) 74220030: 2408448,-331776 to 2430976,-196608 # : 51.679688,-7.119141 to 52.163086,-4.218750 and building with minimal options plus above and default style should demonstrate the problem. There are also extra error messages starting ... 030.osm.pbf: Multipolygon generated SeaPolygonRelation [nat... in the log file, which I attach I think it is related to the faster-mp changes and the MP structure SeaGenerator created. This has 1 outer (the tile) and all bits of land are inners, including land touching the edge of the tile. I've attached a patch for an enhanced version of SeaGenerator that distinguishes between land/sea areas that touch the edge and true [anti-]islands and only use MP processing for the islands. With this, tiles are correct. It also has other benefits: It is clearer in what is happening, doesn't do a lot of pointless tagging of ways that will joined to become polygons, etc Ticker

2 7

Commit r4902: slightly modified genSeaEnhance_v3.patch by Ticker Berkin:
by svn commit 13 May '22

13 May '22

Version mkgmap-r4902 was committed by gerd on Fri, 13 May 2022 slightly modified genSeaEnhance_v3.patch by Ticker Berkin: "I've attached a patch for an enhanced version of SeaGenerator that distinguishes between land/sea areas that touch the edge and true [anti-]islands and only use MP processing for the islands. With this, tiles are correct. It also has other benefits: It is clearer in what is happening, doesn't do a lot of pointless tagging of ways that will joined to become polygons, etc" http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4902

1 0

Commit r4901: fix bug in code which is used to generate precompSea.zip
by svn commit 13 May '22

13 May '22

Version mkgmap-r4901 was committed by gerd on Fri, 13 May 2022 fix bug in code which is used to generate precompSea.zip Tiles with complex coastlines contained ways with tag natural=sea outside of the tile bounds. Not sure if this cause wrong maps, it seems that the downloadable sea-latest.zip on the mkgmap site was created with an older version of mkgmap which doesn't show this bug. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4901

1 0

Name Capitalisation with Mkgmap
by dfjkman＠gmail.com 04 May '22

04 May '22

Hi, I have noticed that in maps I compile of Zambia some of the place names have incorrect capitalization. I complied a map using the most basic options with both splitter and mkgmap to make sure it had nothing to do with any of my styles or options, the commands were as follows: java -jar -Xmx2g ` C:\Users\Dave\Documents\Maps\Utils\splitter\splitter.jar ` "C:\Users\Dave\Documents\Maps\Data\zambia-latest.osm.pbf" ` --output=pbf ` --output-dir="C:\Users\Dave\Documents\Maps\Temp\Split_files" Java -jar -Xmx7g ` C:\Users\Dave\Documents\Maps\Utils\mkgmap\mkgmap.jar ` --gmapi ` --output-dir="C:\Users\Dave\Documents\Maps\Temp\Output Map" ` -c "C:\Users\Dave\Documents\Maps\Temp\Split_files\template.args" I have attached screenshots from BaseCamp to indicate the problem. The first is just over the border in Malawi, the Mchingi Forest Reserve, which is shown as McHingi, the 'H' should not be capitalised. There is also a town named Mchingi not shown and a mountain with the same name not mapped in OSM. The second is of a place in Zambia called Shiwa Ng'andu, shown as Shiwa Ng'Andu, again the 'A' should not be capitalised, the apostrophe here indicates how the word Ng'andu is pronounced, a glottal stop. There used to be more examples of the glottal stop apostrophes in Zambian place names such as the town M'kushi but it seems that this practice is being dropped and the town name is now officially spelt Mkushi as is the district and river. In both these cases I have checked and the OSM data is correct, so I am not sure if it is something hard coded in mkgmap or there is a way to correct it with options. Thanks, Dave

1 0

Re: [mkgmap-dev] Compile error
by Dave Swarthout 03 May '22

03 May '22

I don't create an overview map. No tiles show up with zero size nor are any of the 56 tiles larger than about 159,000 nodes. Carlos has offered a patch to indicate the problem tile but I'm on a Windows 10 system and am not willing to set up a Linux environment just to patch my mkgmap program. Is there a debugging tool or method that you can suggest? On Mon, May 2, 2022 at 11:10 AM Gerd Petermann <gpetermann_muenchen(a)hotmail.com> wrote: > > Hi Dave, > > I would expect a tile with 0 bytes. Maybe you get this message for the overview map? > > Gerd > > ________________________________________ > Von: Dave Swarthout <daveswarthout(a)gmail.com> > Gesendet: Montag, 2. Mai 2022 20:02 > An: Gerd Petermann > Cc: Development list for mkgmap > Betreff: Re: [mkgmap-dev] Compile error > > Thanks, Gerd, > > I get the same error when using the default syle. In DJS.cfg, I placed this line: > style-file=C:\Users\Alask\Documents\mkgmap\examples\styles\default. That is correct usage, right? > > Another list member told me to look for the offending tile in order to manually split it, however, all the tiles look alike to me in terms of size. How would I tell which tile is the "bad one" that's causing this RGN error? > > You mentioned adjusting some mkgmap parameters that would reduce the size and/or complexity of the map I'm trying to create. The descriptive text in the Options file for directives about processing lines and polygons doesn't make clear how to reduce the amount of information they handle— can you offer any suggestions? > > Thanks, > > Dave > > > > On Mon, May 2, 2022 at 9:23 AM Gerd Petermann <gpetermann_muenchen(a)hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: > Hi Dave, > > the max-nodes value is already very small, so maybe something in mkgmap goes very wrong. > We probably need the input file (*.o5m) for the tile that fails and the style unless you can reproduce the > problem also with the default style. > > Gerd > > ________________________________________ > Von: Dave Swarthout <daveswarthout(a)gmail.com<mailto:daveswarthout@gmail.com>> > Gesendet: Montag, 2. Mai 2022 18:08 > An: Gerd Petermann > Cc: Development list for mkgmap > Betreff: Re: [mkgmap-dev] Compile error > > Reducing the node count means I was adjusting the max-nodes value; I had been using a value of 160,000 for max-nodes but after getting that error message, I tried running splitter with max-nodes=120,000 and 100,000 nodes but that had zero effect on the error message. There were more tiles generated by splitter but the same error resulted. > > I've attached my splitter logs and the DJS.CFG file > > Thanks for the help > > On Mon, May 2, 2022 at 1:42 AM Gerd Petermann <gpetermann_muenchen(a)hotmail.com<mailto:gpetermann_muenchen@hotmail.com><mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>>> wrote: > Hi Dave, > > what do you mean with "I've tried reducing the size of the node count but that had no effect"? A smaller --max-nodes value for splitter should always have an effect: > More / different tiles. Maybe it just didn't change the size of the problematic tile? > > So, if you don't want to "reduce the amount of information included in the map" which means > changing the style or options like --reduce-points, --levels etc, your only option is to tell splitter to produce smaller tiles. > That is done with the --max-nodes option or maybe allow trimming if the problematic tile contains a huge area with sea only. > > Can't say much more without knowing the content of the problematic tile and content of DJS.cfg. > > Gerd > > > > ________________________________________ > Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>>> im Auftrag von Dave Swarthout <daveswarthout(a)gmail.com<mailto:daveswarthout@gmail.com><mailto:daveswarthout@gmail.com<mailto:daveswarthout@gmail.com>>> > Gesendet: Sonntag, 1. Mai 2022 02:06 > An: Development list for mkgmap > Betreff: [mkgmap-dev] Compile error > > Hi, > > I'm not on this list anymore but I'm having a problem with mkgmap that I'm unable to understand or fix. > > I'm getting this error all the time now. "The RGN section of the map or tile is too big. The maximum size is 16777215 bytes. Try splitting the map into smaller tiles or reducing the amount of information included in the map." > > I've tried reducing the size of the node count but that had no effect. Here's my command line: > > java -Xmx4000m -jar mkgmap.jar -c DJS.cfg --latin1 --family-id=24566 --name-tag-list=name,alt_name,loc_name,int_name --description="Eugene" "C:\Users\Alask\Downloads\Maps\Eugene.osm" "C:\Users\Alask\Dropbox (Personal)\Mapping\24983djs.TYP" > > Splitter ends normally with 56 areas for a 1.5 GB input file > > Any ideas? > > Please address all replies to me as well as the list membership because I was removed from this list for having "too many bounces", whatever that is but I need a solution to this problem. > > Thanks in advance > > -- > Dave Swarthout > Homer, Alaska > Chiang Mai, Thailand > Travel Blog at http://dswarthout.blogspot.com > > > -- > Dave Swarthout > Homer, Alaska > Chiang Mai, Thailand > Travel Blog at http://dswarthout.blogspot.com > > > -- > Dave Swarthout > Homer, Alaska > Chiang Mai, Thailand > Travel Blog at http://dswarthout.blogspot.com -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com

3 4

Commit r4900: Show file name when mkgmap stops because the img file get's too big
by svn commit 03 May '22

03 May '22

Version mkgmap-r4900 was committed by gerd on Tue, 03 May 2022 Show file name when mkgmap stops because the img file get's too big ShowFailingTile.patch by Carlos Dávila http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4900

1 0

Compile error
by Dave Swarthout 02 May '22

02 May '22

Hi, I'm not on this list anymore but I'm having a problem with mkgmap that I'm unable to understand or fix. I'm getting this error all the time now. "The RGN section of the map or tile is too big. The maximum size is 16777215 bytes. Try splitting the map into smaller tiles or reducing the amount of information included in the map." I've tried reducing the size of the node count but that had no effect. Here's my command line: java -Xmx4000m -jar mkgmap.jar -c DJS.cfg --latin1 --family-id=24566 --name-tag-list=name,alt_name,loc_name,int_name --description="Eugene" "C:\Users\Alask\Downloads\Maps\Eugene.osm" "C:\Users\Alask\Dropbox (Personal)\Mapping\24983djs.TYP" Splitter ends normally with 56 areas for a 1.5 GB input file Any ideas? Please address all replies to me as well as the list membership because I was removed from this list for having "too many bounces", whatever that is but I need a solution to this problem. Thanks in advance -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com

3 6