Closed mschicker closed 6 years ago
FWIW, I see this without the bounding box argument as well...
@mschicker Above is the native api call might be helpful to compare the two. Looks like we might be dropping the user who created the data as well.
Unsure if we want to include user who created data on export.
Merged #2365
OSM exports from MapeEdit are producing XML files where all of the timestamps are set to the computer epoch (1970-01-01T00:00:00Z)
Corresponding data in the osmapi database, however, has valid timestamp data. The export should be fixed, so that valid timestamps are included in the export.
On the server side, the export is accomplished with a hoot command like this:
hoot convert -D convert.bounding.box=minx,miny,maxx,maxy "osmapidb://user:pass@server:port/db_name" export_out.osm