[gdal-dev] GPKG raster creation : error with too small resolution

[Philippe Ghesquiere]

I agree with the standard limit of  the InspireCRS84Quad grid.
That's why I was wondering if we could deal with this weird image like :
gdal_translate -of GPKG -co TILING_SCHEME=InspireCRS84Quad -co
ZOOM_LEVEL_STRATEGY=UPPER *-co MAX_ZOOM_LEVEL=17* 1mm.tif 1mm.gpkg

In this particular case, the GPKG will stop at ZoomLevel=17
Philippe

On Thu, Jan 18, 2024 at 3:36 PM Rahkonen Jukka <
jukka.rahkonen at maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> I am not sure how standard the level 25 is for the InspireCRS84Quad, the
> INSPIRE technical guidance stops at 17. But I believe that you know your
> own use case and have considered also that EPSG:3857 at 1 mm resolution is
> good for you.
>
> The number of tiles at level 25 is 2^50= 1.1259E+15. TileCol and TileRow
> would get rather large numbers but I suppose that it is not an issue.
>
>
>
> -Jukka Rahkonen-
>
>
>
> *Lähettäjä:* Philippe Ghesquiere <philippe.ghesquiere at airbus.com>
> *Lähetetty:* torstai 18. tammikuuta 2024 16.06
> *Vastaanottaja:* Rahkonen Jukka <jukka.rahkonen at maanmittauslaitos.fi>
> *Kopio:* gdal-dev <gdal-dev at lists.osgeo.org>
> *Aihe:* Re: [gdal-dev] GPKG raster creation : error with too small
> resolution
>
>
>
> Hi Jukka,
>
>
>
> I have no choice but to use the standard InspireCRS84Quad tiling grid.
>
>
>
> Thanks for the "-a_ullr fix"
>
>
>
> Philippe
>
>
>
>
>
> On Thu, Jan 18, 2024 at 2:42 PM Rahkonen Jukka <
> jukka.rahkonen at maanmittauslaitos.fi> wrote:
>
> Hi,
>
>
>
> Can you imagine using a custom tiling schema instead of the world-wide
> InspireCRS84Quad? These commands work
>
> gdal_create -of GTiff -co COMPRESS=DEFLATE -outsize 2000 2000 -burn 255
> -burn 0 -burn 0 -bands 3 -ot Byte -a_srs epsg:32631 -a_ullr 1000000 1000002
> 1000002 1000000 1mm.tif
>
> gdal_translate -of GPKG  1mm.tif 1mm.gpkg
>
> Notice the fixed ullr for making the image north-up.
>
>
>
> -Jukka Rahkonen-
>
>
>
> gdal_translate -of GPKG  1mm.tif 1mm.gpkg
>
> Input file size is 2000, 2000
>
> 0ERROR 6: Only north-up non rotated geotransform supported
>
> ..ERROR 1: Raster table 1mm not correctly initialized due to missing call
> to SetGeoTransform()
>
>
>
> *Lähettäjä:* gdal-dev <gdal-dev-bounces at lists.osgeo.org> *Puolesta *Philippe
> Ghesquiere via gdal-dev
> *Lähetetty:* torstai 18. tammikuuta 2024 15.22
> *Vastaanottaja:* gdal-dev <gdal-dev at lists.osgeo.org>
> *Aihe:* [gdal-dev] GPKG raster creation : error with too small resolution
>
>
>
>
>
> Dear all,
>
> I just had an error while converting an image to GPKG. This image has a
> very small resolution and gdal_translate pops up an error message.
>
> *Test image :*
> gdal_create -of GTiff -co COMPRESS=DEFLATE -outsize 2000 2000 -burn 255
> -burn 0 -burn 0 -bands 3 -ot Byte -a_srs epsg:32631 -a_ullr 1000000 1000000
> 1000002 1000002 1mm.tif
>
> *Conversion to GPKG :*
> gdal_translate -of GPKG -co TILING_SCHEME=InspireCRS84Quad -co
> ZOOM_LEVEL_STRATEGY=UPPER 1mm.tif 1mm.gpkg
> Input file size is 2000, 2000
> ERROR 1: Could not find an appropriate zoom level
>
> *Analysis*
>
> The error is due to  ogrgeopackagedatasource.cpp
> <https://github.com/OSGeo/gdal/blob/master/ogr/ogrsf_frmts/gpkg/ogrgeopackagedatasource.cpp#L3169> (line
> 3169), and it does make sense : the zoom level is too high (Z>25).
>
>
>
> However, wouldn't it be possible to modify gdal_translate behavior ?
>
> For example, we could :
>
>    - let GDAL compute the appropriate zoom level : -co
>    ZOOM_LEVEL_STRATEGY=AUTO/LOWER/UPPER,
>    - optionally specify a maximum zoom level : -co MAX_ZOOM_LEVEL=18
>
> What do you think ?
>
>
>
> Philippe
>
>
>
> The information in this e-mail is confidential. The contents may not be
> disclosed or used by anyone other than the addressee. Access to this e-mail
> by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus immediately
> and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or completeness
> of this e-mail as it has been sent over public networks. If you have any
> concerns over the content of this message or its Accuracy or Integrity,
> please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated virus
> scanning software but you should take whatever measures you deem to be
> appropriate to ensure that this message and any attachments are virus free.
>
> The information in this e-mail is confidential. The contents may not be
> disclosed or used by anyone other than the addressee. Access to this e-mail
> by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus immediately
> and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or completeness
> of this e-mail as it has been sent over public networks. If you have any
> concerns over the content of this message or its Accuracy or Integrity,
> please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated virus
> scanning software but you should take whatever measures you deem to be
> appropriate to ensure that this message and any attachments are virus free.
>
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240118/570851ec/attachment-0001.htm>