Yes VRT is a good point,
but it behaves like another datasource, so geomatic guys will know it, but
common user won't.
I think having a transparent provider, detecting, reading and writing WKT
could not be a solution.
Real life example:
- an external enterprise has developped a whole Access
Yes VRT is a good point,
but it behaves like another datasource, so geomatic guys will know it, but
common user won't.
I think having a transparent provider, detecting, reading and writing WKT
could be a solution.
Real life example:
- an external enterprise has developped a whole Access DB
About Spatial indexes, why not creating them on the fly in memory?
The more I think of it, the more I like the idea. Am I alone?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/storing-and-reading-WKT-geom-in-non-spatial-Datasource-tp5078296p5078411.html
Sent from the
About Spatial indexes, why not creating them on the fly in memory?
If you have large dynamic tables you could instead have a datamodel where
min_x, min_y, max_x max_y indexed columns are added along side the WKT/WKB in
the table. Then the QGIS provider could do bbox queries to quickly return
Hi,
Jeremy Palmer-2 wrote
Question: if you can't use ODBC because of security problems (?) then how
are you going to read the MS Access data into QGIS?
First, I will try to convince my sys admin ;-), and second, I will keep on
looking if funding direct gdal access / xlsx is expensive. That
Hi all,
a good question has been raised on Stackexchange [0]
How do I import WKT text data back into QGIS, and how useful could Base or
Access be in storing the data using WKT rather than spatially enabling it
within a proper GIS database, like Spatialite?
The good point beyond that, is that
