qgis / QGIS

QGIS is a free, open source, cross platform (lin/win/mac) geographical information system (GIS)
https://qgis.org
GNU General Public License v2.0
10.55k stars 2.99k forks source link

Refine current rule #18891

Open qgib opened 10 years ago

qgib commented 10 years ago

Author Name: Barrett Higman (@barretthigman) Original Redmine Issue: 10479

Redmine category:gui Assignee: Nathan Woodrow


It would be good that when 'Refine current rule' is used that the refinements respect the original rule that they are based on.

For example, for a road dataset, if a rule is used to exclude unsealed roads then a categorised refinement of that rule should not create classifications that include unsealed roads.



Related issue(s): #19191 (duplicates) Redmine related issue(s): 10815


qgib commented 10 years ago

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


qgib commented 10 years ago

Author Name: baditaflorin - (baditaflorin -)


I had the same poblem and i was able to do this using the CASE conditionals

CASE WHEN "pntcnt" <50 THEN "pntcnt" END

And my rule was to show only pntcnt that are lower then 50

qgib commented 10 years ago

Author Name: baditaflorin - (baditaflorin -)


But this only work for <

if you try = or > is not working

qgib commented 10 years ago

Author Name: Giovanni Manghi (@gioman)


ticket #19191 is about a different thing: expression in rule based symbology are written in a wrong way, at least when used to refine rules, see https://github.com/qgis/QGIS/issues/19191#issuecomment-495834072

qgib commented 9 years ago

Author Name: Nyall Dawson (@nyalldawson)


More detail in #20124

qgib commented 8 years ago

Author Name: Donovan Cameron (@saultdon)


This would be a great improvement to see! I've attached a screen shot to help illustrate the problem.

Also, if the "Label" that shows up in the layer list was styled with just the ranges. Otherwise it creates a large label. Maybe it could create the label similarly to how it's created when using just the "graduated" style.

Currently (it includes the expression!):

@"column" >= 0 AND "column" <= 1 "column" >= 1 AND "column" <= 4 "column" >= 4 AND "column" <= 8@

or

@(CASE WHEN "unique_value_column" = "value" THEN "column" END) >= 0 AND (CASE WHEN "unique_value_column" = "value" THEN "column" END) <= 1 (CASE WHEN "unique_value_column" = "value" THEN "column" END) >= 1 AND (CASE WHEN "unique_value_column" = "value" THEN "column" END) <= 4 (CASE WHEN "unique_value_column" = "value" THEN "column" END) >= 4 AND (CASE WHEN "unique_value_column" = "value" THEN "column" END) <= 8@

Preferred (in a simplified manner):

@0 - 1 1 - 4 4 - 8@

The preferred type is better for when viewing in the map canvas and trying to create an actual map with a legend.



qgib commented 7 years ago

Author Name: Giovanni Manghi (@gioman)