Closed Sameme closed 5 years ago
This is more like an issue with GeoODK app than this algorithm.
Could you try gdalinfo and the tile and attach the output here? Essentially, if it is readable by GDAL, any other application using GDAL driver should be able to read the file.
@saberraz thanks for the response.
This is not an issue with GeoODK but the file composition of the mbtiles. Even when we try to serve it as a WMTS it fails with the same error that it couldn't find the images
table. It works as a layer within QGIS but not across the multiple platforms where we have previously used GDAL generated mbtiles.
Would it be possible to attach an example file or add the gdalinfo
output from the file?
Here is what the gdalinfo return:
From GeoODK, it appears that they only support vector (???) mbtiles: https://github.com/GeoODK/collect#main-functionality (I guess by "line Layer tiles (MapBox)" they mean vector mbtile).
The XYZ tile generator is for raster mbtiles, which appears not to be supported in GeoODK. Please file a ticket in GeoODK feature request or use https://inputapp.io which is based on QGIS.
@saberraz GeoODK supports raster mbtiles because we have used these countless times. However, I have tried serving the mbtiles as WMTS file using portable base map server but it still fails with the same error.
mbtiles file generated with the tool doesn't work in GeoODK app. The reason is the absence of
images table
. See error screenshots below-- This is how the file composition look like
-- File composition of mbtiles from other sources that work looks like this
Any suggested solution to resolve this will be highly appreciated.
Thanks