On Nov 9, 2010, at 12:30 AM, Lennard wrote:
>> A stupid but working workaround is to go through the .osm file with sed or
>> something and rename coastline to something else before running osm2pgsql.
>
> And the more logical solution would be to find the single line in the
> osm2pgsql code that drops natural=coastline, adapt that, and
> recompile/reimport. Also remove the natural=coastline 'delete' keyword
> from default.style. You'll then have the raw natural=coastline ways in
> planet_osm_line, and you can create a mapnik rule for those.
Both of these workarounds will get me a personally useful file, but neither is
appropriate for situations where I'm setting up rendering styles for clients or
other people and need to help them help themselves.
Where would I put in a formal request that those lines be deleted from the
osm2pgsql code, or submit a patch? The instructions here suggest that Trac is
the right place, but I seem to need a Trac login to file a report:
http://wiki.openstreetmap.org/wiki/Osm2pgsql#Bug_reports
Jon Burgess is helping me off-list with some interesting intermediate files
from the processor that he linked to in a previous mail. I'm interested in
seeing those made available at the "official" URL,
http://hypercube.telascience.org/~kleptog/.
-mike.
----------------------------------------------------------------
michal migurski- m...@stamen.com
415.558.1610
_______________________________________________
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk
