org.opengis.referencing.datum
Interface VerticalDatum

Show UML class diagram

All Superinterfaces:

Datum, IdentifiedObject

@UML(identifier="CD_VerticalDatum",
     specification=ISO_19111)
public interface VerticalDatum
extends Datum

A textual description and/or a set of parameters identifying a particular reference level surface used as a zero-height surface. The description includes its position with respect to the Earth for any of the height types recognized by this standard.

There are several types of Vertical Datums, and each may place constraints on the Coordinate Axis with which it is combined to create a Vertical CRS.

Since:

1.0

See Also:

DatumAuthorityFactory.createVerticalDatum(String), DatumFactory.createVerticalDatum(Map, VerticalDatumType)

Field Summary

Fields inherited from interface Datum

ANCHOR_POINT_KEY, DOMAIN_OF_VALIDITY_KEY, REALIZATION_EPOCH_KEY, SCOPE_KEY

Fields inherited from interface IdentifiedObject

ALIAS_KEY, IDENTIFIERS_KEY, NAME_KEY, REMARKS_KEY

Method Summary

VerticalDatumType

getVerticalDatumType() The type of this vertical datum.

Methods inherited from interface Datum

getAnchorPoint, getDomainOfValidity, getRealizationEpoch, getScope

Methods inherited from interface IdentifiedObject

getAlias, getIdentifiers, getName, getRemarks, toWKT

Method Detail

getVerticalDatumType

@UML(identifier="vertDatumType",
     obligation=MANDATORY,
     specification=ISO_19111)
VerticalDatumType getVerticalDatumType()

The type of this vertical datum.

Returns:

The type of this vertical datum.

See Also:

Datum.getAnchorPoint()

Departure from OGC/ISO specification:
This attribute is kept conformant with the specification published in 2003. The 2007 revision of ISO 19111 removed this attribute, since this information can be encoded in the anchor point. However GeoAPI keep this attribute for historical reasons, and because it provides some of the anchor point information in a programmatic way more suitable to coordinate transformation engines.

Note that GML defines the anchor point as a code list, which address the programmatic needs. In GeoAPI the anchor point is rather defined as an international string, thus the need for equivalent information as a code list.