[mkgmap-dev] [PATCH v2] Fix so that all polygons are really closed
From Henning Scholland osm at aighes.de on Sun Feb 27 16:09:03 GMT 2011
Am 27.02.2011 16:58, schrieb Torsten Leistikow: > WanMil schrieb am 27.02.2011 16:53: >> Your example will result in >> 1. line with 0x01 >> 2. a) nothing more if node1 or node2 is within the tiles bounding box >> b) a polygon 0x02 if node1 and node2 is outside or on the tiles >> bounding box. > Ok, I will try out r1865 when it is availbale as a download. > > But in my opinion 2.b) is a fault: If the polygon is not closed in the OSM data, > it shouldn't be closed by mkgmap, no matter whether the start and end nodes are > inside or outside the bounding box But correct polygons gets divided into two or more unclosed polygons by splitting the hole osm-datafile into smaller tiles. These polygons should be closed by mkgmap. Maybe it could be managed if polygons gets only closed, then there isn't only a rule in polygons-file. Example: man_made=pier in polygons and lines-file -> no closing man_made=pier & area=yes in polygons-file and man_made=pier & area!=* in lines-file -> close, if nodes are outside man_made=pier only in polygons-file -> close, if nodes are outside Henning
- Previous message: [mkgmap-dev] [PATCH v2] Fix so that all polygons are really closed
- Next message: [mkgmap-dev] [PATCH v2] Fix so that all polygons are really closed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list