Opened 10 years ago

Closed 10 years ago

#1744 closed defect (wontfix)

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

Reported by: Dwi Secundus Owned by: zerebubuth@…
Priority: minor Milestone:
Component: admin Version:
Keywords: api timestamp Cc: again@…

Description

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 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?

Change History (3)

comment:1 Changed 10 years ago by Dwi Secundus

Cc: again@… added

comment:2 Changed 10 years ago by Grant Slater

Owner: changed from Tom Hughes to zerebubuth@…

comment:3 Changed 10 years ago by Matt

Priority: majorminor
Resolution: wontfix
Status: newclosed

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.

Note: See TracTickets for help on using tickets.