Thanks for reporting the typo. I've just corrected the wiki page as well as
the NEWS file in subversion which is the master for the wiki page.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Hi Even,
Thanks for the verbose response. Option 2 (SQLITE_LIST_ALL_TABLES=YES)
is the easiest and best one for my use case : importing data from both
spatial and non-spatial sources into one SQLite file).
Realising I had not read the release notes [1] properly and having read
them again, I
Roald,
Several points :
* I've tried with 1.6 branch, and even if it can list the tasmania_cities
layer, it doesn't seem to be able to read the features in it, as a dumb
geometry column name '(null)' was inserted by ogr2ogr into the
geometry_columns table. Thus when reading the definition of t
Hi list,
I have the following issue: OGR 1.7.x cannot read the SQLite files it
creates from a source *without geometries*.
I used the following GDAL:
- from http://vbkto.dyndns.org/sdk/
(release-1310-gdal-1-7-mapserver-5-6.zip, based on r9799, r18849)
- on a WinXP machine
- having no other G