id summary reporter owner description type status priority milestone component version severity resolution keywords cc 6447 "ogr2ogr does not find table when using ""§"", ""ß"", ""ö"", ""ä"" or ""ü"" characters in the qualified identifier" hansw warmerdam "Hello, I'm using GDAL 2.1.0beta1, (released 2016/04/01) under Windows 7 x64. [http://download.gisinternals.com/sdk/downloads/release-1800-x64-gdal-mapserver.zip Source][[BR]][[BR]] I'm exporting geodata from from a Spatialite table to a Schapfile using the command line. It usually works fine except when there is a ""§"", ""ß"", ""ö"", ""ä"" or ""ü"" in the table name.[[BR]] I created a test Spatialite (sqlite) DB.[[BR]] As the attached file upload size is under 1MB I uploaded the file to: ​[http://www.file-upload.net/download-11474575/importTest.sqlite.html] [[BR]] To see the table name error use this command line. {{{ ogr2ogr.exe -f ""ESRI Shapefile"" ""C:\exportTest.shp"" ""C:\importTest.sqlite"" -lco ""ENCODING=ISO-8859-1"" -lco ""SPATIAL_INDEX=YES"" -sql ""SELECT \""straßenExport\"".\""the_geom\"", \""straßenExport\"".\""id\"" AS \""ident\"" FROM \""straßenExport\"";"" -t_srs ""EPSG:4326"" }}} Gives following error: {{{ ERROR 1: In ExecuteSQL(): sqlite3_prepare(SELECT ""stra+âenExport"".""the_geom"", ""stra+âenExport"".""id"" AS ""ident"" FROM ""stra+âenExport"";): no such table: stra+âenExport }}} When using ""§"", ""ö"", ""ä"" or ""ü"" in the column name the export of this column does not work properly too. In my case the values of this attribute are overwritten with the original column name. (see picture attached to the ticket) [[BR]] To see the column error use this command line. {{{ ogr2ogr.exe -f ""ESRI Shapefile"" ""C:\exportTest.shp"" ""C:\importTest.sqlite"" -lco ""ENCODING=ISO-8859-1"" -lco ""SPATIAL_INDEX=YES"" -sql ""SELECT \""strassenExport\"".\""the_geom\"", \""strassenExport\"".\""idä\"" AS \""id\"" FROM \""strassenExport\"";"" -t_srs ""EPSG:4326"" }}} Gives following error: {{{ ERROR 1: In ExecuteSQL(): sqlite3_prepare(SELECT ""strassenExport"".""the_geom"", ""strassenExport"".""id+±"" AS ""id"" FROM ""strassenExport"";): no such column: strassenExport.id+± }}} [[BR]] They are valid ISO-8859-1 characters and not UTF-8 only. I don't understand why they create this issues. As I used qualified identifiers the use of an them in the table name should not be a problem. GDAL > 2.0.0 supports qualified identifiers. [[BR]] I have problems believing it is a windows command line encoding problem as I already used this characters in filenames and GDAL has no problem reading them. [[BR]] [[BR]] (Updated the ticket according to the discussion below)" defect closed normal default svn-trunk major fixed ogr2ogr ISO-8859-1 characters table qualified identifier