Geography Markup Language (GML)

The Geography Markup Language data store is available for Reading data in 1Integrate.

Read and Write Support

Read	Write		FME Required
	Commit	Copy To

Data Support

Data	Support	Notes
Non-Spatial
2D
Measured
Heighted		All 3 coordinate geometries are assumed to be XYZ.
3D		For more information about 3D data in 1Integrate, please refer to 3D Support.

Key Information

• Only GML 3.0 is supported, with no deprecated tags.

• Nested objects are not supported.

• Links are not supported.

• All curves are treated as linear.

Input and Output Parameters

Input Parameters

Parameter	Description
Source Files (.csv, .gz, .txt)	Drag and drop your file into the window, or click within the upload box and navigate to the file on your network. Note: You will need to upload the schema (.xsd) alongside the GML data in a zip file.
Include gml:id	Select to include the gml:id field in the schema.
Keep class namespace prefix	Select if class names should keep prefixes (e.g. org:BUILDING with prefix, or BUILDING without).
Coordinate Reference System	This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically. This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined). Note: Coordinate Reference System parameters are required in a session that will write data to Oracle. See Coordinate Reference System for more information on when this is required.
Allow invalid geometries	Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported. This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.
Fix ring direction and inclusion errors	Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise. If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data. Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.