Proposal:Conveying:time
| Duration for escalators and moving alkways | |
|---|---|
| Proposal status: | Draft (under way) |
| Proposed by: | Bstein |
| Tagging: | conveying:duration=hh::mm::ss |
| Applies to: |  
|
| Definition: | the time a full ride on an conveying object takes, without actively moving (walking) |
| Statistics: |
|
| Rendered as: | not rendered visually, but affects routing time |
| Draft started: | 2019-12-28 |
Proposal
The tag conveying:duration=* can be added to conveying objects, to define how long a single ride takes.
Rationale
There are escalators and moving walkways with different speeds. Routers should be able to evaluate this. Tagging the time one ride takes instead of the actual speed is both practical for routing software and easy to map. All mappers need is a (stop)watch while they use the conveying way. Conveying features are very present at stations, airports and other transportation hubs. Places with special need for accurate short-range routing for changeover times.
Examples
Tagging
conveying:duration='hh::mm::ss', for example conveying:duration=00::00::47.
Applies to
highway=steps or highway=footway and conveying=*
Rendering
Routing
The value is used as the time it takes to move along the object.
Map
There is no need for this feature to be visualized. However, it can be visualized for certain use cases: calculate the speed (time/lenght of object) and assign a colour map to the values. Similar to the way ITO map maxspeed did.
Features/Pages affected
External discussions
- should seconds or minutes be default?
- should the existing tag duration=* be used?
Comments
Please comment on the discussion page.