ype for example. Add the -nlt POINT option on the ogr2ogr
command line for that. The table will be registered as begin a POINT table,
but no feature will have a geometry. Works with both 1.6.0 and 1.7.0
So, all in all, I think OGR 1.7 should work rather well when dealing with non
spatial sqlite dat
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
On 19/01/10 01:23, Frank Warmerdam wrote:
Roald,
Would you mind filing a ticket on this? I think the CopyLayer()
method ought
to use transactions in a manner similar to ogr2ogr.
Best regards,
Hi Frank,
Done: http://trac.osgeo.org/gdal/ticket/3335
Thanks, Roald
___
Transaction()
... insert features
lyr.CommitTransaction()
Best regards,
Even
Le Monday 18 January 2010 06:32:47 Roald de Wit, vous avez écrit :
Hi list,
Whilst trying to mimic ogr2ogr functionality in Python, I stumbled upon
an issue with writing to SQLite: it works, but it's pain
Hi list,
Whilst trying to mimic ogr2ogr functionality in Python, I stumbled upon
an issue with writing to SQLite: it works, but it's painfully slow
(minutes instead of seconds).
The link below points to an example that can be used for reproducing the
behaviour:
http://rdewit.pastebin.com/f7
