[OSM-talk] conclusions from my postgres / postgis experiments

[Nick Whitelegg]

>IMO the OSM db structure should facilitate the simplest, most accurate
>storage of geodata. Everything else is up to the client app, whether
>it be Mapnik, Osmarender, Free-Map, a route-planner, or whatever. (Hey
>- isn't it cool to have three such quality clients already?) Each
>client app will have its own needs and there's no single db structure
>which is ideal for all of them.

True, though Freemap isn't really a renderer in its own right any more; 
rather it's a mash-up of various combinations of Mapnik, 
planet.osm-derived footpaths, SRTM contours and NPE maps. Having said 
that, I agree about clients storing data in a way which facilitates them; 
for instance, one thing I'd like to do with freemap is combine the 
OSM-derived path coordinates with footpath reports from freemap users, and 
arguably this would be better done in a different database structure.

Nick