[mkgmap-dev] Coastline warnings for --generate-sea=polygons at tile border
From Mark Burton markb at ordern.com on Thu Jan 28 20:39:02 GMT 2010
Hi Marko, > I am still seeing it with unpatched r1533 (if we ignore the traffic_calming=* > that I added to the points file): > > 2010/01/27 23:40:12 WARNING (Osm5XmlHandler): Way null (http://www.openstreetmap.org/browse/way/4611686018427418010) has consecutive nodes with the same coordinates (http://www.openstreetmap.org/?mlat=62.22656&mlon=25.82736&zoom=17) but they can't be merged because both are boundary nodes! Err, that message is not in r1533 - something's screwy! > 2010/01/27 23:40:08 WARNING (Osm5XmlHandler): Non-closed coastline segment does not hit bounding box: 279763707 (61,81651/30,07776) 279763719 (61,81599/30,07524) http://www.openstreetmap.org/?mlat=61.81651&mlon=30.07776&zoom=17 > > but they can most likely be attributed to Geofabrik's cutting > (Finland is about 60N,20E to 70N,30E). Has someone already bugged > the osmosis or Geofabrik folks about this? Could I work around the issue > with some mkgmap options? I guess I'd want an imaginary L-shaped coastline > running south from the Swedish-Finnish border and turning east towards > St. Petersburg. Have you tried the close-gaps option to generate-sea? That may help: close-gaps=NUM close gaps in coastline that are less than this distance (metres) Mark
- Previous message: [mkgmap-dev] Coastline warnings for --generate-sea=polygons at tile border
- Next message: [mkgmap-dev] Coastline warnings for --generate-sea=polygons at tile border
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list