| 5 | | after all, an elevator may have different features on each level (for example on which side the doors open) |
| | 5 | ~~after all, an elevator may have different features on each level (for example on which side the doors open)~~ |
| | 6 | well, this could still be tagged using a single node, I guess, |
| | 7 | and osm wiki actually has documentation to this: |
| | 8 | [http://wiki.openstreetmap.org/wiki/Key:level#Multiple_values] |
| | 9 | |
| | 10 | But for the store level abstraction above this does not seem to apply. These are three distinct building levels and |
| | 11 | using the indoor mapping proposal they will be represented by one object each. So shouldn't the node that seems like |
| | 12 | a predeccesor to that in this case also exist in a distint way for each level? |
| | 13 | |
| | 14 | If the three building levels ''were'' already indoor-mapped, the store would probably be expressed as a relation |
| | 15 | to these, after all. |
| | 16 | |
| | 17 | All I'm saying is, that wrt this ticket, a node that represents an elevator would be a better example, since its a |
| | 18 | less questionable valid data example. |
