[Tile-serving] how to expedite coastlines shapefile updates?

Paul Norman penorman at mac.com
Sun Apr 14 00:06:04 UTC 2013

shoreline_300 doesn't need regular updates, it's only used at low zooms. It
is just a simplified version of processed_p. I'm not sure off-hand exactly
what zooms it is used at, but I doubt 


If this is historical, as I presume, you need to set up your own coastline
generation process. This would consist of running coastcheck or OSMCoastline
on a planet file. For the full OSM data, this process takes 1-2 hours once
you have the planet file.


I haven't benchmarked them on comparable hardware, but OSMCoastline is
reported to be a bit faster. 


https://github.com/gravitystorm/openstreetmap-carto/issues/39 may relevant
to using the coastline files.


From: Jeff Meyer [mailto:jeff at gwhat.org] 
Sent: Saturday, April 13, 2013 3:51 PM
To: tile-serving at openstreetmap.org
Subject: [Tile-serving] how to expedite coastlines shapefile updates?


Hi - I'm trying to figure out the best way to set up a rendering chain that
reflects changes to shorelines relatively quickly. The use case here is
getting rid of man-made features and coastal landfill that are currently
reflected in OSM in urban areas.


I've set up an OSM stack that won't be using data from planet.osm, which
means I won't be able to take advantage of automatic updates to processed_p
and shoreline_300. The rest of the stack is pretty vanilla - rails,
mapnik/renderd, minutely updates, etc.


Any advice on how to set up something like this?





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20130413/b49b109b/attachment.html>

More information about the Tile-serving mailing list