Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-10 Thread Johann Gail
But I see a technical problem arise: In the filter chain there aren't any more tags or other information on how polygons are connected. There are only the raw polygon objects with coordinate data. Do you mean the multipolygon information which polygons belong to the mulitpolygon

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread WanMil
Am 09.01.2010 00:05, schrieb Johann Gail: Changes: * Polygons with inner polygons are now divided into several polygons. It's much faster and the PolygonSplitter cannot destroy them any more. Hello WanMil, this change could have some other side effects. (As observed and described in

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread Felix Hartmann
On 09.01.2010 10:08, WanMil wrote: Am 09.01.2010 00:05, schrieb Johann Gail: Changes: * Polygons with inner polygons are now divided into several polygons. It's much faster and the PolygonSplitter cannot destroy them any more. Hello WanMil, this change could have

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread Ralf Kleineisel
On 01/09/2010 10:08 AM, WanMil wrote: Another idea is to add some specific tags by the mulitpolygon algorithm that link to the other pieces of the formerly big forrest. This could be evaluated by the SizeFilter? Another idea (don't know if this is possible): You have a big multipolygon

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread WanMil
Am 09.01.2010 11:25, schrieb Ralf Kleineisel: On 01/09/2010 10:08 AM, WanMil wrote: Another idea is to add some specific tags by the mulitpolygon algorithm that link to the other pieces of the formerly big forrest. This could be evaluated by the SizeFilter? Another idea (don't know if this

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread Thilo Hannemann
AFAIK the POI searches work only with the actual POIs that are generated, not the polygons. So this should be no big problem. You should make sure though that the --add-pois-to-areas option doesn't generate the POIs twice. Regards Thilo Am 09.01.2010 um 11:56 schrieb WanMil: Am 09.01.2010

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread WanMil
however lake Neusidel / Neusiedler See in Austria is now empty in some places where before it was filled with water. I have compared the trunk to the the mp branch with the Austria dump from http://download.geofabrik.de/osm/europe/. Trunk: lake Neusiedel is completely empty. No water at all.

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread WanMil
Is there any mkgmap tag yet to avoid this? (like mkgmap:noaddpoitoarea=yes) WanMil AFAIK the POI searches work only with the actual POIs that are generated, not the polygons. So this should be no big problem. You should make sure though that the --add-pois-to-areas option doesn't generate

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread Johann Gail
Ralf Kleineisel schrieb: On 01/09/2010 10:08 AM, WanMil wrote: Another idea is to add some specific tags by the mulitpolygon algorithm that link to the other pieces of the formerly big forrest. This could be evaluated by the SizeFilter? Another idea (don't know if this is

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread WanMil
Ralf Kleineisel schrieb: On 01/09/2010 10:08 AM, WanMil wrote: Another idea is to add some specific tags by the mulitpolygon algorithm that link to the other pieces of the formerly big forrest. This could be evaluated by the SizeFilter? Another idea (don't know if this is possible):

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread Johann Gail
Another idea (don't know if this is possible): You have a big multipolygon forest. You could duplicate it. One copy without small inner polygons for the low resolutions. Another copy with the inner polygons which gets splitted for the higher resolutions. The copies could be marked with some

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread Clinton Gladstone
On Jan 9, 2010, at 12:41, WanMil wrote: Is there any mkgmap tag yet to avoid this? (like mkgmap:noaddpoitoarea=yes) POI generation from areas is disabled by default. Command line option --add-pois-to-areas enables this. Further, POIs will only be generated from areas if there is a

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread WanMil
Johann, thank you for you good explanations to the filter chain. It gives me a good overview how it works! What do you mean by mo code composign larger polygons? As far as I understand the thing, it combines an outer poylgon with an inner polygon to a poygon with an hole. But by definition

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-09 Thread Steve Ratcliffe
Hi When mkgmap was started relations had not been invented and so I think it is very valid to re-think the processing steps and data structures. Mkgmap is separated in three layers: 1. The reader layer (package ..mkgmap.reader.osm) which deals in concepts from osm such as

Re: [mkgmap-dev] [mp: PATCH] Multipolygon handling - decomposed polygons

2010-01-08 Thread Felix Hartmann
Well speed seems improved... however lake Neusidel / Neusiedler See in Austria is now empty in some places where before it was filled with water. In general it seems to be working great (and very quick). Of course missing the ways makes it not production ready yet. On 07.01.2010 23:39,