There is a discussion on the "operational_status" tag on the tagging list, which is of relevance to the HOT efforts. Attached is a copy of one of the messages.
I'm attempting to formalize use of an operational_status tag for domestic uses for pay phones, toilets and drinking water. But the HOT team may want similar tagging for critical infrastructure. For example: HOT may want tags like operational_status:source, in order to document the name of the team that verified a feature. ---------------------------------------------------------------------------------------------------------------------------------------------------- On Tue, Jul 2, 2013 at 1:14 AM, Frederik Ramm <[email protected]> wrote: > A telephone that is already tagged as functional would not normally be > re-tagged as functional just to say "yes, it still is". This means that the > "operational_status:date" tag is superfluous, since it will always be the > date of the changeset when the operational_status was last modified. > The changeset date should definitely supply the *default* observation date, agreed. But which would you trust more if you're thirsty: amenity=dessert _oasis operational_status=working operational_status:date=1996-01-01 Or amenity=dessert _oasis operational_status=working operational_status:date=2013-01-01 The observed status at any point may change from "working" to "working". You don't want to force people to change status to "broken" and back, just to make an observation look more fresh. Note that a very typical HOT team activity is to visit all of a certain feature type and verify if it they work (think wells, fire hydrants, sewers, gates, health clinics, sanitation facilities, etc). Such ground surveys are always "as of" a given date.
_______________________________________________ HOT mailing list [email protected] http://lists.openstreetmap.org/listinfo/hot
