Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSM name tag encoding #39

Closed
crocovert opened this issue Nov 5, 2014 · 16 comments

Comments

@crocovert
Copy link

commented Nov 5, 2014

Hello,

I would like to know how to retrieve correct text encoding of OSM tag with Quick OSM plugin?
Should I specify text encoding somewhere in the query or should I specify an ecnoding in the layer properties (bu which enconding)

Thanks in advance

Regards

@Gustry

This comment has been minimized.

Copy link
Collaborator

commented Nov 5, 2014

Could you provide some informations about your language (OS and QGIS) ?
What do you get actually for instance ? and what it should be ?
If I can try with a query and your language in my QGIS, it would be better.

@crocovert

This comment has been minimized.

Copy link
Author

commented Nov 5, 2014

Hello,

I'm working on Qgis 2.6 and Windows 7 in french
some examples of names

"Rue Brûle Maison" instead of "Rue Brûle Maison"

"Rue Desmazières" "Rue Desmazières"

"Avenue Léon Jouhaux" "Avenue Léon Jouhaux"

"Rue de l'Hôpital "Rue de l'Hôpital"

Best regards

Patrick PALMIER
Responsable du groupe Systèmes de Transport et Sécurité
tél : +33 (0)3 20 49 60 70
mob:+33 (0)7 77 34 25 07

Centre d’études et d’expertise sur les risques, l’environnement, la
mobilité et l’aménagement - www.cerema.fr
Direction territoriale Nord-Picardie - 2, rue de Bruxelles CS 20275 -
59019 Lille Cedex
Siège social : Cité des Mobilités - 25 avenue François Mitterrand - CS
92 803 - 69674 Bron Cedex - tél : +33 (0)4 72 14 30 30

Le 05/11/2014 12:51, "> Gustry (par Internet, dépôt noreply@github.com)"
a écrit :

Could you provide some informations about your language (OS and QGIS) ?
What do you get actually for instance ? and what it should be ?
If I can try with a query and your language in my QGIS, it would be
better.


Reply to this email directly or view it on GitHub
#39 (comment).

@Gustry

This comment has been minimized.

Copy link
Collaborator

commented Nov 7, 2014

I'm also using French, I can't reproduce this bug on my PC. However I've already noticed this bug on another Windows 7.
In your temporary folder (C:\Users\AppData\Local\Temp), you should find a .osm, *.geojson and a processing/*****/.shp.
Could you open these 3 files and tell which files are affected ?

@Andre-J

This comment has been minimized.

Copy link

commented Nov 9, 2014

Can you check if the resulting layer is encoded to utf-8? Properties -> General tab.

@crocovert

This comment has been minimized.

Copy link
Author

commented Nov 12, 2014

Hello,

No the layer is encoded to system

Patrick PALMIER
Responsable du groupe Systèmes de Transport et Sécurité
tél : +33 (0)3 20 49 60 70
mob:+33 (0)7 77 34 25 07

Centre d’études et d’expertise sur les risques, l’environnement, la
mobilité et l’aménagement - www.cerema.fr
Direction territoriale Nord-Picardie - 2, rue de Bruxelles CS 20275 -
59019 Lille Cedex
Siège social : Cité des Mobilités - 25 avenue François Mitterrand - CS
92 803 - 69674 Bron Cedex - tél : +33 (0)4 72 14 30 30

Le 09/11/2014 07:44, "> AndreJ (par Internet, dépôt
bounces+848413-5eca-patrick.palmier=cerema.fr@sgmail.github.com)" a écrit :

Can you check if the resulting layer is encoded to utf-8? Properties
-> General tab.


Reply to this email directly or view it on GitHub
#39 (comment).

@Andre-J

This comment has been minimized.

Copy link

commented Nov 12, 2014

It should rather be set to UTF-8, because all OSM raw data is encoded in UTF-8.

@crocovert

This comment has been minimized.

Copy link
Author

commented Nov 12, 2014

Yes, but even when I change to utf-8, it's unreadable

Le 12/11/2014, "> AndreJ (par Internet, dépôt bounces+848413-5eca-
patrick.palmier=cerema.fr@sgmail.github.com)"
notifications@github.com a écrit:

It should rather be set to UTF-8, because all OSM raw data is
encoded in UTF-8.


Reply to this email directly or view it on GitHub:
#39 (comment)

@Andre-J

This comment has been minimized.

Copy link

commented Nov 12, 2014

Just another chance: Settings -> Options -> DataSources tab, check "Ignore shapefile encoding declaration". It might need to restart QGIS and reload the data.

@crocovert

This comment has been minimized.

Copy link
Author

commented Nov 13, 2014

In fact, it was already checked. I tried to uncheck it and restart QGis.
Then the layer is written to be encoded in utf8 (I can't change the
encoding) but texts whith special charcaters still remains unreadable

If it was checked, I can change the layer encoding , but it remains
still unreadable whatever the encoding I choose.

Patrick PALMIER
Responsable du groupe Systèmes de Transport et Sécurité
tél : +33 (0)3 20 49 60 70
mob:+33 (0)7 77 34 25 07

Centre d’études et d’expertise sur les risques, l’environnement, la
mobilité et l’aménagement - www.cerema.fr
Direction territoriale Nord-Picardie - 2, rue de Bruxelles CS 20275 -
59019 Lille Cedex
Siège social : Cité des Mobilités - 25 avenue François Mitterrand - CS
92 803 - 69674 Bron Cedex - tél : +33 (0)4 72 14 30 30

Le 12/11/2014 19:15, "> AndreJ (par Internet, dépôt noreply@github.com)"
a écrit :

Just another chance: Settings -> Options -> DataSources tab, check
"Ignore shapefile encoding declaration". It might need to restart QGIS
and reload the data.


Reply to this email directly or view it on GitHub
#39 (comment).

@Gustry

This comment has been minimized.

Copy link
Collaborator

commented Nov 13, 2014

Just to know where this issue is raised, in your temporary folder (C:\Users\AppData\Local\Temp), you should find a .osm, then a .geojson and finally a processing****__.shp.
Could you open these 3 files with QGIS and tell us which files are affected ?

@crocovert

This comment has been minimized.

Copy link
Author

commented Nov 13, 2014

The OSM seems OK but not the geojson

Patrick PALMIER
Responsable du groupe Systèmes de Transport et Sécurité
tél : +33 (0)3 20 49 60 70
mob:+33 (0)7 77 34 25 07

Centre d’études et d’expertise sur les risques, l’environnement, la
mobilité et l’aménagement - www.cerema.fr
Direction territoriale Nord-Picardie - 2, rue de Bruxelles CS 20275 -
59019 Lille Cedex
Siège social : Cité des Mobilités - 25 avenue François Mitterrand - CS
92 803 - 69674 Bron Cedex - tél : +33 (0)4 72 14 30 30

Le 13/11/2014 08:33, "> Gustry (par Internet, dépôt noreply@github.com)"
a écrit :

Just to know where this issue is raised, in your temporary folder
(C:\Users\AppData\Local\Temp), you should find a .osm, then a .geojson
and finally a processing******.shp.
Could you open these 3 files with QGIS and tell us which files are
affected ?


Reply to this email directly or view it on GitHub
#39 (comment).

@Gustry Gustry added the bug label Dec 7, 2014
Gustry added a commit that referenced this issue Mar 16, 2015
@Gustry

This comment has been minimized.

Copy link
Collaborator

commented Mar 16, 2015

Hi @crocovert,
A new version of the plugin has been released.
Could you check that shapefiles are now well encoded on your system ?

@crocovert

This comment has been minimized.

Copy link
Author

commented Mar 18, 2015

Hello

Soory but in my windows 7 desktop it still doesn't work well (problem in
GeoJSON file)
But it works in my Linux PC

Patrick PALMIER
Responsable du groupe Systèmes de Transport et Sécurité
tél : +33 (0)3 20 49 60 70
mob:+33 (0)7 77 34 25 07

Centre d’études et d’expertise sur les risques, l’environnement, la
mobilité et l’aménagement - www.cerema.fr
Direction territoriale Nord-Picardie - 2, rue de Bruxelles CS 20275 -
59019 Lille Cedex
Siège social : Cité des Mobilités - 25 avenue François Mitterrand - CS
92 803 - 69674 Bron Cedex - tél : +33 (0)4 72 14 30 30

Le 16/03/2015 21:51, "> Etienne Trimaille (par Internet, dépôt
noreply@github.com)" a écrit :

Hi @crocovert https://github.com/crocovert,
A new version of the plugin has been released.
Could you check that shapefiles are now well encoded on your system ?


Reply to this email directly or view it on GitHub
#39 (comment).

@stephan75

This comment has been minimized.

Copy link

commented Mar 18, 2015

same issue still here on a Win7 system with latest quickosm 1.3

On Linux system, character encoding is OK

@Gustry

This comment has been minimized.

Copy link
Collaborator

commented Apr 1, 2015

Could you test again with 1.3.1 which has been released tonight ?

@crocovert

This comment has been minimized.

Copy link
Author

commented Apr 2, 2015

Hello,

It seems to work well now
Thanks. Great job!

Patrick PALMIER
Responsable du groupe Systèmes de Transport et Sécurité
tél : +33 (0)3 20 49 60 70
mob:+33 (0)7 77 34 25 07

Centre d’études et d’expertise sur les risques, l’environnement, la
mobilité et l’aménagement - www.cerema.fr
Direction territoriale Nord-Picardie - 2, rue de Bruxelles CS 20275 -
59019 Lille Cedex
Siège social : Cité des Mobilités - 25 avenue François Mitterrand - CS
92 803 - 69674 Bron Cedex - tél : +33 (0)4 72 14 30 30

Le 02/04/2015 01:27, "> Etienne Trimaille (par Internet, dépôt
bounces+848413-5eca-patrick.palmier=cerema.fr@sgmail.github.com)" a écrit :

Could you test again with 1.3.1 which has been released tonight ?


Reply to this email directly or view it on GitHub
#39 (comment).

@Gustry Gustry closed this Apr 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.