Object
Departures
Departures in GeoAPI interfaces compared to OGC/ISO schemas.
Each
Departures instance is initialized with a default set of departure information.
More departure can be added by calls to add(…) methods.- Since:
- 3.1
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidaddMergedType(String toRetrofit, String target) Adds a class to be retrofitted into another class.voidaddSpellingChange(String uml, String xsd) Changes the spelling of an identifier.
-
Constructor Details
-
Departures
public Departures()Creates new collections of departure information. All maps in public fields (mergedTypes, etc.) are initialized with new instances and populated.
-
-
Method Details
-
addMergedType
Adds a class to be retrofitted into another class. For example, ISO 19115-2 definesMI_Bandas an extension of ISO 19115-1MD_Band, but GeoAPI merges those two types in a single interface for simplicity.- Parameters:
toRetrofit- name of the type to retrofit into another type. Example:MI_Band.target- name of a type which will receive the properties of the retrofitted type. Example:MD_Band.
-
addSpellingChange
Changes the spelling of an identifier. The differences may be for historical reasons, or in a few cases because of a misspelling in the XSD file compared to the UML.- Parameters:
uml- the spelling in the UML, including class name. Example:"LI_ProcessStep.stepDateTime".xsd- the spelling in the XSD file. Example:"dateTime".
-