Encoding problems with Processing toolbox - Githubissues

qgib commented 8 years ago

Author Name: vedar sum (vedar sum) Original Redmine Issue: 14704 Affected QGIS version: 2.18.4 Redmine category:processing/qgis

new description

Some qgis algs create outputs where the attribute tables have encoding issues. Examples are buffer and dissolve. Maybe others are also affected (an example that works as expected in "voronoi polygons").

Sample data attached.

old description Hi,

I'm using QGIS 2.14.1 on Windows 10 through OSGeo4W setup.

I noticed that if I process a vector layer (i.e. UTF-8 encoded geojson) with QGIS algorithm (i.e. crop, Voronoi, etc) through Processing toolbox, result layer has attribute table with question marks instead expected characters. While if I run the same algorithm through QGIS menu, result layer is correctly encoded.

I noticed also that this affects GDAL/OGR algorithms, besides QGIS algorithms, while not SAGA algorithms.

For reference I open a question first here: http://gis.stackexchange.com/questions/190137/qgis-algoritms-have-encoding-problems

portugal_continental_3763_1.zip (Giovanni Manghi)

qgib commented 8 years ago

Author Name: Anita Graser (@anitagraser)

category_id was configured as Processing/QGIS

qgib commented 8 years ago

Author Name: Anita Graser (@anitagraser)

priority_id was changed from Normal to High

qgib commented 8 years ago

Author Name: Alexander Bruy (@alexbruy)

Canyou share sample dataset?

qgib commented 8 years ago

Author Name: Alexander Bruy (@alexbruy)

status_id was changed from Open to Feedback

qgib commented 8 years ago

Author Name: Giovanni Manghi (@gioman)

closing for lack of feedback, please reopen if necessary.

status_id was changed from Feedback to Closed
resolution was changed from to not reproducable

qgib commented 7 years ago

Author Name: Saber Razmjooei (@saberraz)

In my case, the problem was with path.

The bug is present in 2.18 and 2.14.

resolution was changed from not reproducable to
status_id was changed from Closed to Reopened
priority_id was changed from High to Severe/Regression

qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)

Saber Razmjooei wrote:

In my case, the problem was with path.

The bug is present in 2.18 and 2.14.

Tested on 2.18.4 on Windows special chars in paths seems to be not an issue for QGIS algs. They are an issue for GDAL/OGR ones (will file a different ticket).

Encoding problems in outputs do not seem to be a problem with GDAL/OGR algs or with all QGIS algs, but certainly a few QGIS algs are affected, like dissolve and buffer (and maybe others).

operating_system was changed from Windows to
version was changed from 2.14.1 to 2.18.4
os_version was changed from 10 to
10771 was configured as portugal_continental_3763_1.zip

portugal_continental_3763_1.zip (Giovanni Manghi)

qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)

fixed_version_id was changed from Version 2.14 to Version 2.18

qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)

crashes_corrupts_data was changed from 0 to 1

qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)

regression was configured as 1

qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)

priority_id was changed from Severe/Regression to High

qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)

easy_fix was configured as 0

qgib commented 7 years ago

Author Name: Alexander Bruy (@alexbruy)

Can't reproduce with latest 2.18 using attached sample data and native buffer and dissolve algorithms.

status_id was changed from Reopened to Feedback
description was changed from new description

Some qgis algs create outputs where the attribute tables have encoding issues. Examples are buffer and dissolve. Maybe others are also affected (an example that works as expected in "voronoi polygons").

Sample data attached.

old description Hi,

I'm using QGIS 2.14.1 on Windows 10 through OSGeo4W setup.

I noticed that if I process a vector layer (i.e. UTF-8 encoded geojson) with QGIS algorithm (i.e. crop, Voronoi, etc) through Processing toolbox, result layer has attribute table with question marks instead expected characters. While if I run the same algorithm through QGIS menu, result layer is correctly encoded.

I noticed also that this affects GDAL/OGR algorithms, besides QGIS algorithms, while not SAGA algorithms.

For reference I open a question first here: http://gis.stackexchange.com/questions/190137/qgis-algoritms-have-encoding-problems to new description

Some qgis algs create outputs where the attribute tables have encoding issues. Examples are buffer and dissolve. Maybe others are also affected (an example that works as expected in "voronoi polygons").

Sample data attached.

old description Hi,

I'm using QGIS 2.14.1 on Windows 10 through OSGeo4W setup.

I noticed that if I process a vector layer (i.e. UTF-8 encoded geojson) with QGIS algorithm (i.e. crop, Voronoi, etc) through Processing toolbox, result layer has attribute table with question marks instead expected characters. While if I run the same algorithm through QGIS menu, result layer is correctly encoded.

I noticed also that this affects GDAL/OGR algorithms, besides QGIS algorithms, while not SAGA algorithms.

For reference I open a question first here: http://gis.stackexchange.com/questions/190137/qgis-algoritms-have-encoding-problems

qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)

Alexander Bruy wrote:

Can't reproduce with latest 2.18 using attached sample data and native buffer and dissolve algorithms.

confirmed, if some other tool is affected please reopen this one.

status_id was changed from Feedback to Closed
resolution was changed from to fixed/implemented

qgis / QGIS

Encoding problems with Processing toolbox #22665