I've experienced the same issue and will provide the fix shortly.
Added a ticket for the record: http://trac.osgeo.org/gdal/ticket/5474
Tamas
2014-05-15 12:45 GMT+02:00 Niels Kjøller Hansen :
> Hello all
>
> I have been running a python script daily, which takes a table from a
> MSSQL database,
Le jeudi 15 mai 2014 14:01:58, Niels Kjøller Hansen a écrit :
> Hi Even,
>
> Thank you for responding so fast. I am not sure, however, how to use
> ogr2ogr and ogrinfo to further diagnose my problem.
Well, "ogrinfo the_syntax_to_open_a_mssql_db -al" and you'll see if there are
geometries in it,
Hi Even,
Thank you for responding so fast. I am not sure, however, how to use
ogr2ogr and ogrinfo to further diagnose my problem.
I have tried stepping through batch file, where the Python script is a part..
Ogr2ogr loads the file into dbo.table_name as it should (although with
wrong character s
Niels,
you could use ogr2ogr and ogrinfo to check where the issue appears in your
processing.
Even
> Hello all
>
> I have been running a python script daily, which takes a table from a
> MSSQL database, identifies which fields are strings, and does some
> character set fixing (utf8 to latin1)
>
Hello all
I have been running a python script daily, which takes a table from a
MSSQL database, identifies which fields are strings, and does some
character set fixing (utf8 to latin1)
The trouble is, that after an upgrade to GDAL/OGR 1.11, the table ends
up with an empty geometry column. When I
