Key:state
Aller à la navigation
Aller à la recherche
 state
|
| Description |
|---|
Operational state of a route relation or route section. 
|
| Group: routes |
| Used on these elements |
    |
| See also |
|
| Status: in use |
| Tools for this tag |
The key state=* is in use on route relations to document the current operational state of the route.
An alternative to state=proposed is to use the prefix proposed:*=*, that is, proposed:route=* - this makes it clearer to database users that this route is not yet in existence, and has other advantages.
The most common values currently in use are:
state=proposed: route proposed but not yet signposted/in operationstate=connection: a connecting route but not part of the core route. See also Role:connection for individual route membersstate=alternate: an alternate route but not part of the core route. See also Role:alternative for individual route membersstate=temporary: a temporary detour
Software support
Routers and renderers may behave differently depending on the value. For example, state=proposed causes CyclOSM, OpenCycleMap, and OsmAnd to deemphasize the route but causes cycle.travel and Waymarked Trails to hide it entirely. The vector fork of OpenRailwayMap also deemphasizes state=proposed.
See also
- Lifecycle prefix -
proposed:*=*as the less problematic alternative proposed=*- The proposed tag may be used for any road, railway or route that is in planning phase.condition=*- Describes the physical condition of an object (good, bad)operational_status=proposed- deprecated