Proposed Model Transformation Rule: Fan-Out Features by Geometry Type

[jsaligoe]

Review Feedback
For consideration, a Model Transformation (MT) rule to fan-out features into separate feature classes depending on the geometry type.

MT00X: (PROPOSED) Fan-Out Features by Geometry Type

Category
Simplification

Description
To improve usability within standard GIS systems, the geometry type may be fanned-out into multiple feature classes for portrayal in layers.

Some INSPIRE spatial object types allow instances to carry a range of geometry types (for example, either a point, line string, or polygon). Mixed geometry types in a single feature layer are not supported in desktop GIS software. Rather, points, lines, and polygon geometry types must be represented in separate feature classes depending on the geometry type. As a result, these INSPIRE spatial object types are fanned-out to multiple feature classes with different geometry types.

Original vs. Transformed UML Model, where applicable

Original instance in default encoding

Transformed instance in default encoding, where applicable

Model Transformation Rule
Parameters:
• separator: The character to use to separate the original property name from the type name of the components.

Instance Transformation Rule

Solved Usability issues
In standard GIS systems it is not feasible to mix geometry types in the same feature class.

Known Usability issues
None.

INSPIRE compliance conditions and reversibility
Data transformed using this rule is INSPIRE compliant as long as there is no information loss from the source data. Data in separate feature classes may still be complex, therefore other rules may still be needed, e.g., MT001: Flatten Nested Structures.

Examples of use
Fanning-out of geometry types to multiple feature layers is used in ELF and in ArcGIS for INSPIRE Geodatabase to make data fit for purpose.

Additional notes
None.

Other comments

Examples to be provided. For further consideration, to maintain uniqueness of the feature class names and indicate the geometry type, may want to add a code to the end of the feature class name, e.g., Point, Line, Shape.