Opened 8 years ago
Last modified 8 years ago
#6339 closed defect
Overview Creation fails in geopackages created using Tiling Scheme — at Version 3
Reported by: | Augustus | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | 2.0.3 |
Component: | default | Version: | 2.0.1 |
Severity: | normal | Keywords: | raster geopackage gdaladdo |
Cc: |
Description (last modified by )
The following command will cause a crash for large tiled images. With small tiled images the overviews creation is done fine
gdal_translate -of GPKG byteError.tif gpkg.gpkg -co TILING_SCHEME=GoogleMapsCompatible gdaladdo gpkg.gpkg 2 4 8 16 32
You can reproduce this issue by re-sampling the byte.tif to 9999 rows and columns and then manipulating the resultant tif file using the above commands https://github.com/OSGeo/gdal/blob/trunk/autotest/gdrivers/data/byte.tif I have attached the intermediate files.
Update: Workflow for reproducing the issue
Change History (5)
by , 8 years ago
by , 8 years ago
Attachment: | byte4800.tif added |
---|
comment:1 by , 8 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:2 by , 8 years ago
Description: | modified (diff) |
---|
I was able to reproduce this issue with larger images. Steps to reproduce this issue
Data is Attached byte4800.tif
gdal_translate -outsize 9999 10118 byte4800.tif byteError.tif gdal_translate -of GPKG byteError.tif Test.gpkg -co TILING_SCHEME=GoogleMapsCompatible
Error
ERROR 1: sqlite3_exec(UPDATE partial_tiles SET zoom_level = -21, partial_flag = 0 WHERE zoom_level = 20 AND partial_flag != 0) failed: columns zoom_level, tile_ column, tile_row are not unique ERROR 1: sqlite3_exec(UPDATE partial_tiles SET zoom_level = -21, partial_flag = 0 WHERE zoom_level = 20 AND partial_flag != 0) failed: database disk image is ma lformed
comment:3 by , 8 years ago
Description: | modified (diff) |
---|---|
Resolution: | duplicate |
Status: | closed → reopened |
Note:
See TracTickets
for help on using tickets.
I guess this is the same as #6335 I cannot reproduce any issue after the fixes done in #6335 (instead of the error message you got in #6335, crash was also likely)