Proposal:Flooded
Jump to navigation
Jump to search
flooded | |
---|---|
Proposal status: | Abandoned (inactive) |
Proposed by: | BGNO |
Tagging: | flooded=* |
Applies to: | |
Definition: | Key for mapping the physical condition under which a given traffic way is flooded. |
Statistics: |
|
Draft started: | 2014-01-04 |
RFC start: | 2014-01-05 |
Description
The purpose of the key is to map the physical condition under which a given traffic way is flooded.
Examples:
- Tidal roads and paths:
flooded = high_tide - In some countries certain river beds are used as roads, which cannot be passed by cars during the rainy season:
flooded = rainy_season
Rationale
The new key proposed here can be a significant help for route-planning.
Advantages
- Unified notation for tidal traffic ways and traffic ways that are flooded in the rainy season.
- General applicability. The feature can be used for roads as well as for any other traffic way. (see Proposed features/Tidal_road and Proposed features/Tidal_path)
Why not use access=* or opening_hours=* instead of a new key?
Because access and opening_hours stand for legal restrictions whereas flooded stands for physical conditions. These types of information are independent and should consequently be tagged independently.
Values
The values describe the condition under which the traffic way is flooded:
- flooded = rainy_season
- flooded = high_tide
See also
- Key:flood_prone - previous tagging of dangerous areas
- Proposed features/Tidal_road
- Proposed features/Tidal_path
- tidal=*