[gdal-dev] SQL script for creating a test GeoPackage

[Pepijn Van Eeckhoudt]

Jukka,

What I have is in the tool I wrote <https://bitbucket.org/luciad/libgpkg> ;) Not easy to copy/paste the SQL though.

Table definitions, required data and validation logic are in gpkg_db.c <https://bitbucket.org/luciad/libgpkg/src/20586fffd8e7ce1af4425d03e99707a5cf6ecdf2/gpkg/gpkg_db.c>. That code gets get called by the Init- and CheckSpatialMetaData SQL functions.

The other test SQL code I have is in the test suite. See addgeometrycolumn_spec.rb <https://bitbucket.org/luciad/libgpkg/src/20586fffd8e7ce1af4425d03e99707a5cf6ecdf2/test/addgeometrycolumn_spec.rb?at=default> for an example.

I don’t have an exhaustive test database generation script I’m afraid. The code Even pointed to is the closest thing to that that I’m aware of.

Pepijn

> On 23 Apr 2015, at 18:54, Jukka Rahkonen <jukka.rahkonen at maanmittauslaitos.fi> wrote:
> 
> Hi,
> 
> Inspired by this Spatialite forum thread
> https://groups.google.com/d/msg/spatialite-users/rBKeuXLpQv8/THStsQdQXI0J I
> started to write a SQL script that creates a GeoPackage database with all
> the metadata tables, triggers etc. and also data tables for every possible
> geometry type, each with one column for every possible data type, populated
> with some data that suits the type. 
> 
> However, I started to think that this is so obvious that someone must have
> done that already and that could save me a few hours. Even, Pepijn, where do
> you have your SQL? This Python in autotest directory probably has it all
> http://trac.osgeo.org/gdal/browser/trunk/autotest/ogr/ogr_gpkg.py.
> 
> The ultimate GeoPackage experts could then inspect the resulting GPKG
> database byte by byte and once it is perfect it could be shared to everybody
> and used in the conformance tests.
> 
> If I copy and paste right the columns will be:
> 
> BOOLEAN
> TINYINT
> SMALLINT
> MEDIUMINT
> INTEGER
> INT
> FLOAT
> DOUBLE
> TEXT
> BLOB
> GEOMETRY
> DATE
> DATETIME
> 
> And the basic geometry types:
> GEOMETRY
> POINT
> LINESTRING
> POLYGON
> MULTIPOLYGON
> MULTILINESTRING
> MULTIPOLYGON
> GEOMETRYCOLLECTION
> 
> And the extented geometry types:
> CIRCULARSTRING
> COMPOUNDCURVE
> CURVEPOLYGON
> MULTICURVE
> MULTISURFACE
> CURVE
> SURFACE
> 
> I have no idea about how I could insert contents to these but I think they
> should be put into their own database anyways.
> 
> -Jukka Rahkonen-
> 
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20150423/f828f5a0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4151 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20150423/f828f5a0/attachment.bin>