-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Vector cannot be styled by joined attributes #17466
Comments
Author Name: Giovanni Manghi (@gioman) Hi, I cannot confirm here, try the attached shapefiles: join "join2" to "join1" and use the "code06" column to do the symbology.
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Radim Blazek (@blazek) Thanks for testing. For me it does not work. Table is OK, identify OK, feature counts for classes in legend are OK but everything is rendered with the color assigned to empty value (NULL). I tried also to check/uncheck "Cache join layer in virtual memory" and "Create attribute index on join field" but no effect. Styles based on attributes from base layer are working without problems. Current master dae9b5d, GDAL 1.10.1, Debian 7. |
Author Name: Giovanni Manghi (@gioman) Radim Blazek wrote:
so for you doesn't work with the data I have attached here? |
Author Name: Radim Blazek (@blazek) Giovanni Manghi wrote:
No. |
Author Name: Denis Rouzaud (@3nids) I confirm it does not work, also for rule-based symbologoy. features not drawn but can be identified! |
Author Name: Giovanni Manghi (@gioman) yeah I confirm it, I don't what I have done wrong the first time i tested. Isn't this a regression?
|
Author Name: Matthias Kuhn (@m-kuhn) Fixed in changeset "5e14fea1b856e4178f545c9a81ce7090240bc06c".
|
Author Name: Radim Blazek (@blazek)
Original Redmine Issue: 8757
Affected QGIS version: master
Redmine category:symbology
Vector layers cannot be styled (categorized, graduated, ...) based on attributes from
joined table. All features are rendered in class with empty value.
Tested with two Shapefiles joined.
The text was updated successfully, but these errors were encountered: