[mkgmap-dev] Analysis of MP issues in Finland

2010-01-29 Thread Marko Mäkelä
Hi WanMil, Mark, all, I analyzed all the multipolygon errors and warnings I got for today's finland.osm.bz2 from Geofabrik, without --generate-sea. Most of them can apparently be blamed on missing boundary information. I wrote the relation IDs an explanations to my logging.ignore file, so that

[mkgmap-dev] Unchecked conversions and calls

2010-01-29 Thread Marko Mäkelä
I am compiling mkgmap with Sun javac with -Xlint:unchecked by commenting out the compilerarg definition in build.xml, and I get some warnings for unchecked calls and type conversions. I do not know Java well enough to fix these (I learned it before the generics were introduced and have not written

[mkgmap-dev] Commit: r1537: Initial code for the SRT file.

2010-01-29 Thread svn commit
Version 1537 was commited by steve on 2010-01-29 13:26:12 + (Fri, 29 Jan 2010) Initial code for the SRT file. Not used by anything else yet. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk

[mkgmap-dev] Duo Tagged polygon.

2010-01-29 Thread Dave F.
Hi My last question got missed (Polygon with barrier problem) but I would like to know the answer so I'm posting it again. As discussed (polygon) landuse=farmyard barrier=wall wont render landuse if (line) barrier=wall is present. Is there any development in progress to solve this problem?

Re: [mkgmap-dev] Duo Tagged polygon.

2010-01-29 Thread Felix Hartmann
On 29.01.2010 15:44, Dave F. wrote: Hi My last question got missed (Polygon with barrier problem) but I would like to know the answer so I'm posting it again. As discussed (polygon) landuse=farmyard barrier=wall wont render landuse if (line) barrier=wall is present. Is there any

Re: [mkgmap-dev] Duo Tagged polygon.

2010-01-29 Thread Dave F.
Felix Hartmann wrote: No because streets have higher priority, as routing is to most people more important. Well, that debatable, but anyway... What I was suggesting is that when mkgmap finds a line it looks in the line style no other, when it finds a polygon it looks in polygon no

Re: [mkgmap-dev] Duo Tagged polygon.

2010-01-29 Thread Mark Burton
Hi Dave, I don't see how that would affect routers. I thought these style files just decided what colours were used to display on the screen. The data in the IMG would still be the same wouldn't it? No, the style files also decide which ways are routable and which are not. Mark

Re: [mkgmap-dev] Duo Tagged polygon.

2010-01-29 Thread Steve Ratcliffe
Hello What I was suggesting is that when mkgmap finds a line it looks in the line style no other, when it finds a polygon it looks in polygon no other. There would be no order or priority, mkgmap would look This is not so easy, because you don't know if something is a line or a polygon

Re: [mkgmap-dev] Duo Tagged polygon.

2010-01-29 Thread Dave F.
Mark Burton wrote: No, the style files also decide which ways are routable and which are not. Ok, I've learnt something new, thanks. However I'm still failing to understand why a linear way needs information from the polygon file. Isn't all the data it needs stored in the line file? Cheers

Re: [mkgmap-dev] Duo Tagged polygon.

2010-01-29 Thread Dave F.
Steve Ratcliffe wrote: Hello This is not so easy, because you don't know if something is a line or a polygon until you look it up. Having the first point equal to the last is not decisive because sometimes lines go in circles (eg. roundabouts, fence around a field) and sometimes polygons are

Re: [mkgmap-dev] --add-pois-to-areas behaviour

2010-01-29 Thread Christoph Wagner
Thilo Hannemann schrieb: The reason why you need a matching polygon rule for POIs to be generated is that mkgmap needs this to find out that it is a polygon. Now I really understand the problem. Would it be enough for mkgmap to specify a rule in polygons-file like this: building=* without

Re: [mkgmap-dev] --add-pois-to-areas behaviour

2010-01-29 Thread Thilo Hannemann
Am 29.01.2010 um 17:47 schrieb Christoph Wagner: Thilo Hannemann schrieb: The reason why you need a matching polygon rule for POIs to be generated is that mkgmap needs this to find out that it is a polygon. Now I really understand the problem. Would it be enough for mkgmap to specify a

[mkgmap-dev] Commit: r1538: Print expected result rather than repeating the actual result.

2010-01-29 Thread svn commit
Version 1538 was commited by steve on 2010-01-29 18:14:52 + (Fri, 29 Jan 2010) BRANCH: style Print expected result rather than repeating the actual result. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk

Re: [mkgmap-dev] Analysis of MP issues in Finland

2010-01-29 Thread WanMil
Hi Marko, Hi WanMil, Mark, all, I analyzed all the multipolygon errors and warnings I got for today's finland.osm.bz2 from Geofabrik, without --generate-sea. that's great!! Most of them can apparently be blamed on missing boundary information. I wrote the relation IDs an explanations to

Re: [mkgmap-dev] Analysis of MP issues in Finland

2010-01-29 Thread Marko Mäkelä
Hi WanMil, This mp was changed today (Jan 29th 2010, 06:33). Before the change a small polygon in the north of the mp touched the outer ring. So it contains to your first category overlapping lines. Thanks for figuring this out. I was too lazy to check previous versions, and the Geofabrik