You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating, the current timestamp is used as the time attribute of the change. But when OWL is lagging behind, this can cause confusion - e.g. showing something as "3 hours ago" when the change itself is a week old.
It would be better to use the timestamp from the element in the change file instead.
The text was updated successfully, but these errors were encountered:
lxbarth
referenced
this issue
in lxbarth/openstreetmap-watch-list
Nov 1, 2012
https://github.com/zerebubuth/openstreetmap-watch-list/blob/master/cpp/src/osm/db/owl_database.cpp#L308
When updating, the current timestamp is used as the time attribute of the change. But when OWL is lagging behind, this can cause confusion - e.g. showing something as "3 hours ago" when the change itself is a week old.
It would be better to use the timestamp from the element in the change file instead.
The text was updated successfully, but these errors were encountered: