
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

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@lists.mkgmap.org.uk> im Auftrag von Dave Swarthout <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

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@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@lists.mkgmap.org.uk> im Auftrag von Dave Swarthout <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

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@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@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@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Dave Swarthout <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

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@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@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@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@lists.mkgmap.org.uk<mailto: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Dave Swarthout < 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

Failing tile should be 0 bytes size. Regarding this question, in the past mkgmap showed the tile that was failing to compile, but this feature was removed some time ago. I use a patched version which re-implements it (see attached patch). El 2/5/22 a las 20:02, Dave Swarthout escribió:
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?

@Carlos, Thank you. I'm running mkgmap on a Windows 10 system. Installing a Linux-style environment so I can patch mkgmap is not something I want to do in order to get my maps to compile. Dave On Mon, May 2, 2022 at 11:31 AM Carlos Dávila <carlos@alternativaslibres.org> wrote:
Failing tile should be 0 bytes size. Regarding this question, in the past mkgmap showed the tile that was failing to compile, but this feature was removed some time ago. I use a patched version which re-implements it (see attached patch).
El 2/5/22 a las 20:02, Dave Swarthout escribió:
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?_______________________________________________
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com
participants (3)
-
Carlos Dávila
-
Dave Swarthout
-
Gerd Petermann