Re: [mkgmap-dev] boundary France broken?

2014-01-26 Thread WanMil
Hi, > > Yes, I finally saw some other output but memory usage was very high > indeed (and swapping). So now it's working on the pre-split polygons. > > I get quite a lot of the following messages, are those expected? > > > Compressed buffers are too short, causing extra copy > Yes, these m

[mkgmap-dev] question on new style

2014-01-26 Thread Steve Sgalowski
with my old style file on my nuvi 1450lmt unit , there is no hospitals comming up now on the poi section i have included amenity = hospital and building = hospital here is the code i use for it amenity=hospital { name '${emergency} ${name} ${name}' | '${emergency}' | '${name}' '${name }' }[0x

Re: [mkgmap-dev] question on new style

2014-01-26 Thread Bernd Weigelt
Am Sonntag, 26. Januar 2014, 20:52:28 schrieb Steve Sgalowski: try this # Hospital amenity=hospital { name '${emergency} ${name} ${name}' | '${emergency}' |'${name}' '${name }} [0x3002 resolution 24] > with my old style file > on my nuvi 1450

Re: [mkgmap-dev] boundary France broken?

2014-01-26 Thread Gerd Petermann
Hi WanMil, yes, it complains when the ids are not sorted. It is easy to change that in the PrecompSeaSaver, but that makes debugging more difficult. Not nice, but no problem for mkgmap. Gerd > Date: Sun, 26 Jan 2014 10:38:50 +0100 > From: wmgc...@web.de > To: mkgmap-dev@lists.mkgmap.org.uk > Su

Re: [mkgmap-dev] boundary France broken?

2014-01-26 Thread Lambertus
Thanks for the report Minko, the script should be fixed now. The sea polygons too. On 25-01-14 22:01, Minko wrote: Thanks Lambertus for updating those files! There is however one issue. You packed the files in a subdirectory which mkgmap cannot process: SEVERE (BoundaryUtil): splitter\100100

[mkgmap-dev] Question regarding polish input data

2014-01-26 Thread Gerd Petermann
Hi, I just stumbled over this special case in the test data mkgmap\test\resources\in\mp\test1.mp : ; WayID = 23809417 ; building=yes ; ERROR: WayID=23809417 area is not closed [POLYGON] Type=0x13 Data0=(51.5270965,-0.1008803), (51.5271606,-0.100537), (51.5272514,-0.1005885), (51.527198,-0.10088

Re: [mkgmap-dev] broken mp in mkgmap-high-prec-coord-r2984

2014-01-26 Thread Gerd Petermann
Hi Minko, this error was fixed with r2986. I wonder why it did not also occur in the trunk, as it seems to be an error in the implementation of java.awt.geom.Area . Gerd > Date: Sat, 25 Jan 2014 13:56:40 +0100 > From: ligfiet...@online.nl > To: mkgmap-dev@lists.mkgmap.org.uk > Subject: [mkgmap-

Re: [mkgmap-dev] broken mp in mkgmap-high-prec-coord-r2984

2014-01-26 Thread Gerd Petermann
Hi Minko, the error is fixed with r2990. Regarding non-routable lines: Do you have an example for a line (not a shape) that should be improved? Maybe elevation data? Gerd > Date: Sat, 25 Jan 2014 21:27:21 +0100 > From: ligfiet...@online.nl > To: mkgmap-dev@lists.mkgmap.org.uk > Subject: Re: [m

Re: [mkgmap-dev] broken mp in mkgmap-high-prec-coord-r2984

2014-01-26 Thread Minko
Hi Gerd, I tried r2990 but it returned this error java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 at java.util.ArrayList.rangeCheckForAdd(Unknown Source) at java.util.ArrayList.addAll(Unknown Source) at uk.me.parabola.util.Java2DConverter.areaToSingularAreas(Java2DC

Re: [mkgmap-dev] Question regarding polish input data

2014-01-26 Thread Andrzej Popowski
Hi Gerd, > As the comment says, this polygon is not closed. The trunk version > ignores this error and creates a shape. > Is this intended? Yes, this is standard for polish format. Cgpsmapper would probably complain if you close a polygon. I think there are still some basic problems with mkg

Re: [mkgmap-dev] broken mp in mkgmap-high-prec-coord-r2984

2014-01-26 Thread GerdP
Hi Minko, a stupid typo. Please try r2991. Gerd ligfietser wrote > Hi Gerd, > I tried r2990 but it returned this error > > java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 > at java.util.ArrayList.rangeCheckForAdd(Unknown Source) > at java.util.ArrayList.addAll(Unknown Source)

Re: [mkgmap-dev] broken mp in mkgmap-high-prec-coord-r2984

2014-01-26 Thread Minko
Thanks Gerd, Works fine now. >Regarding non-routable lines: >Do you have an example for a line (not a shape) that should be improved? >Maybe elevation data? The example I showed you is good now. Contour lines don't look bad either. I'll run r2991 on whole Europe now and will check it out tomorr

[mkgmap-dev] Commit: r2992: Add newly discovered pointer multiplier to nod header.

2014-01-26 Thread svn commit
Version mkgmap-r2992 was committed by steve on Sun, 26 Jan 2014 Add newly discovered pointer multiplier to nod header. Currently mkgmap does not use it. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo

Re: [mkgmap-dev] Question regarding polish input data

2014-01-26 Thread Gerd Petermann
Hi Andrzej, > > As the comment says, this polygon is not closed. The trunk version > > ignores this error and creates a shape. > > Is this intended? > > Yes, this is standard for polish format. Cgpsmapper would probably > complain if you close a polygon. okay, that should work now in branch r

Re: [mkgmap-dev] Commit: r2982: performance improvement: use Path2D.append() followed by one

2014-01-26 Thread GerdP
Hi WanMil, I was not yet able to change the PrecompSea* code so that it generates identical output in two runs, so I still can't say for sure that the differences in the output can be ignored :-( Maybe you have an idea? Gerd GerdP wrote > Good hint :-) > I'll try that tomorrow. > > Gerd > >