[gdal-dev] GPKG application_id

[Even Rouault]

Hi Paul,

> As we found when developing gpkg, setting the PRAGMA application_id can be
> tricky given the general state of installed sqlite libraries on a randomly
> chosen system: generally, the libraries are old enough to not support that
> pragma!

For reference: old sqlite lib can be a problem for another reason. When 
implementing spatial index, I discovered that my antique sqlite 3.6.22-1 
(ubuntu 10.04) has issues with some of the required triggers, in some 
conditions (update situations with null geometries)

> 
> We ended up hacking around it by directly editing the bytes in the file
> header.
> 
> Others are less likely. I’ve learned that GeoServer is emitted GPKG files
> without the application_id set.

Hum, do they plan fixing that at some point ? Couldn't they do the same trick 
we do (direct editing) ?

> 
> Right now, OGR GPKG driver is strict: fail on wrong application_id. I’d
> like to make it more lenient: warn on wrong application_id. We can always
> fail later if required tables are missing, etc.
> 
> Is it OK to make this change in trunk? In 1.12 or 1.11 branch?

trunk (2.0dev) and 1.11 branch are fine (there's no 1.12)

Best regards,

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com