Re: [mkgmap-dev] Compile error

[Gerd Petermann]

Hi Dave,

I've already committed the patch from Carlos with r4900, but I doubt that the 
improved message
helps in a case of "I can't see the forest for the trees" ;)

Gerd


Von: Dave Swarthout 
Gesendet: Dienstag, 3. Mai 2022 07:43
An: Gerd Petermann
Cc: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Compile error

OMG!

I copied parts of my batch file for Thailand maps to make this batch
file when I came back to the U.S. but forgot to use the splitter
output file as inputs. I never noticed my omission. It works fine now:

java -Xmx4000m -jar mkgmap.jar -c DJS.cfg --latin1 --family-id=24566
--name-tag-list=name,alt_name,loc_name,int_name --description="Eugene"
splitter\*.o5m "C:\Users\Alask\Dropbox
(Personal)\Mapping\24983djs.TYP"

Sorry for wasting your time. I must say, however, that the error
message I got didn't help diagnose or solve that problem. Maybe that
could be looked at and improved.

Thanks, Gerd.

On Mon, May 2, 2022 at 10:22 PM  wrote:
>
> Hi Dave,
>
> I just double checked what you wrote before and it seems you feed mkgmap with
> the large file C:\Users\alask\Downloads\Maps\Eugene.osm ?
> You also posted a log that shows that you use splitter with the same file.
> So, change your mkgmap command to actually use the output from splitter and 
> your
> problem shoud be solved. There is probably no need to use the small 
> --max-nodes value.
>
> Gerd
>
>
> 
> Von: Dave Swarthout 
> Gesendet: Montag, 2. Mai 2022 23:13
> An: Gerd Petermann
> Cc: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Compile error
>
> 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
>  wrote:
> >
> > Hi Dave,
> >
> > I would expect a tile with 0 bytes. Maybe you get this message for the 
> > overview map?
> >
> > Gerd
> >
> > ________________
> > Von: Dave Swarthout 
> > 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 
> > mailto:gpetermann_muenc...@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 
> > mailto:daveswarth...@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 A

Re: [mkgmap-dev] Compile error

[Dave Swarthout]

I just saw your other email that the next release of mkgmap includes
Carlos's patch. I've downloaded it.

Thanks again to everyone on this list.

Dave

On Mon, May 2, 2022 at 10:43 PM Dave Swarthout  wrote:
>
> OMG!
>
> I copied parts of my batch file for Thailand maps to make this batch
> file when I came back to the U.S. but forgot to use the splitter
> output file as inputs. I never noticed my omission. It works fine now:
>
> java -Xmx4000m -jar mkgmap.jar -c DJS.cfg --latin1 --family-id=24566
> --name-tag-list=name,alt_name,loc_name,int_name --description="Eugene"
> splitter\*.o5m "C:\Users\Alask\Dropbox
> (Personal)\Mapping\24983djs.TYP"
>
> Sorry for wasting your time. I must say, however, that the error
> message I got didn't help diagnose or solve that problem. Maybe that
> could be looked at and improved.
>
> Thanks, Gerd.
>
> On Mon, May 2, 2022 at 10:22 PM  wrote:
> >
> > Hi Dave,
> >
> > I just double checked what you wrote before and it seems you feed mkgmap 
> > with
> > the large file C:\Users\alask\Downloads\Maps\Eugene.osm ?
> > You also posted a log that shows that you use splitter with the same file.
> > So, change your mkgmap command to actually use the output from splitter and 
> > your
> > problem shoud be solved. There is probably no need to use the small 
> > --max-nodes value.
> >
> > Gerd
> >
> >
> > ____________________
> > Von: Dave Swarthout 
> > Gesendet: Montag, 2. Mai 2022 23:13
> > An: Gerd Petermann
> > Cc: Development list for mkgmap
> > Betreff: Re: [mkgmap-dev] Compile error
> >
> > 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
> >  wrote:
> > >
> > > Hi Dave,
> > >
> > > I would expect a tile with 0 bytes. Maybe you get this message for the 
> > > overview map?
> > >
> > > Gerd
> > >
> > > 
> > > Von: Dave Swarthout 
> > > 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 
> > > mailto:gpetermann_muenc...@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 
> > > mailto:daveswarth...@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 er

Re: [mkgmap-dev] Compile error

[Dave Swarthout]

OMG!

I copied parts of my batch file for Thailand maps to make this batch
file when I came back to the U.S. but forgot to use the splitter
output file as inputs. I never noticed my omission. It works fine now:

java -Xmx4000m -jar mkgmap.jar -c DJS.cfg --latin1 --family-id=24566
--name-tag-list=name,alt_name,loc_name,int_name --description="Eugene"
splitter\*.o5m "C:\Users\Alask\Dropbox
(Personal)\Mapping\24983djs.TYP"

Sorry for wasting your time. I must say, however, that the error
message I got didn't help diagnose or solve that problem. Maybe that
could be looked at and improved.

Thanks, Gerd.

On Mon, May 2, 2022 at 10:22 PM  wrote:
>
> Hi Dave,
>
> I just double checked what you wrote before and it seems you feed mkgmap with
> the large file C:\Users\alask\Downloads\Maps\Eugene.osm ?
> You also posted a log that shows that you use splitter with the same file.
> So, change your mkgmap command to actually use the output from splitter and 
> your
> problem shoud be solved. There is probably no need to use the small 
> --max-nodes value.
>
> Gerd
>
>
> 
> Von: Dave Swarthout 
> Gesendet: Montag, 2. Mai 2022 23:13
> An: Gerd Petermann
> Cc: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Compile error
>
> 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
>  wrote:
> >
> > Hi Dave,
> >
> > I would expect a tile with 0 bytes. Maybe you get this message for the 
> > overview map?
> >
> > Gerd
> >
> > ____________________
> > Von: Dave Swarthout 
> > 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 
> > mailto:gpetermann_muenc...@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 
> > mailto:daveswarth...@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 
> > mailto:gpetermann_muenc...@hotmail.com><mailto:gpetermann_muenc...@hotmail.com<mailto:gpetermann_muenc...@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 

Re: [mkgmap-dev] Compile error

[gpetermann_muenchen]

Hi Dave,

I just double checked what you wrote before and it seems you feed mkgmap with 
the large file C:\Users\alask\Downloads\Maps\Eugene.osm ?
You also posted a log that shows that you use splitter with the same file.
So, change your mkgmap command to actually use the output from splitter and your
problem shoud be solved. There is probably no need to use the small --max-nodes 
value.

Gerd



Von: Dave Swarthout 
Gesendet: Montag, 2. Mai 2022 23:13
An: Gerd Petermann
Cc: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Compile error

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
 wrote:
>
> Hi Dave,
>
> I would expect a tile with 0 bytes. Maybe you get this message for the 
> overview map?
>
> Gerd
>
> 
> Von: Dave Swarthout 
> 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 
> mailto:gpetermann_muenc...@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 mailto:daveswarth...@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 
> mailto:gpetermann_muenc...@hotmail.com><mailto:gpetermann_muenc...@hotmail.com<mailto:gpetermann_muenc...@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 
> mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk><mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk<mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk>>>
>  im Auftrag von Dave Swarthout 
> mailto:daveswarth...@gmail.com><mailto:daveswarth...@gmail.com<mailto:daveswarth...@gmail.com>>>
> Gesendet: Sonntag, 1. Mai 2022 02:06
> An: Development list for mkgmap
> Betreff: [mkgmap-dev] Compile error
>
> Hi,
>
> I'm not on thi

Re: [mkgmap-dev] Compile error

[Dave Swarthout]

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
 wrote:
>
> Hi Dave,
>
> I would expect a tile with 0 bytes. Maybe you get this message for the 
> overview map?
>
> Gerd
>
> 
> Von: Dave Swarthout 
> 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 
> mailto:gpetermann_muenc...@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 mailto:daveswarth...@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 
> mailto:gpetermann_muenc...@hotmail.com><mailto:gpetermann_muenc...@hotmail.com<mailto:gpetermann_muenc...@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 
> mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk><mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk<mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk>>>
>  im Auftrag von Dave Swarthout 
> mailto:daveswarth...@gmail.com><mailto:daveswarth...@gmail.com<mailto:daveswarth...@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_na

Re: [mkgmap-dev] Compile error

[Dave Swarthout]

@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 
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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Compile error

[Carlos Dávila]

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?Index: src/uk/me/parabola/imgfmt/app/BufferedImgFileWriter.java
===
--- src/uk/me/parabola/imgfmt/app/BufferedImgFileWriter.java	(revisión: 4827)
+++ src/uk/me/parabola/imgfmt/app/BufferedImgFileWriter.java	(copia de trabajo)
@@ -273,7 +273,9 @@
 bufferSize += GROW_SIZE;
 			if (bufferSize > maxAllowedSize) {
 throw new MapTooBigException(maxAllowedSize,
-		"The " + subfile + " section of the map or tile is too big.",
+		"The " + subfile + " section of the map or tile ("
+			+ log.threadTag()
+			+ ") is too big.",
 		"Try splitting the map into smaller tiles or reducing the amount of information included in the map.");
 			}
 			ByteBuffer newb = ByteBuffer.allocate(bufferSize);
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Compile error

[Dave Swarthout]

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_muenc...@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 
> 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_muenc...@hotmail.com<mailto:gpetermann_muenc...@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-boun...@lists.mkgmap.org.uk>> im Auftrag von Dave Swarthout <
> daveswarth...@gmail.com<mailto:daveswarth...@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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Compile error

[Gerd Petermann]

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 
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 
mailto:gpetermann_muenc...@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 
mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk>>
 im Auftrag von Dave Swarthout 
mailto:daveswarth...@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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Compile error

[Dave Swarthout]

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_muenc...@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  im Auftrag von
> Dave Swarthout 
> 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


splitter.log
Description: Binary data


areas.list
Description: Binary data


DJS.cfg
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Compile error

[Gerd Petermann]

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  im Auftrag von Dave 
Swarthout 
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
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] compile error "Stack size is 2" with mkgmap-r3834

[greg crago]

Thanks. Looked but could not see

On Tue, Mar 7, 2017 at 7:01 AM, greg crago  wrote:

> Using this line in my POINTS file:
>
> power=generator & generator:source=wind & generator:method=wind_turbine
> [0x6419 resolution 22] continue
> power=generator [0x6016 resolution 22] # special point if Method NOT Wind
> Turbine
>
> I get this compile result:
>
> Found one style in \MKGMAP\BaseCamp-style\openmapchest
> Error in style: Error: (points:315): Stack size is 2
> could not open style openmapchest
> finished check-styles
> Error in style: Error: (points:315): Stack size is 2
> Error in style: Error: (points:315): Stack size is 2
> Error in style: Error: (points:315): Stack size is 2
> Could not open style
> Number of ExitExceptions: 1Error in style: Error: (points:315): Stack size
> is 2
>
> Can I use multiple "&"?
>
> Greg
>
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] compile error "Stack size is 2" with mkgmap-r3834

[Gerd Petermann]

Hi Greg,

first line is wrong, you have to place the word continue before the closing 
brackets "]"

Gerd

Von: mkgmap-dev  im Auftrag von greg 
crago 
Gesendet: Dienstag, 7. März 2017 16:01:05
An: Development list for mkgmap
Betreff: [mkgmap-dev] compile error "Stack size is 2" with mkgmap-r3834

Using this line in my POINTS file:

power=generator & generator:source=wind & generator:method=wind_turbine [0x6419 
resolution 22] continue
power=generator [0x6016 resolution 22] # special point if Method NOT Wind 
Turbine

I get this compile result:

Found one style in \MKGMAP\BaseCamp-style\openmapchest
Error in style: Error: (points:315): Stack size is 2
could not open style openmapchest
finished check-styles
Error in style: Error: (points:315): Stack size is 2
Error in style: Error: (points:315): Stack size is 2
Error in style: Error: (points:315): Stack size is 2
Could not open style
Number of ExitExceptions: 1Error in style: Error: (points:315): Stack size is 2

Can I use multiple "&"?

Greg
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev