> > #8: Altitude type of 0 == no altitude
> > ---------------------------------------+-------------------------------
> > -----
> > Reporter: martin.thomson@andrew.com | Owner:
> > Type: defect | Status: new
> > Priority: major | Milestone:
> > Component: rfc3825bis | Version:
> > Severity: - | Keywords: altitude
> > ---------------------------------------+-------------------------------
> > -----
> > RFC 3825 seems to indicate that an altitude type of 0 indicates that
> > there
> > is no altitude defined.
>
>Just wondering: if that is really the case, how is sea level indicated?
Glen -- there are several "sea levels" actually, a few (in no particular order)
- Mean Low Tide (MLT)
- Mean Lowest Low Tide (MLLT)
- Mean Tide (MT)
- Mean High Tide (MHT)
If we are getting into the weeds of having to be specific here, then
each datum needs to specify which vertical datum (i.e., altitude) is
ZERO; as each of these (and a few more) are used; though some are rarely used.
> > This needs to be clearer in the bis.
> >
> > Q: is altitude type 0 valid?
> >
> > Q: what meaning is attached to altitude type 0?
> >
> > Q: what is the impact of having no altitude on the existing datum
> > definitions?
> >
> > --
> > Ticket URL: <http://trac.tools.ietf.org/wg/geopriv/trac/ticket/8>
> > geopriv <http://tools.ietf.org/geopriv/>
> >
> > _______________________________________________
> > Geopriv mailing list
> > Geopriv@ietf.org
> > https://www.ietf.org/mailman/listinfo/geopriv
>
>
>_______________________________________________
>Geopriv mailing list
>Geopriv@ietf.org
>https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
