It is potentially possible for the results of OSMCoastline to be absurd. In these cases, my understand is the new files might not be posted.
There are a couple of coastline error displays. One is the coastline layer in OSMI at http://tools.geofabrik.de/osmi/?view=coastline which shows errors found by OSMCoastline. Another is http://wightpaths.co.uk/coast/ which shows the results of coastcheck, the software used for the coastline on tile.openstreetmap.org. I supply the results as part of my generation of http://pnorman.dev.openstreetmap.org/coastlines/. It's worth noting that I do not do any checks on my data. It's the result of an entirely automatic process that just uploads the results of coastcheck. From: Preet [mailto:[email protected]] Sent: Sunday, March 10, 2013 7:34 PM To: [email protected] Subject: [OSM-dev] openstreetmapdata.com Hiya, First off, thanks to Jochen for creating such an awesome service. The hardware I have isn't really capable of extracting coastlines from planet.osm in any reasonable amount of time, so having updated data available is invaluable for me! I had a question about one of the notes on the coastline data: "The coastline in OpenStreetMap is often broken. The update process will try to repair it, but this does not always work. If the OSM data can't be repaired automatically, the data here will not be updated." What does this mean exactly? Is there a chance poorly defined coastline data won't be seen in the resulting shapefile? ie, could there be chunks of coastline simply missing? Or is there a 'decent' baseline, and only newly updated coastline data that's bad won't be processed to reflect the changes? Preet
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
