Subworkflow: Buffer --> Execute failed: Invalid projection

[Awiener]

ok, so the Container Input (Table) node does not recognize any other CRS than 4326, or changes every other CRS to 4326.

Caller

Callee:

You can prove the output of the Container Input (Table) node with a Geopackage Writer: not matter which CRS you choose, it’s stored as 4326.

But it somehow destroys the geometry as well. That’s the result of the Geopackage output:

I’d say, that’s a bug, how about the Knime guys? @tobias.koetter ? @ScottF ?

And now it would be great to have something like a QM Node…

Geospatial: Check Geometry Node for quality issues

Hi, as often the input quality of datasets is “not great”, it would be great to have something like a Check Geometry Node. Shapely provides something like this with shapely.is_valid_reason — Shapely 2.1.2 documentation and shapely.make_valid — Shapely 2.1.2 documentation It would help a lot when working with corrupted or otherwise difficult datasets. Thanks!