[OSM-dev] Copying data from OSM to another open mapping project using the same software stack.

[andrzej zaborowski]

On 2 February 2012 12:48, Morten Olsen Lysgaard <morten at lysgaard.no> wrote:
> Case:
> I export an bbox containing some features from the OSM database using the
> api.
> Now I want to push those features as new features to another database,
> OpenAviationMap, running the same API. That means that all the id's in the
> OSM XML are invalid for the OpenAviationMap database.
>
> What I'm wondering: What transformations would i have to do with an XML file
> from OSM to upload it to another database running rails_port.
> I've understood i have to create unique negative ids for each object in the
> XML, but what about version, changeset date and all those other attributes.
> What are the correct attributes for data that's "new" to a database?
>
> Note: I want to upload the "new" data using JOSM. Right now, if I try it
> complains that I'm trying to modify objects that don't exist in my database.

You'd also need to make sure there's action="create" attached to the
imported objects.  Version and changeset might be ignored by the
rails_port when you're creating objects (not sure), but likely JOSM
will just ignore all of those attributes when generating the change
xml.

Cheers