<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Jukka,</div><div class=""><br class=""></div><div class="">What I have is in <a href="https://bitbucket.org/luciad/libgpkg" class="">the tool I wrote</a> ;) Not easy to copy/paste the SQL though.</div><div class=""><br class=""></div><div class="">Table definitions, required data and validation logic are in <a href="https://bitbucket.org/luciad/libgpkg/src/20586fffd8e7ce1af4425d03e99707a5cf6ecdf2/gpkg/gpkg_db.c" class="">gpkg_db.c</a>. That code gets get called by the Init- and CheckSpatialMetaData SQL functions.</div><div class=""><br class=""></div><div class="">The other test SQL code I have is in the test suite. See <a href="https://bitbucket.org/luciad/libgpkg/src/20586fffd8e7ce1af4425d03e99707a5cf6ecdf2/test/addgeometrycolumn_spec.rb?at=default" class="">addgeometrycolumn_spec.rb</a> for an example.</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">Pepijn</div><br class=""><div><blockquote type="cite" class=""><div class="">On 23 Apr 2015, at 18:54, Jukka Rahkonen <<a href="mailto:jukka.rahkonen@maanmittauslaitos.fi" class="">jukka.rahkonen@maanmittauslaitos.fi</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi,<br class=""><br class="">Inspired by this Spatialite forum thread<br class=""><a href="https://groups.google.com/d/msg/spatialite-users/rBKeuXLpQv8/THStsQdQXI0J" class="">https://groups.google.com/d/msg/spatialite-users/rBKeuXLpQv8/THStsQdQXI0J</a> I<br class="">started to write a SQL script that creates a GeoPackage database with all<br class="">the metadata tables, triggers etc. and also data tables for every possible<br class="">geometry type, each with one column for every possible data type, populated<br class="">with some data that suits the type. <br class=""><br class="">However, I started to think that this is so obvious that someone must have<br class="">done that already and that could save me a few hours. Even, Pepijn, where do<br class="">you have your SQL? This Python in autotest directory probably has it all<br class=""><a href="http://trac.osgeo.org/gdal/browser/trunk/autotest/ogr/ogr_gpkg.py" class="">http://trac.osgeo.org/gdal/browser/trunk/autotest/ogr/ogr_gpkg.py</a>.<br class=""><br class="">The ultimate GeoPackage experts could then inspect the resulting GPKG<br class="">database byte by byte and once it is perfect it could be shared to everybody<br class="">and used in the conformance tests.<br class=""><br class="">If I copy and paste right the columns will be:<br class=""><br class="">BOOLEAN<br class="">TINYINT<br class="">SMALLINT<br class="">MEDIUMINT<br class="">INTEGER<br class="">INT<br class="">FLOAT<br class="">DOUBLE<br class="">TEXT<br class="">BLOB<br class="">GEOMETRY<br class="">DATE<br class="">DATETIME<br class=""><br class="">And the basic geometry types:<br class="">GEOMETRY<br class="">POINT<br class="">LINESTRING<br class="">POLYGON<br class="">MULTIPOLYGON<br class="">MULTILINESTRING<br class="">MULTIPOLYGON<br class="">GEOMETRYCOLLECTION<br class=""><br class="">And the extented geometry types:<br class="">CIRCULARSTRING<br class="">COMPOUNDCURVE<br class="">CURVEPOLYGON<br class="">MULTICURVE<br class="">MULTISURFACE<br class="">CURVE<br class="">SURFACE<br class=""><br class="">I have no idea about how I could insert contents to these but I think they<br class="">should be put into their own database anyways.<br class=""><br class="">-Jukka Rahkonen-<br class=""><br class="">_______________________________________________<br class="">gdal-dev mailing list<br class=""><a href="mailto:gdal-dev@lists.osgeo.org" class="">gdal-dev@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/gdal-dev<br class=""></div></blockquote></div><br class=""></body></html>