[OSM-dev] Osmosis error

Error occurs in Osmosis 0.33: /backup/projects/3rdparty/osmosis/bin/osmosis --rx file=/backup/projects/data/gos/andi/bremen.osm --wd database=b validateSchemaVersion=no ... populateCurrentTables=no java.io.FileNotFoundException: /backup/projects/3rdparty/osmosis/config/plexus.conf (No such

[OSM-dev] Osmosis and current tables

Is there a way to make Osmosis populate and refresh just the current tables and ignoring the history tables? It would be faster and it is easier to work with tables which have exactly one version - the recent - for every feature. Andi ___ dev

[OSM-dev] Errors with populateCurrentTables=yes on refresh based on partial dataset

Using populateCurrentTables=yes on refresh will make Osmosis stop. When I use populateCurrentTables=no, then all is OK, but then I don't have updated data in the current tables. What can I do about that? Feb 14, 2010 4:15:28 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Osmosis Version

Re: [OSM-dev] Osmosis and current tables - temporary solution

Deleting all old versions before inserting the new one via triggers will slow down the script a bit, but the checks for the latest version can be omitted and you can use populateCurrentTables=no: CREATE OR REPLACE FUNCTION nodes_insert() RETURNS trigger AS $$ DECLARE BEGIN