[gdal-dev] GPKG and antimeridian
Bugbuster
philippe.ghesquiere at airbus.com
Tue Nov 24 07:53:59 PST 2020
Sorry my previous message is a bit screwed up (part of the message has been
lost)
1) gdalwarp using *"-co"* options yield to errors, even with -tr and -t_srs
options
PROMPT> gdalwarp -overwrite -of GPKG -co TILING_SCHEME=InspireCRS84Quad -co
ZOOM_LEVEL_STRATEGY=AUTO -tr 0.000056168363154 0.000056168363154 -t_srs
EPSG:4326 MyImageEast.tif MyImageWest.tif out.gpkg
Creating output file that is 1901P x 1277L.
ERROR 6: Could not find an appropriate zoom level of InspireCRS84Quad tiling
scheme that matches raster pixel size
ERROR 1: Raster table out not correctly initialized due to missing call to
SetGeoTransform()
PROMPT>
2) gdalwarp using *"-doo"* options
These options are ignored : I obtain exactly the same image with or without
them.
In this case, the GPKG image is not compliant to any tle scheme : it spans
[+170° ; +190°].
3) As you say, gdal_translate automatically does the "right thing". Which is
quite nice.
As I mentioned in my 1st message, I created my GPKG in two steps :
3.1) create a VRT
gdalbuildvrt MyImage.vrt MyImageEast.tif MyImageWest.tif
This image has no data in the intervalle [-179° ; +179°]
3.2) Translate it to GPKG
gdal_translate -of GPKG -co TILING_SCHEME=InspireCRS84Quad -co
ZOOM_LEVEL_STRATEGY=AUTO MyImage.vrt MyImage.gpkg
In this translation, GDAL creates non-existant tiles between [-179° ;
+179°], resulting in a huge image.
Does it sound all right to you ?
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
More information about the gdal-dev
mailing list