Upload GeoTiff Error You can't execute queries until the end of the 'atomic' block about geonode-importer HOT 10 CLOSED

Hi @jeff-bradley
Did you try with a different GeoTiff or always happen?
Just to understand if is something related to the GeoTiff or to the import flow

from geonode-importer.

Hello @mattiagiupponi
I was able to successfully load a very small test geotiff, but I received the error on both the wind and solar from these downloads
https://sitewindright.s3.amazonaws.com/KeyWildlifeAreas_Wind_GT_20211113.zip
https://sitewindright.s3.amazonaws.com/KeyWildlifeAreas_Solar_GT_20210907.zip

from geonode-importer.

Ok is not happening on all GeoTiff (which is a good point)
I try in local and looks like that the importer is extracting as CRS EPSG:5070 which is not one of the default accepted format.
@giohappy do you have any hints on this? how should we proceed?

from geonode-importer.

Thanks @mattiagiupponi I was able to load the GeoTiff after I transformed it to EPSG:3857

from geonode-importer.

Thanks @mattiagiupponi I was able to load the GeoTiff after I transformed it to EPSG:3857

Great news, I'll keep this open waiting an input from @giohappy. Then we can close the issue

from geonode-importer.

I've reopened and tranfered the issue inside the importer repo.

@mattiagiupponi in case of unsupported CRS a more informative error should be returned by the importer.
"An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block. Request: None" is very cryptic, to say the least :)

from geonode-importer.

May I ask if adding additional CRSs in Geoserver would also solve this problem? As described here: https://docs.geoserver.org/2.23.x/en/user/configuration/crshandling/customcrs.html

But I agree, that a better error message is key here ;)

from geonode-importer.

@jeff-bradley after some troubleshooting we found that the problem is with the CRS assigned to the Geotiff. It's not EPSG:5070 but ESRI:102039. Geoserver doesn't parese this CRS correctly (to be investigated why) but it creates the layer: Everything is fine if we reproject the original tiff to EPSG:5070.

We are going to open an issue for the importer to trigger a rollback if Geoserver fails at returning a valid CRS before pubslighing the dataset in GeoNode.

from geonode-importer.

I just merge a PR which will raise a clear error if the Srid is not recognied correctly.
At least should be more clear the issue instead of the "atomic block" exception

from geonode-importer.

This was resolved via #198

from geonode-importer.