-
Notifications
You must be signed in to change notification settings - Fork 1
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
Value 'XX' does not exist in association #21
Comments
Hello, I have a similar problem when doing the step 3 of rasterization. I tried running the program with a shp file but it shows "Value 'Forêt fermée de conifères' does not exist in association". However, the program worked with another layer that was a gpkg even if the cathegories had accents too. Is there a way to solve this? |
Hello, If you load this shp layer directly into QGIS, are the values correctly loaded ? I assume you work with Windows ? Regards, |
Hello,
Yes, they load normally on QGIS. I am using the BD TOPO layers in
particular the vegetation zone and roads.
I solved it by changing the name of the values that have accents.
I am working on a mac but I tried it on windows and also had similar
problems.
Thank you
Emilia
El vie, 9 ago 2024 a las 11:25, MathieuChailloux ***@***.***>)
escribió:
… Hello,
If you load this shp layer directly into QGIS, are the values correctly
loaded ?
And what is your layer encoding ?
I assume you work with Windows ?
Regards,
Mathieu
—
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKKTSB3IFN2AZADALNQE7CTZQSDJBAVCNFSM6AAAAABMAQHXSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGUZTGMZWG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Could you send me your problematic layer (with accent) to [email protected] ? I'll try to reproduce error on my config. Regards, |
Error occurs when applying selection by field on layer loaded from QGIS GUI (drag and drop) if field value contains an accent (encoding UTF 8).
The text was updated successfully, but these errors were encountered: