[OSM-dev] multiple tables

[Jon Burgess]

On Tue, 2007-02-27 at 21:12 +0000, Artem Pavlenko wrote:
> Here is 'multiple tables' patch for osm2pgsql which creates three tables - one 
> per geometry type. I think it makes creating styles/rules/filters a little 
> bit more manageable. 
> 
> How about filtering out  'coastlines'? 
> 
> Cheers,
> Artem

Do you happen to have a corresponding patch to osm.xml which uses these
new table names?

Does dropping the coastline data make any significant performance
difference? I'd suspect we shouldn't drop it from osm2pgsql until we
have a replacement set of shapefiles which a reasonable polygon
coastline coverage.

Personally i'd like to start with an interim approach of converting the
coastline rendering to a line style like I mentioned previously. IMO a
thin blue line is an improvement over the present grey triangles (at
least until the coastline polygons get completed).

I've also been wondering whether creating specific tables for each of
the SQL select queries in osm.xml might speed things up a little. Since
the same query gets run multiple times it seems logical to me that
performing this once and storing in a separate table would be a win. I
think the previous consensus was that osm2pgsql+osm.xml are a fairly
tightly coupled pair which need to be kept in sync anyway.


	Jon