Warn about 1,2,3,4,5 year old shops/amenities

[openstreetmap.org-user-d1g]

• (amenity=* or shop=*) timestamp:2010-01-01/2011-01-01
• (amenity=* or shop=*) timestamp:2011-01-01/2012-01-01

PS. tag list could be extended with more POI centric keys.
PS2. We can consider additional checks for "survey:date"=* values (or if they are absent)

[Klumbumbus]

Only 0.06% of all amenity also have the survey:date tag. A missing survey:date tag doesn't make the object more up to date than an outdated survey:date. So to warn only about the outdated survey:date seems not usefull in relation to the amenities without this tag. Warn about both (outdated or missing survey:date) would produce a warning for 99.9% of all amenities, which is also not helpful.

Also survey:date is not an established tagging schema. (The high total number of survey:date tags comes from keypadmapper3) There are also several other similar tags: check_date, survey_date, survey, lastcheck, last_checked, updated,...

[openstreetmap.org-user-d1g]

Replying to Klumbumbus:

Only 0.06% of all amenity also have the survey:date tag.

There also many highways without surface=asphalt. It doesn't mean that specifying asphalt would harm us.

Also survey:date is not an established tagging schema. (The high total number of survey:date tags comes from keypadmapper3) There are also several other similar tags: check_date, survey_date, survey, lastcheck, last_checked, updated,...

based on what was said ​http://wiki.openstreetmap.org/wiki/Key:check_date it is most commonly used

data: 212.000 (10x times more than second), last users: 1367

I consider 1367 users as established usage, even this tag wasn't voted using proposal.

It's usage grows over time:
​http://taginfo.openstreetmap.org/keys/survey:date - 231 881 objects and 1 565 different users

[openstreetmap.org-user-d1g]

Replying to Klumbumbus:

So to warn only about the outdated survey:date seems not usefull

Well I suggested validation based on last modification date and not about any tag. As you can see, there no "survey:date" checks in my queries.

Yes, we can adapt survey:date as separate checks. I think that 1500 users would appreciate this.