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

Wrong "Last rendered" time and date #1950

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

Wrong "Last rendered" time and date #1950

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

Reporter: rune.andersen[at]gmail.com
[Submitted to the original trac issue database at 6.28pm, Thursday, 11th June 2009]

When checking certain tiles by appending /status to the tile URL, Mapnik reports:
Tile is due to be rendered. Last rendered at Sat Jan 01 00:00:00 2000

This is not correct in my case, since none of the ways rendered in the tile existed in 2000. Besides, the date 00.00.00 00:00:00 is obviously an error.

Example (not working when posting this):
http://tile.openstreetmap.org/18/138654/70925.png/status

@openstreetmap-trac
Copy link
Author

Author: smsm1
[Added to the original trac issue at 11.25pm, Thursday, 11th June 2009]

You example now has:
Tile is clean. Last rendered at Thu Jun 11 22:20:23 2009

The reason for that date, is that the tile in question is due to be re-rendered, and the way that we currently denote this is by setting the last rendered date to a long time ago.

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 10.10pm, Tuesday, 30th June 2009]

As above: not a mapnik issue, and by design.

@openstreetmap-trac
Copy link
Author

Author: Vid the Kid
[Added to the original trac issue at 2.41am, Thursday, 13th August 2009]

This is probably the first time I've seen January 1, 2000 used as a placeholder for "a long time ago" in computing. Usually it's 1900 or the Unix Epoch.

Makes me wonder how many programmers are enjoying the "fact" that year-2100 compliance is a far-off concern...

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