Geography Markup Language (GML)

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

Read and Write Support

Read	Write
Read	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 Full 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.

Parameters

Read and Commit

Parameter	Description
Source Files Required:.xml, .gml and .xsd Zipped: .zip/.gz	Click the Upload button and drag and drop the file anywhere or click to browse. All files must be zipped together for the upload. Note: For .xsd files you must consider the following: GML does not support folders. .xsd files must be at the root of the zip and once uploaded are added to the schema. You must ensure that all classes required to resolve the schema hierarchy are included in one of the .xsd's.
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. The input format will be `SRID=######` for Spatial Reference Identifiers (SRID) and `EPSG=######` for EPSG codes. See Coordinate Reference System for more information on this parameter, and when it may be required. 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: When you override the CRS you must refresh the Data Store's schema before it will take effect. Note: Coordinate Reference System parameters are required in a session that will write data to Oracle.
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	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.
Read all Geometries as 2D	If selected, all geometries will be read as 2D and any Z or M coordinates will be discarded.

1Integrate v 5.1

Copyright © 2025 1Spatial