New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate Requirement #69 #234

jyutzler opened this Issue Aug 2, 2016 · 3 comments


None yet
3 participants

jyutzler commented Aug 2, 2016

The SWG determined that it is not possible to comply with this requirement and that it needs to be deprecated.

@jyutzler jyutzler added this to the post-1.1 milestone Aug 2, 2016

@jyutzler jyutzler referenced this issue Aug 2, 2016


Add some ATS tests #193

3 of 4 tasks complete

This comment has been minimized.


cclark1984 commented Aug 23, 2016

It is difficult, if not impossible, to comply with Req 69 "SQL functions that operate on GeoPackageBinary geometries as specified in other extensions SHALL operate correctly on the non-linear geometries specified in this extension." because the functions could have been loaded via an extension such SpatiaLite which cannot be changed, and does not support the non-linear geometries. The removal of this requirement will allow for interoperable storage and retrieval of the geometries, while not requiring but allowing existing functions to work with the geometries.


This comment has been minimized.


pepijnve commented Aug 23, 2016

Dropping that requirement may cause issues when using non-linear geometry in combination with the spatial index extension since that requires triggers that call ST_Min/MaxX/Y.
In other words, if you drop that requirement then interoperable reading will work; interoperable writing (insert/update of a non-linear geometry into a geopackage created by someone else) may not.

jyutzler added a commit to jyutzler/geopackage that referenced this issue Aug 23, 2016

@jyutzler jyutzler referenced this issue Aug 23, 2016


Extensions #239


This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment