You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the GeoNode exported datasets as GeoPackage has case-sensitive Geometry-Types which can't be read from the GeoNode (e.g MultiPolygon instead of MULTIPOLYGON)
#12725
Open
ffischer1984 opened this issue
Nov 19, 2024
· 0 comments
When I'm exporting a Dataset in the GeoPackage-Format I'll expect that I can import the exact same GeoPackage-File into a GeoNode-Instance, again.
Actual Behavior
When I'm trying to import an exported GeoPackage-File from a geonode-instance I'll get this error-message:
""Found geometry_type_name: MultiPolygon for table nz_primary_parcels_9748d5b75426d9bbcb35b64365387811 (from the gpkg_geometry_columns table).. Error layer: nz_primary_parcels_9748d5b75426d9bbcb35b64365387811, found geometry: MULTIPOLYGON that should be MultiPolygon, 832 times, example id: 1. GPKG: unrecognized user_version=0x00000000 (0) on '/mnt/volumes/statics/assets_data/20241119110606skdh8uub/result (2).gpkg'. Request: 7eac5ac3-3da4-4bb4-9805-e6e88fab7e20"
Additional details: used the two demo-instances from geosolutions.
The text was updated successfully, but these errors were encountered:
ffischer1984
changed the title
export dataset as GeoPackage has case-sensitive Geometry-Types which can't be read from the GeoNode
From the GeoNode exported datasets as GeoPackage has case-sensitive Geometry-Types which can't be read from the GeoNode (e.g MultiPolygon instead of MULTIPOLYGON)
Nov 19, 2024
Expected Behavior
When I'm exporting a Dataset in the GeoPackage-Format I'll expect that I can import the exact same GeoPackage-File into a GeoNode-Instance, again.
Actual Behavior
When I'm trying to import an exported GeoPackage-File from a geonode-instance I'll get this error-message:
Steps to Reproduce the Problem
lds-nz-primary-parcels-GPKG.zip
Specifications
The text was updated successfully, but these errors were encountered: