> > *The requirement for a single geometry column per table > > > > I just don't see a good reason to forbid that > > > > Possible mitigation: a) alter the standard. b) ignore the standard > > > > and patch the ogr implementation. > > I don't think the Geopackage OGC SWG would be keen to change that. I believe > I floated the idea around a few years ago, but they wanted GeoPackage core > to remain simple and adding multiple geometry columns goes against that.
Actually that might be just my past reading of the below blog post that Jeff Yutzler, the editor of the spec just reminded me about: http://geopackage.blogspot.com/2015/10/one-geometry-per-table.html The link to the modeling guidelines in this post is now dead. They are at: http://www.geopackage.org/guidance/modeling.html Even -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
