Geometry Support

The types of Geometries that can be read by 1Integrate are dependent on the type of data.

The types of geometry generally supported are:

  • 2D
  • 2.5D (geometries with a height at each vertex, but not volumes or vertical lines or surfaces).
  • 2D with measures

1Integrate geometry support has the following capabilities:

  • Geometries can be single or multi-part
  • Polygons can have zero or multiple inner rings

  • Circles or geometries with circular Arcs are supported, but:

    • For Oracle data or data formats read by FME (the formats listed in the data store interface with (FME) at the end, see Data Stores), the geometries are densified into a set of smaller straight line segments as an approximation of the shape of the arc or circle on import. This means that the circular arcs will be converted to a multiple-straight line approximation when written back out.

  • Optimised rectangles in Oracle geometries are converted into a normal polygon on import.

Features with Geometries that are null or fundamentally invalid are not loaded unless the Data Store is set to Allow Invalid Geometries. These can be read in to allow them to be detected or fixed.

Note: Spatial operations on invalid geometries are not guaranteed to succeed until they are fixed.

Reading Invalid Geometries

You can enable or disable the Allow invalid geometries option when specifying input details for data stores (see Input Connection).

By default this is not enabled, which means that features with invalid geometries are not read in, and are counted as errors in an Open Data task within a session.

This alerts users to geometries that are fundamentally invalid and avoids them causing later problems within a session. When this option is ticked it allows the open data task to read in the geometries even if they are invalid, allowing reporting using rules, or allows them to be corrected using actions.

Invalid geometries include null geometries, geometries with duplicate consecutive vertices, lines with fewer than two points, or polygons with problems such as:

  • Outer rings that do not enclose inner rings
  • Self-touching rings
  • Rings that intersect other rings
  • Rings containing duplicate points

When these features are loaded then you can use:

  • Validation rules to validate the data using built-in functions such as has_duplicates or is_valid
  • Fix-up actions to fix the data using built-in functions such as remove_duplicates