-
Notifications
You must be signed in to change notification settings - Fork 1k
GeoPackage database import error; possible a bug? #1706
Description
I’m dealing with a small test App to load and display a GeoPackage raster layer.
The source .gpkg file archive is on getExternalFilesDir(null) osmdroid/files path so must not be a matter of permission, but anyway I have evidences that the folder is writable and the source file is loaded and parsed.
The App works onboard an old Lg G2, Android 7 Api 25. The map shows up in the window.
On a newer Xiaomi Poco F1, Android 10 Api 29 the App fires up the below error
W/System.err: mil.nga.geopackage.GeoPackageException: Invalid GeoPackage database file
W/System.err: Caused by: mil.nga.geopackage.GeoPackageException: Failed to insert GeoPackage metadata. Name: cesaneMTB, External Path: null
Now I cannot figure out what’s on different Api … The source file is the same so why here it’s a valid gpkg and there it’s not … really confused and any debug strategy is landing to nowhere.
Gdal says
gdalinfo cesaneMTB.gpkg -oo TABLE=cesaneMTB
Files: cesaneMTB.gpkg
LENGTHUNIT["metre",1]]],
PRIMEM["Greenwich",0,
ANGLEUNIT["degree",0.0174532925199433]],
CS[ellipsoidal,2],
AXIS["geodetic latitude (Lat)",north,
ORDER[1],
ANGLEUNIT["degree",0.0174532925199433]],
AXIS["geodetic longitude (Lon)",east,
ORDER[2],
ANGLEUNIT["degree",0.0174532925199433]],
ID["EPSG",4326]]
Data axis to CRS axis mapping: 2,1
Origin = (12.668898420000000,43.749655154000003)
Pixel Size = (0.000009685365377,-0.000009685365303)
Metadata:
IDENTIFIER=cesaneMTB
ZOOM_LEVEL=13
Image Structure Metadata:
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left ( 12.6688984, 43.7496552) ( 12d40' 8.03"E, 43d44'58.76"N)
Lower Left ( 12.6688984, 43.6603851) ( 12d40' 8.03"E, 43d39'37.39"N)
Upper Right ( 12.8348378, 43.7496552) ( 12d50' 5.42"E, 43d44'58.76"N)
Lower Right ( 12.8348378, 43.6603851) ( 12d50' 5.42"E, 43d39'37.39"N)
Center ( 12.7518681, 43.7050201) ( 12d45' 6.73"E, 43d42'18.07"N)
etc. etc….
Any hint?
TyL. Paolo