Florian Esser

I'd be ok with closing it. Can always be reopened in case this affects a user in the future.

@Kate-Lyndegaard Are you sure that the `srsName` attribute is allowed in the `PolygonPatch` element? From a superficial check it looks like that `PolygonPatch` does not inherit from `AbstractGeometryType` and, therefore,...

Thanks for the clarification, @stempler and @Kate-Lyndegaard!

The commit message and the PR should also reference the related GitHub issue #1085

> The commit message and the PR should also reference the related GitHub issue #1085 The closing keyword (e.g. "Closes" or "Fixes") is still missing (see [discussion here](https://github.com/halestudio/hale/pull/1184#pullrequestreview-2070984515))

Shouldn't PRs only be merged after the corresponding ticket is challenged? I'm wondering because the merge now closed #1085 even though the challenge on ING-4129 was not done yet.

That warning is generated [here](https://github.com/halestudio/hale/blob/479017ea2b7fea81c5314f03cf6442f9427a44cd/io/plugins/eu.esdihumboldt.hale.io.jdbc.postgresql/src/eu/esdihumboldt/hale/io/jdbc/postgresql/PostGISGeometries.java#L111). It looks like the `srid` returned by [this query](https://github.com/halestudio/hale/blob/479017ea2b7fea81c5314f03cf6442f9427a44cd/io/plugins/eu.esdihumboldt.hale.io.jdbc.postgresql/src/eu/esdihumboldt/hale/io/jdbc/postgresql/PostGISGeometries.java#L89) is `0`. At first glance this looks like an error in the geometries.

> It would definitely be nice to have a more robust way of cancelling the transformation, or the option to not automatically trigger an transform when you implement a large...

If we change the current behaviour to always write the target attribute regardless of the input variable, we are not backwards compatible anymore, i.e. transformations run w/ e. g. hale...

TODO: Add reproduction case