Execute failed: CRS appears to be JSON but is not valid

[Awiener]

Hi all,

with the current 5.5.1 I see a lot of CRS errors, especially when working with non-spatial Nodes. For me it looks like some of them (the older ones?) are not capable of handling the geometry column as they should.

I get these errors a lot lately:

Execute failed: CRS appears to be JSON but is not valid

File "...\KNIME\bundling\sdl_harvard_geospatial_channel_bin_2.0.0\.pixi\envs\default\Lib\site-packages\pyproj\crs\crs.py", line 137, in _prepare_from_string
    raise CRSError("CRS appears to be JSON but is not valid") from err
pyproj.exceptions.CRSError: CRS appears to be JSON but is not valid

When I change them with newer versions of the same nodes (the workflow is at least 5 years old), some of the errors don’t occur anymore. However most of them persist.

Is there any way, to see what is stored within the geometry column? Copy + Paste only shows the coordinate pairs, but none of the logic:

I’ve reprojected the CRS to a UTM CRS, so maybe this is the initial problem, however shouldn’t be.

Thanks for any hints!

Maybe @tobias.koetter has an idea?

and again:

[Awiener]

Ok, I found one issue: It looks like saving and opening as Geoparquet can be an issue for projected CRS.

Issue_CRS.knwf (20.4 KB)

[Awiener]

ok, got it. Not all EPSG Codes are working similar, some of them produce the issues.

epsg:25832 does not work, although 10289 is working…