Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Did timestamp of some elements change after API upgrade to 0.6? #1744

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Comments

@openstreetmap-trac
Copy link

Reporter: Dwi Secundus
[Submitted to the original trac issue database at 7.00pm, Friday, 24th April 2009]

I have an OSM file that I saved in the old API 0.5 times. This file contains some nodes that weren't changed in the meantime, like for example:

<node id='367684170' action='delete' timestamp='2009-03-30T20:58:52Z' user='Dwi Secundus' visible='true' lat='48.84823734955774' lon='10.06293166846246' />

Today if I query the [http://openstreetmap.org/api/0.6/node/367684170 API 0.6 for this node], it returns

<node id="367684170" lat="48.8483098" lon="10.0628546" version="1" changeset="870523" user="Dwi Secundus" uid="52915" visible="true" timestamp="2009-03-30T21:58:52Z"/>

So the time of the node has changed by one hour.

I wonder if this is correct? If it is not correct, is it a JOSM or an API problem?

@openstreetmap-trac
Copy link
Author

Author: Matt
[Added to the original trac issue at 6.46pm, Sunday, 26th April 2009]

yes. the 0.5 database was in UK local time with a few hacks in the API, osmosis and planet to try and deal with it. the new database is in UTC so such hacks are unnecessary, but it is possible that times returned by the old and new server don't match.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant