Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of localtimestamp can be misleading #4

Open
gravitystorm opened this issue Jan 23, 2012 · 0 comments
Open

Use of localtimestamp can be misleading #4

gravitystorm opened this issue Jan 23, 2012 · 0 comments

Comments

@gravitystorm
Copy link

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.

lxbarth referenced this issue in lxbarth/openstreetmap-watch-list Nov 1, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant