KML export is generating decimal separators depending on system locale #15452

qgib · 2012-07-27T11:40:24Z

Author Name: Rodrigo Hjort (Rodrigo Hjort)
Original Redmine Issue: 6110
Affected QGIS version: master
Redmine category:vectors

I'm using Quantum GIS on Linux with locales set to pt-BR (Brazilian Portuguese).

When I export to KML, it produces coordinates using "," decimal separator (according to pt-BR regionalization rules):

@-51,09189516,0,01566702 -51,091517879999998,0,01681002 -51,090230267830101,0,01554286575332 -51,089511609343091,0,014835625502677 -51,089524844693898,0,014785154452175 -51,089621934159901,0,014414918150888 -51,089695920000004,0,01413396 -51,090616079999997,0,01472103 -51,091445940477001,0,015334783410788 -51,09189516,0,01566702@

When I call Quantum GIS setting locales to en-US (i.e., by issuing "LC_ALL=C qgis"), proper values are set on KML file (by using "." and not "," as decimal separators):

@-51.09189516,0.01566702 -51.091517879999998,0.01681002 -51.090230267830101,0.01554286575332 -51.089511609343091,0.014835625502677 -51.089524844693898,0.014785154452175 -51.089621934159901,0.014414918150888 -51.089695919999997,0.01413396 -51.090616079999997,0.01472103 -51.091445940477001,0.015334783410789 -51.09189516,0.01566702@

In order to generate KML files, current system locale should be ignored.

test_polygons.zip (François-Xavier Thomas)

Related issue(s): #17120 (relates)
Redmine related issue(s): 8332

qgib · 2012-07-27T12:07:18Z

Author Name: Giovanni Manghi (@gioman)

Tickets are tagged as blockers only if are regressions. Is this a regression since 1.7.4 (are you using 1.8, right?)?

Did you tested make the conversion using the ogr2ogr cli tool? I'm not sure QGIS uses it to do this particular conversion, but if the issue surface also with ogr2ogr it may be not a qgis issue.

category_id was configured as Vectors
status_id was changed from Open to Feedback
priority_id was changed from Severe/Regression to Normal

qgib · 2012-07-27T12:22:14Z

Author Name: Rodrigo Hjort (Rodrigo Hjort)

Giovanni Manghi wrote:

Tickets are tagged as blockers only if are regressions. Is this a regression since 1.7.4 (are you using 1.8, right?)?

I don't know. Yes, I'm on 1.8.0.

Did you tested make the conversion using the ogr2ogr cli tool? I'm not sure QGIS uses it to do this particular conversion, but if the issue surface also with ogr2ogr it may be not a qgis issue.

I've just tested ogr2ogr as you suggested. It generates proper KML files regardless the locales I set. All instructions below give binarily the same KML files:

@ogr2ogr -f KML censo-ap1.kml 16SEE250GC_SIR.shp
LC_ALL=C ogr2ogr -f KML censo-ap2.kml 16SEE250GC_SIR.shp
LC_ALL=pt_BR.UTF-8 ogr2ogr -f KML censo-ap3.kml 16SEE250GC_SIR.shp@

qgib · 2012-07-27T23:38:49Z

Author Name: Giovanni Manghi (@gioman)

then is a qgis issue.

I've just tested ogr2ogr as you suggested. It generates proper KML files regardless the locales I set. All instructions below give binarily the same KML files:

@ogr2ogr -f KML censo-ap1.kml 16SEE250GC_SIR.shp
LC_ALL=C ogr2ogr -f KML censo-ap2.kml 16SEE250GC_SIR.shp
LC_ALL=pt_BR.UTF-8 ogr2ogr -f KML censo-ap3.kml 16SEE250GC_SIR.shp@

fixed_version_id was configured as Version 2.0.0
status_id was changed from Feedback to Open

qgib · 2012-07-28T00:51:21Z

Author Name: Jürgen Fischer (@jef-n)

Rodrigo Hjort wrote:

I don't know. Yes, I'm on 1.8.0.

Not reproducable here. What's your platform and GDAL version?

qgib · 2012-07-28T01:52:20Z

Author Name: Even Rouault (@rouault)

LC_ALL=C ogr2ogr -f KML censo-ap2.kml 16SEE250GC_SIR.shp
LC_ALL=pt_BR.UTF-8 ogr2ogr -f KML censo-ap3.kml 16SEE250GC_SIR.shp@

Setting LC_ALL isn't sufficient, as by default GDAL utilities will not call setlocale(), so it will not be taken into account.

So you should try : "ogr2ogr -f KML censo-ap3.kml 16SEE250GC_SIR.shp --locale pt_BR.UTF-8"

With recent GDAL versions (1.9 at least, perhaps older too), the code that exports the coordinates for KML, GML, WKT will replace the comma by decimal point.

Note: there might be still issues with decimal points and non-C locale in other parts of GDAL/OGR however. Export of real values in DBF for example is known to be broken with non-C locale ( http://trac.osgeo.org/gdal/ticket/4713 )

Note 2: I've just discovered that a bug in in proj 4.7 hides some locale related problems, because it installs the C locale temporarily, but fails to restore the original locale properly. This has been fixed in proj 4.8 that restores properly the original locale, and now some locale related problems surface again

qgib · 2012-07-30T23:45:48Z

Author Name: Giovanni Manghi (@gioman)

status_id was changed from Open to Feedback

qgib · 2013-07-13T01:39:19Z

Author Name: Jürgen Fischer (@jef-n)

closed for the lack of feedback.

resolution was changed from to worksforme
status_id was changed from Feedback to Closed

qgib · 2014-05-28T00:29:10Z

Author Name: François-Xavier Thomas (François-Xavier Thomas)

I'm facing the exact same issue with QGIS 2.2 under Ubuntu 12.04. @Locale@ output on my system :

@lang=fr_FR.UTF-8
LANGUAGE=
LC_CTYPE=fr_FR.UTF-8
LC_NUMERIC="fr_FR.UTF-8"
LC_TIME="fr_FR.UTF-8"
LC_COLLATE="fr_FR.UTF-8"
LC_MONETARY="fr_FR.UTF-8"
LC_MESSAGES="fr_FR.UTF-8"
LC_PAPER="fr_FR.UTF-8"
LC_NAME="fr_FR.UTF-8"
LC_ADDRESS="fr_FR.UTF-8"
LC_TELEPHONE="fr_FR.UTF-8"
LC_MEASUREMENT="fr_FR.UTF-8"
LC_IDENTIFICATION="fr_FR.UTF-8"
LC_ALL=
@

Attached is a sample shapefile created from QGIS under the system locale, and its KML conversion from :

QGIS using the system locale
QGIS started using the @LC_NUMERIC="C" /usr/bin/qgis@ command
The @ogr2ogr@ command from GDAL

Both GDAL and QGIS under the C locale output a valid KML file, but QGIS using the system locale does not and uses comma as decimal separators.

Additionally, for some reason which might be related, QGIS is unable to display the shapefile (not the KML file!) if opened under the system locale, but displays it perfectly well under the C locale. As far as I can tell, even though it was created under a french locale, the shapefile is valid, i.e. GDAL can open it under any locale.

(It's the first time I'm around here, so forgive me if I shouldn't have reopened the ticket but created a new one instead)

7289 was configured as test_polygons.zip
status_id was changed from Closed to Reopened
fixed_version_id was changed from Version 2.0.0 to Version 2.2

test_polygons.zip (François-Xavier Thomas)

qgib · 2014-06-28T05:36:35Z

Author Name: Jürgen Fischer (@jef-n)

fixed_version_id was changed from Version 2.2 to Future Release - Lower Priority

qgib · 2014-09-20T11:07:35Z

Author Name: Andrey Isakov (@Andrey-VI)

Same issue for me under Debian testing.
QGIS 2.4.0-Chugiak
Compiled against GDAL/OGR 1.10.1 Running against GDAL/OGR 1.10.1

andrey@crt-s1:~$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=ru_RU.utf8
LC_TIME=ru_RU.utf8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=ru_RU.utf8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=ru_RU.utf8
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT=ru_RU.utf8
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Related issue #17120

qgib · 2016-02-25T04:01:57Z

Author Name: Jürgen Fischer (@jef-n)

Andrey Isakov wrote:

Same issue for me under Debian testing.
QGIS 2.4.0-Chugiak
Compiled against GDAL/OGR 1.10.1 Running against GDAL/OGR 1.10.1
[...]

Related issue #17120

odd, still doesn't happen for me. fr_Fr, lv_LV, de_DE - all fine on unstable using GDAL/OGR 1.11.3.

status_id was changed from Reopened to Feedback

qgib · 2016-04-09T09:41:26Z

Author Name: Giovanni Manghi (@gioman)

odd, still doesn't happen for me. fr_Fr, lv_LV, de_DE - all fine on unstable using GDAL/OGR 1.11.3.

closing for lack of feedback. Please reopen if necessary.

status_id was changed from Feedback to Closed

Fix qgis#15452

qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Vectors Related to general vector layer handling (not specific data formats) labels May 24, 2019

qgib added this to the Future Release - Lower Priority milestone May 24, 2019

qgib closed this as completed May 24, 2019

qgib mentioned this issue May 25, 2019

QGIS uses comma as decimal separator for shapefile attribute data #17120

Closed

JamesShaeffer pushed a commit to JamesShaeffer/QGIS that referenced this issue Nov 20, 2019

Hide invalid constraints label when it's unused

ecec1f0

Fix qgis#15452

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

KML export is generating decimal separators depending on system locale #15452

KML export is generating decimal separators depending on system locale #15452

qgib commented Jul 27, 2012 •

edited

Loading

qgib commented Jul 27, 2012

qgib commented Jul 27, 2012

qgib commented Jul 27, 2012

qgib commented Jul 28, 2012

qgib commented Jul 28, 2012

qgib commented Jul 30, 2012

qgib commented Jul 13, 2013

qgib commented May 28, 2014

qgib commented Jun 28, 2014

qgib commented Sep 20, 2014 •

edited

Loading

qgib commented Feb 25, 2016 •

edited

Loading

qgib commented Apr 9, 2016

KML export is generating decimal separators depending on system locale #15452

KML export is generating decimal separators depending on system locale #15452

Comments

qgib commented Jul 27, 2012 • edited Loading

qgib commented Jul 27, 2012

qgib commented Jul 27, 2012

qgib commented Jul 27, 2012

qgib commented Jul 28, 2012

qgib commented Jul 28, 2012

qgib commented Jul 30, 2012

qgib commented Jul 13, 2013

qgib commented May 28, 2014

qgib commented Jun 28, 2014

qgib commented Sep 20, 2014 • edited Loading

qgib commented Feb 25, 2016 • edited Loading

qgib commented Apr 9, 2016

qgib commented Jul 27, 2012 •

edited

Loading

qgib commented Sep 20, 2014 •

edited

Loading

qgib commented Feb 25, 2016 •

edited

Loading