On Fri, 11 May 2018, Rahkonen Jukka (MML) wrote:
I need to run a certain job that requires open option
"-oo encoding="ISO_8859-1" and while it runs fine on Windows with the
OSGeo4W installation with version GDAL 2.2.4, released 2018/03/19 it
leads to loads of warnings "Warning 1: Value of field 'name_field'
is not a valid UTF-8 string." with the gisinternals installation
GDAL 2.3.0dev, released 2017/99/99.
The shapefiles which I have are really using ISO_8859-1 and
gisinternals version handles them OK without using the open option,
except one. The problematic one does not have the LDID "87 / 0x57"
flag in the .dbf part and therefore it is interpreted as UTF-8 if I
do not use the open option. If I use the open option the
gisinternals version prints the warnings about all the
Shape: Treating as encoding 'ISO_8859-1'.
Shape: Cannot recode from 'ISO_8859-1'. Disabling recoding
Is there anything else that an end user could do for finding out why
the gisinternals build fails with recoding? BTW is it documented
somewhere which are the correct values for different encodings?
For example in my case I had to use exactly "-oo encoding="ISO_8859-1".
... with an odd number of quotes ? Wierd.
--
Andrew C. Aitchison Cambridge, UK
[email protected]
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
