Hi everyone,I'm seeing some unexpected behaviour when writing repaired geometries to a GeoPackage.My workflow is:GeometryValidator (Attempt Repair = Yes) → GeoPackage Writer → GeoPackage Reader → GeometryValidatorBefore writing:Input: 32,572 Passed: 10,720 Repaired: 21,852 Failed: 0After reading the GeoPackage back:Input: 32,572 Passed: 31,789 Failed: 783 (Invalid Parts)I also noticed another behaviour:When Spatial Standard Compliance is included in the first GeometryValidator, the written GeoPackage appears to preserve more polygon coverage. When I disable Spatial Standard Compliance, all features still pass after repair, but after writing and reading the GeoPackage back, more features fail validation.Has anyone experienced this before?Is this expected behaviour of GeometryValidator/GeoPackage, or should the repaired geometries remain valid after being written and read back?Before writingAfter writing

Question

GeometryValidator repaired features become invalid again after writing to GeoPackage

+3

Hi everyone,

I'm seeing some unexpected behaviour when writing repaired geometries to a GeoPackage.

My workflow is:

GeometryValidator (Attempt Repair = Yes)       → GeoPackage Writer       → GeoPackage Reader       → GeometryValidator

Before writing:

After reading the GeoPackage back:

I also noticed another behaviour:

When Spatial Standard Compliance is included in the first GeometryValidator, the written GeoPackage appears to preserve more polygon coverage.
When I disable Spatial Standard Compliance, all features still pass after repair, but after writing and reading the GeoPackage back, more features fail validation.

Has anyone experienced this before?

Is this expected behaviour of GeometryValidator/GeoPackage, or should the repaired geometries remain valid after being written and read back?