Talk:Proposed features/Tag:operational status

From OpenStreetMap Wiki
Jump to: navigation, search

But, there's more

Life cycles have quite a few more stages than are yet codified in OSM tags. For example:

  • Citizen concept (no landowner/government involvement yet)
  • Proposed
  • Planned
  • Under construction
  • Operating
  • Broken (but expected to be fixed)
  • Disused (not expected to be fixed). Shades of this include abandoned, vacant, empty.
  • Preserved (e.g. a stabilized ruin).
  • Converted (e.g. historic:railway=funicular).
  • Proposed for removal.
  • Under demolition.
  • Historic.
  • Rebuilt.

Brycenesbitt (talk)

Agree to move forward - with other usage

I agree with Bryce that operational_status is a useful key. I would suggest it also applies to various public services besides toilets and such, and should be used in conjunction with the emergency=* key; i.e. fire_extinguishers, emergency_phones, and especailly aed's as these have a battery life.


"(inserted automatically)"

What by? Please specify, and acknowledge that normal mapping software will not do this. --achadwick (talk) 14:30, 5 July 2013 (UTC)

Shares the same problems as the old styles of using disused/abandoned

Strongly disagree with this article in its current state. It suffers from the same issues as disused=* and abandoned=* prior to their rehabilitation. The example is a case in point: if a public toilet is closed, then it should not be tagged with amenity=toilet, though it could still be tagged as a building. Sure, your rendering may do something special with {operational_status=closed, amenity=toilet}, but no-one else's will, and that will be misleading and inconvenient. For emergency facilities it may even be dangerous. Formalizing this tag in this way encourages other mappers to enter bad data too, so the article really needs fixing.

Please find a different way of expressing this concept that doesn't result in new tags contradicting old ones. Don't get me wrong: if it's helpful to people to use the OSM db for identifying broken water pumps or other specific kinds of facilities, that's a really cool use of OpenStreetMap. But it shouldn't be done at the expense of correct data for all users.

For what it's worth, a standardized namespace prefix to be used when an item is inoperable or defunct is possibly the least worst approach. May I suggest recommending inoperable:<oldname>=<value>, as a nod to the name of the proposed tag? For use only when the object cannot be operated / does not provide basic functionality, of course

--achadwick (talk) 16:56, 5 July 2013 (UTC)

The use of inoperable:<oldname>=<value> hides it from most maps and processing software, which is really undesirable for facilities that are likely to be repaired. The goal here is for objects to retain their database identities as whatever they are, but add a (possibly useful) observational note. (e.g. 'it is still a hospital, but the windows were blown out by the storm'). Brycenesbitt (talk)
If it needs fixing so bad that it can't be used as a hospital, it's not a hospital, until it's fixed. If it needs fixing, but still operates as a hospital, it is a hospital. Duck tagging and all that. It's easier for specialists (so-to-say) interested in finding facilities needing a fix to check other values, than for everybody to check a myriad of tags (like inoperable=yes, broken=yes, disused=yes etc.), or an unconstrained set of values of operational_status. Alv (talk) 08:08, 22 July 2013 (UTC)