f536c346 by Mike Mathews

Updated definitions for Floors.

1 parent 7f961ad6
......@@ -624,12 +624,21 @@
provided here is based on an external consideration. Typically only the common spatial types are used: Circle, Ellipse, Spheroid, and Ellispoid shape types.
</comment>
</elem>
<elem name="floor" type="Tensor.int16" multiplicity="0..1">
<elem name="floor" type="Tensor.float32" multiplicity="0..1">
<comment>
Optional floor specifier if availble. Floor values are specified by local venue mapping information. As general guideline, 0 denotes the ground-level floor.
Negative values denote floors under ground.
Optional floor number if availble. Floor number are specified by local venue mapping floor index. As general guideline, 0 denotes the ground-level floor.
Negative values denote floors underground. Ideally, numbers should be linear and not have jumps common with many building label schemes (e.g. floor 13 is
not present). The floor number may be a calculated quantity derived from multiple data sources, which may result in partial floor estimtes (e.g. returns floor 2.5).
The floor number is useful for indexing data. See floorLabel for a descriptive floor identifier.
</comment>
</elem>
<elem name="floorLabel" type="string" multiplicity="0..1">
<comment>
Optional descriptive floor label if available. Floor labels are useful to provide a floor specifier not readily indexed like floor number. Examples include
'Lobby', 'Parking 1', 'Parking 2', 'Mezzannine 1', '12', '14', 'Observation Deck', etc. In cases, where the result is between floors, the floor label may
specify a compound label such as 'P1/P2' if supported.
<comment>
</elem>
</struct>
<!-- eventually may be able to support variable sized elements
......
Styling with Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!