Proposal:Fitness station
Proposal status: | Inactive (inactive) |
---|---|
Proposed by: | MeastroGlanz |
Tagging: | fitness_station=* |
Applies to: | type |
Definition: | tag different fitness equipment within a fitness station |
Statistics: |
|
Rendered as: | leisure = fitness_station |
Draft started: | 2017-05-23 |
RFC start: | 2017-05-23 |
[[Category:Proposals with "Inactive" status|]]
This Tag was established in the fitness_trail article, of which some of its content had been transferred to the fitness_station article. Therefore, this proposal is set on "inactive".
Proposal
This key should contain different fitness equipment just like Key:playground maps different equipment on a playground.
Rationale
The need for this key came up, when I wanted to map the fitness_trail 7273471 7273471 with more details. The details are interesting for future development of i.e. fitness-apps.
Examples
https://www.trimm-dich-pfad.com/ has listed over 700 fitnesstrails only in Germany. Assuming that each fitness trail consists of at least 15 stations, this means, there are potentially up to 10.000 objects of this type just in Germany.
I tagged the 7273471 7273471 in that way to give an example.
Tagging
Some objects are tagged as fitness_station. This objects are grouped in a multipolygon relation tagged leisure=fitness_station. This fitness stations are part of the relation route=fitness_trail.
Proposed values are so far:
- fitness_station=sign Normally every station consists of at least one sign with ref=<number>, name=<name> and instruction (not mapped).
- fitness_station=balancing
- fitness_station=horizontal_bar
- fitness_station=hurdles
- fitness_station=knee_bends
- fitness_station=leapfrog
- fitness_station=pushups
- fitness_station=sit_ups
- fitness_station=stairs
- fitness_station=stretching
Applies to
nodes, ways and areas; in special cases relations
Rendering
will follow
Features/Pages affected
route=fitness_trail leisure=fitness_station
External Discussions
none
Comments
Please comment on the discussion page.