[Geopackage] Test data for /opt/features/geometry_encoding/data/core_types_all_types_test_data ?

Pepijn Van Eeckhoudt pepijn.vaneeckhoudt at luciad.com
Mon Jan 13 10:53:12 EST 2014

Paul Daisey is best placed to comment on the ATS, but here's my take.

There are two ways to look at this test. Either it's intended to verify 
any existing file for validity or it is intended to test an support 
library for correctness.
If it's a file test you need a verification library that queries all the 
geometry blobs in a geopackage and checks them for wellformedness.
If it's a library test then you don't even need a file; all you need is 
a memory database and a script that excercises the geometry io functions 
of said library. Something along the lines of 


On 10-01-14 23:36, Brad Hards wrote:
> The subject test case requires an assortment of srs_ids, coordinate values,
> with and without z and m and big and little encoding.
> As I see it, that requires a test database (or databases). Ideally that
> database would be generated in a way that anyone could inspect and update.
> I'm planning to write a generator for that database (perhaps in python to make
> it independent of my C implementation), unless someone has already done the
> work and published it.
> Brad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geopackage/attachments/20140113/9df8c414/attachment.html>

More information about the Geopackage mailing list