Key:operational_status
operational_status |
Description |
---|
Observation of the current functional status of a mapped feature - now discouraged |
Group: lifecycle |
Used on these elements |
Documented values: 2 |
See also |
|
Status: in use |
Tools for this tag |
|
There are established alternatives for this tag. Consider using a lifecycle prefix such as disused:*=*, abandoned:*=* or construction:*=*, or in some cases a lifecycle tag such as disused=*, abandoned=* or construction=*, see Comparison of life cycle concepts. |
The key operational_status=* has been used in the past to document an observation of the current functional status of a mapped feature.
In the past this tag was sometimes used by the HDM for Humanitarian mapping projects, for example with amenity=drinking_water. It has also been used with building imports and some organized mapping activities.
Values in use
A wide variety of similar values have been used with this key, many with overlapping meanings.
Positive (functional / operational):
- operational_status=operational Facility was observed to be operating and serves its basic function
- operational_status=open
- operational_status=ok
- operational_status=functional
- operational_status=yes
limited :
- operational_status=needs_maintenance Facility serves its basic function, but something is broken or missing
- operational_status=restricted Facility serves its basic function, but there is some limitation
Negative (Not operational or function):
operational_status=closeduse disused:*=* instead- operational_status=broken
operational_status=out_of_order- operational_status=non-operational (also in use: operational_status=non_operational and other variants, see discussion.)
- operational_status=under_construction
Uncertain:
Problems
Note that operational_status=out_of_order and similar tags are highly problematic and are form of trolltag.
If place has no drinking water then amenity=drinking_water should not be placed there. For places where no longer working drinking fountain or some its remains are present lifecycle prefixes are more fitting. disused:amenity=drinking_water/broken:amenity=drinking_water/etc would be superior.
Expecting that all data consumers will check and exclude operational_status=broken operational_status=closed operational_status=non-operational operational_status=under_construction operational_status=non_operational and other such tags is not reasonable, as list of such values (and keys) may expand at any time.
It is similar to marking prison as tourism=hostel involuntary=yes and expecting that data consumers and other mappers will support this.
Synonymous tags in use
See also
- Comparison of life cycle concepts
- Lifecycle prefixes: disused:*=*, abandoned:*=*, construction:*=* etc.
- Lifecycle tags: disused=*, abandoned=*
- Humanitarian OSM Tags/operational_status