-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi,
per previous discussions, we've now reinstalled ptolemy as the OSM Toolserver database, and i'm now working on setting up PostgreSQL and the mapnik database (which is what cassini has). cassini will remain up for now, but will go offline once ptolemy is ready, since it will become Wikimedia's production OSM database.
users cannot log into ptolemy. instead, it will be accessed from the normal Toolserver.
- river.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
update: import of the mapnik database (from current planet.osm) has now started.
- river.
River Tarnell schrieb:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
update: import of the mapnik database (from current planet.osm) has now started.
What osm2pgsql style did you use?
For cassini we combined the wikimedia style (which is the osm style + the name:xx-tags) with the hike'n'bike style (it needs extra fields) and added some more fields that are not that useful for rendering but eg. for a POI map (what I'm working on atm.) or a Yellow-Pages like search.
This combined style is located at
https://svn.toolserver.org/svnroot/mazder/planet-import/wikimedia.extended.s...
It allows a much wider usage then just rendering and is therefor better suited for a toolserver as cass.. i meant ptolemy :)
Peter
2009/11/24 Peter Körner osm-lists@mazdermind.de:
River Tarnell schrieb: For cassini we combined the wikimedia style (which is the osm style + the name:xx-tags) with the hike'n'bike style (it needs extra fields) and added some more fields that are not that useful for rendering but eg. for a POI map (what I'm working on atm.) or a Yellow-Pages like search.
This combined style is located at
https://svn.toolserver.org/svnroot/mazder/planet-import/wikimedia.extended.s...
If it's still possible, I would like to request an additional line in the style file:
way intermittent text linear
If it's not in this import, then I'll just wait for a next one (which will happen at some point I suppose).
Thanks Colin
Colin Marquardt schrieb:
2009/11/24 Peter Körner osm-lists@mazdermind.de:
River Tarnell schrieb: For cassini we combined the wikimedia style (which is the osm style + the name:xx-tags) with the hike'n'bike style (it needs extra fields) and added some more fields that are not that useful for rendering but eg. for a POI map (what I'm working on atm.) or a Yellow-Pages like search.
This combined style is located at
https://svn.toolserver.org/svnroot/mazder/planet-import/wikimedia.extended.s...
If it's still possible, I would like to request an additional line in the style file:
I added the line to the svn version. As it requires a complete re-import it's not likely that it will come on cassini, soon. I don't know about ptolemy, but I think, if the import runs smooth, it's same for there.
Peter
2009/11/24 Peter Körner osm-lists@mazdermind.de:
Colin Marquardt schrieb:
If it's still possible, I would like to request an additional line in the style file:
I added the line to the svn version.
Thanks.
As it requires a complete re-import it's not likely that it will come on cassini, soon. I don't know about ptolemy, but I think, if the import runs smooth, it's same for there.
When I asked around in the past, it sounded as if it wouldn't be too hard to modify osm2pgsql to make it create new columns in the DB for such things. Maybe someone has the need *and* the skill for it at some point :)
Cheers Colin
Colin Marquardt schrieb:
2009/11/24 Peter Körner osm-lists@mazdermind.de:
Colin Marquardt schrieb:
If it's still possible, I would like to request an additional line in the style file:
I added the line to the svn version.
Thanks.
As it requires a complete re-import it's not likely that it will come on cassini, soon. I don't know about ptolemy, but I think, if the import runs smooth, it's same for there.
When I asked around in the past, it sounded as if it wouldn't be too hard to modify osm2pgsql to make it create new columns in the DB for such things. Maybe someone has the need *and* the skill for it at some point :)
Yes it wouldn't be to hard to create them, but they'd be empty then. The diff-import may fill them within some months, but it will only add them if their value changed. The only possibility is to go over the planet again..
We could do some kind of import from xapi, but who knows if/when it works and how old the data is...
Peter
2009/11/24 Peter Körner osm-lists@mazdermind.de:
Colin Marquardt schrieb:
2009/11/24 Peter Körner osm-lists@mazdermind.de: When I asked around in the past, it sounded as if it wouldn't be too hard to modify osm2pgsql to make it create new columns in the DB for such things. Maybe someone has the need *and* the skill for it at some point :)
Yes it wouldn't be to hard to create them, but they'd be empty then. The diff-import may fill them within some months, but it will only add them if their value changed. The only possibility is to go over the planet again..
Depends on whether the planet parsing is the slow thing or the writing of lots of data into the DB. Might still be lots better than a full import...
Cheers Colin
On Tue, Nov 24, 2009 at 20:44, Colin Marquardt cmarqu42@googlemail.com wrote:
2009/11/24 Peter Körner osm-lists@mazdermind.de:
Colin Marquardt schrieb:
2009/11/24 Peter Körner osm-lists@mazdermind.de: When I asked around in the past, it sounded as if it wouldn't be too hard to modify osm2pgsql to make it create new columns in the DB for such things. Maybe someone has the need *and* the skill for it at some point :)
Yes it wouldn't be to hard to create them, but they'd be empty then. The diff-import may fill them within some months, but it will only add them if their value changed. The only possibility is to go over the planet again..
Depends on whether the planet parsing is the slow thing or the writing of lots of data into the DB. Might still be lots better than a full import...
If we ever get a full DB replication going (not just PostGIS) we could theoretically populate new columns with the planet data and then keep them up to date by changing the style (used when applying diffs).
Should work, but AFAIK OSM itself just does a full re-import, but then again they add new fields rarely.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Colin Marquardt:
If it's still possible, I would like to request an additional line in the style file:
since i had to make some changes for performance and restart the import, i've added this to the Wikimedia style.
- river.
2009/11/26 River Tarnell river@loreley.flyingparchment.org.uk:
Colin Marquardt:
If it's still possible, I would like to request an additional line in the style file:
since i had to make some changes for performance and restart the import, i've added this to the Wikimedia style.
Great, thanks.
Cheers Colin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Körner:
What osm2pgsql style did you use?
the same Wikimedia style that cassini is using, including hike'n'bike.
Colin Marquardt:
If it's still possible, I would like to request an additional line in the style file:
way intermittent text linear
it's too late to add it for this import. if the import needs to be restarted for some reason, i'll add this, but i hope that won't happen ;-)
depending on how much disk space the completed import uses, it might be possible to change styles in future by importing a separate copy with the new style, then swapping that with the current database. however, since we also want to store the API database and rendered tiles, this might not be possible for very long.
- river.
Hi River,
it's too late to add it for this import. if the import needs to be restarted for some reason, i'll add this, but i hope that won't happen ;-)
May I ask which style you used?
depending on how much disk space the completed import uses, it might be possible to change styles in future by importing a separate copy with the new style, then swapping that with the current database.
The script to do this is placed at https://svn.toolserver.org/svnroot/mazder/planet-import/planet-update
It's not enough to rename the tables, you have to rename all indices, too (see activate_tables and drop_old_tables functions).
however, since we also want to store the API database and rendered tiles, this might not be possible for very long.
I'm happily looking forward on the complete db import. There was recently a discussion on osm-dev on how to generate a complete history dump which includes all changes since 2004 or so: http://lists.openstreetmap.org/pipermail/dev/2009-November/017672.html
Is this of interest for ptolemy?
Peter