[mkgmap-dev] Splitter, mkgmap and polygons
From Marko Mäkelä marko.makela at iki.fi on Mon Mar 21 14:32:14 GMT 2011
On Mon, Mar 21, 2011 at 10:16:43AM -0400, Nakor wrote: >A solution to the polygons in general could be to have the splitter >close the polygons properly at the boundary tiles instead of having >mkgmap try to guess where the polygon should be closed. Right, but have the splitter close only those polygons which were closed in the first place. >A step further would be to have splitter draw a polygon on the entire >tile border for multipolygon completly surrounding the tile. Right. Possibly, have Osmosis close the polygons as well, so that the map extracts would be OK. >This would for sure introduce "false" boundaries so those lines >probably would need to be marked in a special way so that mkgmap knows >to use them for determining which part of the tile is in which polygon >but not drawing them. Right, but how would you identify only the false sections of the boundaries? Perhaps, by tagging the false nodes only? Currently, mkgmap does not join connected ways that are tagged with polygon tags. Marko
- Previous message: [mkgmap-dev] Splitter, mkgmap and polygons
- Next message: [mkgmap-dev] Commit: r1877: Allow different smoothing parameters for polygons and lines.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list