Proposal:Last checked
 | The key survey:date=* is in use. |
| last_checked | |
|---|---|
| Proposal status: | Abandoned (inactive) |
| Proposed by: | Cohan |
| Tagging: | last_checked=date in ISO 8601 |
| Applies to: |   
|
| Definition: | The last date the details of an object were checked to be correct. |
| Statistics: |
|
| Rendered as: | n/a |
| Draft started: | 2009-09-16 |
| RFC start: | 2009-09-16 |
Proposal
This proposal is for adding information of when the information of an object was last checked to be correct.
Rationale
Much data becomes inacurate at varying time of decay. E.g. bus routes change, and at least in my area I estimate that 10-20% of the restaurants change name and/or cuisine within a year.
By using a last_checked tag you can easily find objects that needs checking in a given area.
Just using timestamps on the object history is not enough, since the object might have been edited without information beeing checked. (E.g. slightly move the node of a restaurant after the nearby road is better surveyed with GPS)
Tagging
last_checked=date The date should be in ISO 8601 format (YYYY-MM-DD). Month-level accuracy may be indicated with YYYY-MM, in accordance with ISO 8601.
Applies to
- Nodes (e.g. restaurants and other POIs)
- Ways (e.g. roads with specified maxspeed=*)
- Relation (e.g. bus routes)
Rendering
No special rendering other than perhaps as an "old data warning" overlay.
Comments
Use the talk page please.
Votes
Voting has not started!
