my Answers to some of the raised questions:
*Database server* 1. I'd suggest to start with only one read-only PostgreSQL server for both, the Toolserver & the WMF Rendering, but with each with it's own alias. Atm there's nearly nothing on the toolserver, but when the load produced by it grows, we could spawn a separate db-server, keeping the alias.
4. additional metadata like localized names can be included into the mapnik/PostGIS-DB without any problems, as its structure is thought to be customized this way. I don't know about other schemes.
*Rendering machinery* I'd suggest mapnik, as it's the one used on openstreetmap.org, so it's style is somehow the "face" of openstreetmap: this is what new people to osm think, osm looks like.
*Stylesheet management+ 1. Internationalization is well done using the views in the postgis-db, using the name:xx-Tags.
And some more Questions (I added these also to the article) *Main OSM mirror database* what will be mirrored? the current-tables the history-tables the raw-tables how could this be mirrored? only current can be imported from a planet.osm how often should this be updated?
*Mapnik database* we'll need a procedure for regular complete re-imports to solve inconsistencies introduced by the diff-import
Brion Vibber schrieb:
It seems there's been a long serious of miscommunications and dropped handling of access & software setup for the mapping servers, which has led to some very unhappy people. :(
We are all, by any means, only offering our private time to this. So it will take as long as it takes.
Peter