For consistent and correct handling of geometry in our backend, we need vector cubes.
This code path was still emitting shapely geometry objects, for no clear/good reason, causing unexpected behaviour:
https://github.com/VITO-RS-Vegetation/lcfm-production/issues/88
The error logs show clearly that geometry with different CRS's was incorrectly combined when vector cubes are not used.
Next to that, annoying messages were printed in the logs:
geojson_to_geometry usage is deprecated and should be replaced by proper vector cube usage
_normalize_geometry: TODO are we still reaching this code?
This pr suggests to get rid of all that via a simple translation to vector cube, which is a code path with much better support and normally also test coverage.
@soxofaan @JeroenVerstraelen I can add a unit test, but would first like to learn if there were reasons to not do this?
For consistent and correct handling of geometry in our backend, we need vector cubes. This code path was still emitting shapely geometry objects, for no clear/good reason, causing unexpected behaviour: https://github.com/VITO-RS-Vegetation/lcfm-production/issues/88
The error logs show clearly that geometry with different CRS's was incorrectly combined when vector cubes are not used.
Next to that, annoying messages were printed in the logs:
This pr suggests to get rid of all that via a simple translation to vector cube, which is a code path with much better support and normally also test coverage.
@soxofaan @JeroenVerstraelen I can add a unit test, but would first like to learn if there were reasons to not do this?