FME can read and write files in the OGC Geography Markup Language (GML) format.
GML is an OpenGIS® Implementation Specification. The GML specification defines an XML encoding for the transport and storage of geographic information. This specification can be found at the Open GIS Consortium website www.opengeospatial.org.
GML documents must be instances of a conforming application schema. Conforming application schemas are to be defined with the W3C’s XML Schema language.
Versions
GML 3.3.1*, 3.2.2, 3.2.1, 3.1.1, 2.1.2 files, and application schema.
*We support most (but not all) GML 3.3.1 schemas.
For additional version information, refer to the Formats: OGC Standards table in FME and OGC Open Standards.
Reader Overview
Multi-value properties (that is, declared with a maxOccurs that is greater than 1 or unbounded) are supported and are mapped into list attributes. Null values are not read unless they are nillable.
GML properties that are defined as complex types are supported – these complex properties are mapped as structured list attributes.
This reader supports multiple geometry properties per feature type: see the Map Geometry Columns reader parameter.
Writer Overview
The GML writer may either write to an existing GML Application Schema, or output a dataset and a schema document corresponding to the GML writer’s feature type definitions. To generate GML based solely on the feature type definitions, the GML Version parameter must be set to 3.1.1 (which is the default) or 3.2.1.
The GML application schema structure is controlled by the GML writer’s user attributes. The writer will create an XSD that is based on the writer feature type definitions, in the same folder and with the same file basename as the output dataset. Two XML documents are written: a GML instance document, and its corresponding GML application schema.
To write to an existing GML Application Schema, the writer’s GML Version parameter must be set to Application Schema, and a valid accessible GML application schema provided in the Application Schema parameter (local file path or URL). In this mode, the GML writer will write a single GML dataset file corresponding to an existing GML Application Schema. No XSD will be written.
Additional GML Formats
FME supports these additional GML formats:
|
Format Name |
FME Short Name |
|---|---|
|
AIXM 5.x (Aeronautical Information Exchange Model GML) Reader/Writer |
AIXM5 |
|
BC MoF Electronic Submission Framework – (XSD-Driven) Reader/Writer |
ESF_XSD |
|
BC MoF Electronic Submission Framework (ESF) Reader/Writer (deprecated) |
ESF |
|
CUZK_GML |
|
|
TOP10 |
|
|
TOP50NL |
|
|
NAS (ALKIS) |
|
|
HERE_VENUE_MAP |
|
|
INSPIRE |
|
|
JPEG2000 |
|
|
KOMMUNGML |
|
|
KUNTAGML |
|
|
NEN3610 |
|
|
MTKGML |
|
|
CITYGML |
|
|
OGC GML SF-0 (Geography Markup Language Simple Features Level SF-0 Profile) Reader/Writer |
GMLSF |
|
GML2, GML212 |
|
|
INDOORGML |
|
|
SEABEDML |
|
|
SOSI_GML |
|
|
I2KGML |
|
|
CH.EHI.FME.MAIN |
|
|
TIGERGML |
|
|
OS_MASTERMAP_GREENSPACE_GML |
|
|
OS_MASTERMAP_HIGHWAYS_NETWORK_GML |
|
|
OS_MASTERMAP_SITES_GML |
|
|
OS_MASTERMAP_TOPOGRAPHY_GML |
|
|
UK OS MasterMap Topography Layer (Non-XSD-Driven, GML v2.1.2) Reader |
DNF |
|
OS_MASTERMAP_WATER_NETWORK_GML |
|
|
OSVECTORMAPDISTRICT |
|
|
OSVECTORMAPLOCAL |