Comment(by bernard_aboba@…):
Here is the proposed text for Sections 2.4, 2.4.1 and 2.4.2 (text for
Section 2.4.3 is covered in Issue 41).
2.4. Altitude
How the Altitude value is interpreted depends on the Altitude Type
(AType) value and the selected datum. Three Altitude Type values are
defined in this document: unknown (0), meters (1) and floors (2).
2.4.1. No Known Altitude (AType = 0)
In some cases, the altitude of the location might not be provided.
An Altitude Type value of zero indicates that the altitude is not
given to the client. In this case, the Altitude and Altitude
Uncertainty fields can contain any value and MUST be ignored.
2.4.2. Altitude in Meters (AType = 1)
If the Altitude Type has a value of one, Altitude is measured in
meters, in relation to the zero set by the vertical datum. For AType
= 1, the Altitude value is expressed as a 30 bit, fixed point, twos
complement integer with 22 integer bits and 8 fractional bits.
--
---------------------------------------+------------------------------------
Reporter: bernard_aboba@… | Owner: bernard_aboba@…
Type: defect | Status: new
Priority: major | Milestone: draft-ietf-geopriv-3825bis
Component: rfc3825bis | Version: 1.0
Severity: Submitted WG Document | Keywords:
---------------------------------------+------------------------------------
Ticket URL: <http://trac.tools.ietf.org/wg/geopriv/trac/ticket/42#comment:2>
geopriv <http://tools.ietf.org/geopriv/>
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
