<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Josef,</p>
<p>From <a class="moz-txt-link-freetext" href="http://www.gdal.org/drv_geopackage.html">http://www.gdal.org/drv_geopackage.html</a><br>
</p>
<p>"The core GeoPackage specification does not currently support
non-spatial tables, but starting with GDAL 2.0, the driver allows
creating and reading such tables via the Aspatial Support
(gdal_aspatial) extension. Note: starting with GDAL 2.2, the
driver will also, by default, list non spatial tables that are not
registered through the gdal_aspatial extension."</p>
<p>So with newer GDAL versions it is possible to create and read
non-spatial tables.</p>
<p>Andreas<br>
</p>
<br>
<div class="moz-cite-prefix">On 13.03.2017 17:13, josef k wrote:<br>
</div>
<blockquote
cite="mid:CAFN_NvZMNGCyekU4LB3w2U3u8YEcdOzZfDSj_wnjBdbs+vZLvQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Here is just a reminder from a user/plugin maintainer,
please ignore if not relevant.<br>
<br>
If the spatialite data provider is to be removed then we will
have to update some plugins to reflect that which is ok, not a
big deal. But it is important that the current features of the
spatialite data provider are included into the OGR provider
before changing. <br>
<br>
E.g. we are using the spatalite data provider in plugins to
add non-spatial spatialite tables. I could not achieve this by
using the OGR provider (although it was a couple of years ago
I was looking into this and it may have changed by now). <br>
<br>
regards<br>
Josef<br>
<br>
</div>
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">On Mon, 13 Mar 2017
11:28:45 +1000, Nyall Dawson wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
I'm wondering what the future of the spatialite
provider should be. I<br>
find it odd that spatialite layers utilise the
dedicated spatialite<br>
provider, but geopackage layers use the OGR
provider.<br>
<br>
I think there's potential value in removing the
spatialite provider<br>
and always reading these layers via OGR.<br>
<br>
</blockquote>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</body>
</html>