How to symbolize features with NULL values in graduated symbology? Planned maintenance...
Why isn't everyone flabbergasted about Bran's "gift"?
What helicopter has the most rotor blades?
Etymology of 見舞い
Suing a Police Officer Instead of the Police Department
Pointing to problems without suggesting solutions
Can the van der Waals coefficients be negative in the van der Waals equation for real gases?
How to create a command for the "strange m" symbol in latex?
“Since the train was delayed for more than an hour, passengers were given a full refund.” – Why is there no article before “passengers”?
Why do C and C++ allow the expression (int) + 4*5?
Why aren't these two solutions equivalent? Combinatorics problem
Why did Israel vote against lifting the American embargo on Cuba?
What came first? Venom as the movie or as the song?
Kepler's 3rd law: ratios don't fit data
Sorting the characters in a utf-16 string in java
Recursive calls to a function - why is the address of the parameter passed to it lowering with each call?
Will I be more secure with my own router behind my ISP's router?
When speaking, how do you change your mind mid-sentence?
Converting a text document with special format to Pandas DataFrame
Why do people think Winterfell crypts is the safest place for women, children & old people?
Can I take recommendation from someone I met at a conference?
Raising a bilingual kid. When should we introduce the majority language?
Does the Pact of the Blade warlock feature allow me to customize the properties of the pact weapon I create?
Can a Wizard take the Magic Initiate feat and select spells from the Wizard list?
Providing direct feedback to a product salesperson
How to symbolize features with NULL values in graduated symbology?
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?How can I handle NULL values in a color ramp?How to display missing objects in QGIS 2.8.2 cartogram?'Locking' intervals in interval determinationCopying Symbology between layers with different numbers of featuresGraduated values in symbology based on specific attribute in QGISHow to symbolize null values in ArcGIS using Quantities symbology?Ignoring certain data values in graduated mapsHow does `ST_Union` treat NULL values in a raster?Join tables in QGis 2.01. DufourSymbolize feature with most recent data if any existsHow to batch set symbology to Proportional Symbology in ArcMap?Representing NULL data for a numeric field in ArcGIS (symbology)Present polygon features in legend with custom symbology
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have a polygon feature dataset, and an attribute from a different table that I join (one-to-one) within QGIS in order to symbolise the attributes as a choropleth map. However, not all polygon fields have a matching field in the table of numerical attributes, so there are some null values when producing the graduated symbology.
From my research, the most common piece of advice in this situation is to include a copy of the polygon dataset (or some other background) that defines a default symbology. This works because the null values are not classified in the graduated symbology, so one can see "underneath" them. I have attached an image of exactly this. The dark grey features do not exist in the join table (mb_percentile_isochrones_all), but do exist in the boundary polygons table (mb2013_wgtn). So I need two instances of the mb2013_wgtn table in order to show the "no data" features.
However, this does not seem elegant to me. Much more intuitive would be to define a null value symbol. Perhaps this could be perfectly transparent to be consistent with what currently exists, or perhaps it would be some kind of muted grey—whatever the user wants. The point is, at present one needs two different layers in the contents in order to handle the symbology of null values. This means that to change the symbology of all your features at the same time (say, if you want to increase the width of all borders), this has to be handled twice: once in the properties for the feature with the graduated symbology, and once for the "background" layer that handles the null symbol.
Is it possible to define a "null" value symbol without using a "copy" of the same layer used for the graduated symbology, in QGIS (2.6.1)?
qgis postgis symbology attribute-joins
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
add a comment |
I have a polygon feature dataset, and an attribute from a different table that I join (one-to-one) within QGIS in order to symbolise the attributes as a choropleth map. However, not all polygon fields have a matching field in the table of numerical attributes, so there are some null values when producing the graduated symbology.
From my research, the most common piece of advice in this situation is to include a copy of the polygon dataset (or some other background) that defines a default symbology. This works because the null values are not classified in the graduated symbology, so one can see "underneath" them. I have attached an image of exactly this. The dark grey features do not exist in the join table (mb_percentile_isochrones_all), but do exist in the boundary polygons table (mb2013_wgtn). So I need two instances of the mb2013_wgtn table in order to show the "no data" features.
However, this does not seem elegant to me. Much more intuitive would be to define a null value symbol. Perhaps this could be perfectly transparent to be consistent with what currently exists, or perhaps it would be some kind of muted grey—whatever the user wants. The point is, at present one needs two different layers in the contents in order to handle the symbology of null values. This means that to change the symbology of all your features at the same time (say, if you want to increase the width of all borders), this has to be handled twice: once in the properties for the feature with the graduated symbology, and once for the "background" layer that handles the null symbol.
Is it possible to define a "null" value symbol without using a "copy" of the same layer used for the graduated symbology, in QGIS (2.6.1)?
qgis postgis symbology attribute-joins
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
What's wrong with having the same layer twice with different symbology? Perhaps use attribute filtering so that no polygon appears in both layers if you're getting confusion in identify or geoprocessing. Are the unmatched features 'null' in their join value or do they have a value that doesn't appear in the table?
– Michael Stimson
Jan 7 '15 at 3:10
1
1. Problem: if I want to control the common properties of features with a value and with a null (e.g. border colour), it has be be performed twice. This makes it much easier to forget to change one of them, or to make a slight mistake (e.g. wrong shade of grey for the outline). 2. No problems regarding confusion for geoprocessing, just the symbology: I want to symbolise thenullfeature in the same layer. 3. Unmatched features arenullin their join value (as seen in the QGIS attribute table post-join).
– Richard Law
Jan 7 '15 at 3:14
It also makes it more difficult when building a legend to include a "no data" sample, as this symbol would come from a different layer.
– Richard Law
Jan 7 '15 at 3:23
2
You're right. There is nowhere to select 'show NULL features like this' in the graduated symbol dialog, rows with NULL values are simply not shown.
– Michael Stimson
Jan 7 '15 at 3:23
add a comment |
I have a polygon feature dataset, and an attribute from a different table that I join (one-to-one) within QGIS in order to symbolise the attributes as a choropleth map. However, not all polygon fields have a matching field in the table of numerical attributes, so there are some null values when producing the graduated symbology.
From my research, the most common piece of advice in this situation is to include a copy of the polygon dataset (or some other background) that defines a default symbology. This works because the null values are not classified in the graduated symbology, so one can see "underneath" them. I have attached an image of exactly this. The dark grey features do not exist in the join table (mb_percentile_isochrones_all), but do exist in the boundary polygons table (mb2013_wgtn). So I need two instances of the mb2013_wgtn table in order to show the "no data" features.
However, this does not seem elegant to me. Much more intuitive would be to define a null value symbol. Perhaps this could be perfectly transparent to be consistent with what currently exists, or perhaps it would be some kind of muted grey—whatever the user wants. The point is, at present one needs two different layers in the contents in order to handle the symbology of null values. This means that to change the symbology of all your features at the same time (say, if you want to increase the width of all borders), this has to be handled twice: once in the properties for the feature with the graduated symbology, and once for the "background" layer that handles the null symbol.
Is it possible to define a "null" value symbol without using a "copy" of the same layer used for the graduated symbology, in QGIS (2.6.1)?
qgis postgis symbology attribute-joins
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
I have a polygon feature dataset, and an attribute from a different table that I join (one-to-one) within QGIS in order to symbolise the attributes as a choropleth map. However, not all polygon fields have a matching field in the table of numerical attributes, so there are some null values when producing the graduated symbology.
From my research, the most common piece of advice in this situation is to include a copy of the polygon dataset (or some other background) that defines a default symbology. This works because the null values are not classified in the graduated symbology, so one can see "underneath" them. I have attached an image of exactly this. The dark grey features do not exist in the join table (mb_percentile_isochrones_all), but do exist in the boundary polygons table (mb2013_wgtn). So I need two instances of the mb2013_wgtn table in order to show the "no data" features.
However, this does not seem elegant to me. Much more intuitive would be to define a null value symbol. Perhaps this could be perfectly transparent to be consistent with what currently exists, or perhaps it would be some kind of muted grey—whatever the user wants. The point is, at present one needs two different layers in the contents in order to handle the symbology of null values. This means that to change the symbology of all your features at the same time (say, if you want to increase the width of all borders), this has to be handled twice: once in the properties for the feature with the graduated symbology, and once for the "background" layer that handles the null symbol.
Is it possible to define a "null" value symbol without using a "copy" of the same layer used for the graduated symbology, in QGIS (2.6.1)?
qgis postgis symbology attribute-joins
qgis postgis symbology attribute-joins
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
edited Feb 10 '16 at 21:13
underdark♦
69.3k13178351
69.3k13178351
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
asked Jan 7 '15 at 1:32
Richard LawRichard Law
4,59321558
4,59321558
What's wrong with having the same layer twice with different symbology? Perhaps use attribute filtering so that no polygon appears in both layers if you're getting confusion in identify or geoprocessing. Are the unmatched features 'null' in their join value or do they have a value that doesn't appear in the table?
– Michael Stimson
Jan 7 '15 at 3:10
1
1. Problem: if I want to control the common properties of features with a value and with a null (e.g. border colour), it has be be performed twice. This makes it much easier to forget to change one of them, or to make a slight mistake (e.g. wrong shade of grey for the outline). 2. No problems regarding confusion for geoprocessing, just the symbology: I want to symbolise thenullfeature in the same layer. 3. Unmatched features arenullin their join value (as seen in the QGIS attribute table post-join).
– Richard Law
Jan 7 '15 at 3:14
It also makes it more difficult when building a legend to include a "no data" sample, as this symbol would come from a different layer.
– Richard Law
Jan 7 '15 at 3:23
2
You're right. There is nowhere to select 'show NULL features like this' in the graduated symbol dialog, rows with NULL values are simply not shown.
– Michael Stimson
Jan 7 '15 at 3:23
add a comment |
What's wrong with having the same layer twice with different symbology? Perhaps use attribute filtering so that no polygon appears in both layers if you're getting confusion in identify or geoprocessing. Are the unmatched features 'null' in their join value or do they have a value that doesn't appear in the table?
– Michael Stimson
Jan 7 '15 at 3:10
1
1. Problem: if I want to control the common properties of features with a value and with a null (e.g. border colour), it has be be performed twice. This makes it much easier to forget to change one of them, or to make a slight mistake (e.g. wrong shade of grey for the outline). 2. No problems regarding confusion for geoprocessing, just the symbology: I want to symbolise thenullfeature in the same layer. 3. Unmatched features arenullin their join value (as seen in the QGIS attribute table post-join).
– Richard Law
Jan 7 '15 at 3:14
It also makes it more difficult when building a legend to include a "no data" sample, as this symbol would come from a different layer.
– Richard Law
Jan 7 '15 at 3:23
2
You're right. There is nowhere to select 'show NULL features like this' in the graduated symbol dialog, rows with NULL values are simply not shown.
– Michael Stimson
Jan 7 '15 at 3:23
What's wrong with having the same layer twice with different symbology? Perhaps use attribute filtering so that no polygon appears in both layers if you're getting confusion in identify or geoprocessing. Are the unmatched features 'null' in their join value or do they have a value that doesn't appear in the table?
– Michael Stimson
Jan 7 '15 at 3:10
What's wrong with having the same layer twice with different symbology? Perhaps use attribute filtering so that no polygon appears in both layers if you're getting confusion in identify or geoprocessing. Are the unmatched features 'null' in their join value or do they have a value that doesn't appear in the table?
– Michael Stimson
Jan 7 '15 at 3:10
1
1
1. Problem: if I want to control the common properties of features with a value and with a null (e.g. border colour), it has be be performed twice. This makes it much easier to forget to change one of them, or to make a slight mistake (e.g. wrong shade of grey for the outline). 2. No problems regarding confusion for geoprocessing, just the symbology: I want to symbolise the
null feature in the same layer. 3. Unmatched features are null in their join value (as seen in the QGIS attribute table post-join).– Richard Law
Jan 7 '15 at 3:14
1. Problem: if I want to control the common properties of features with a value and with a null (e.g. border colour), it has be be performed twice. This makes it much easier to forget to change one of them, or to make a slight mistake (e.g. wrong shade of grey for the outline). 2. No problems regarding confusion for geoprocessing, just the symbology: I want to symbolise the
null feature in the same layer. 3. Unmatched features are null in their join value (as seen in the QGIS attribute table post-join).– Richard Law
Jan 7 '15 at 3:14
It also makes it more difficult when building a legend to include a "no data" sample, as this symbol would come from a different layer.
– Richard Law
Jan 7 '15 at 3:23
It also makes it more difficult when building a legend to include a "no data" sample, as this symbol would come from a different layer.
– Richard Law
Jan 7 '15 at 3:23
2
2
You're right. There is nowhere to select 'show NULL features like this' in the graduated symbol dialog, rows with NULL values are simply not shown.
– Michael Stimson
Jan 7 '15 at 3:23
You're right. There is nowhere to select 'show NULL features like this' in the graduated symbol dialog, rows with NULL values are simply not shown.
– Michael Stimson
Jan 7 '15 at 3:23
add a comment |
3 Answers
3
active
oldest
votes
As @MichaelMiles-Stimson already mentioned, there doesn't seem to be a way to symbolise NULL features. However, there is an alternative whereby you create a filter to force QGIS to treat NULL values as an integer such as 0. I've included an example where I created 3 simple polygons each with a certain value:
Here is the Graduated Symbology I used with the following command:
case when "Some_Value" IS NULL then 0 else "Some_Value" end
Hope this helps!
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
This is quite helpful and I'll probably put this into practice. The problem I anticipate is that 0 is a meaningful value in my dataset. I could probably use -1 or something. But in either case this would make the automatic identification of class breaks slightly unwieldy. Perhaps I should submit a feature request for this given it's now clear the workarounds are less than ideal.
– Richard Law
Jan 7 '15 at 19:16
Yes, includingNULLvalues could be quite useful. It's not a pretty workaround but you can always submit a feature request and hope it becomes available in the next version :)
– Joseph
Jan 8 '15 at 10:10
add a comment |
I know it has been answered, but just to give another option:
You can just leave the field with no filter or value (I know it works for CATEGORIZED or RULE BASED):
http://docs.qgis.org/2.0/uk/docs/training_manual/vector_classification/classification.html
I'm using QGIS 2.10 and it works.
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
Always nice to know more methods in solving or working around a problem! +1
– Joseph
Sep 21 '15 at 11:57
1
Encouraging to see this improvement since 2.6, right? Can you confirm that it works when the null values come from a joined table?
– Richard Law
Sep 21 '15 at 12:00
1
A couple of notes on this though. The blank or NULL symbology in a rule based symbology will be applied to ALL features. The rules are applied from the top down, so it may be overlayed by another rule, but the NULL will also be there. Important if it is a strong symbology. You can also "generate" you rules by first creating them in the Categorized or Graduated symbology and then switching to Rule Based/
– HeikkiVesanto
Sep 21 '15 at 14:18
@Vesanto, I don't know if I got it, or if it is a problem. In my case, I'm adding Z values to a SHP made of contour lines, that originally had no Z values (Z = NULL). I've set the features with NULL values to red and the ones with any value to black. When editing, as soon as I set a Z value, the feature (the contour line) turns from red to black, this way I know the ones that I'm yet to set the Z value.
– Marcos Saito
Sep 21 '15 at 14:50
@Marcos it won't be an issue in your case. But lets say the line was red to begin with, and you wanted to turn it invisible once it was not null anymore. That would not work.
– HeikkiVesanto
Sep 21 '15 at 18:46
|
show 1 more comment
Similar to what other users have said, the best option is to use rule-based symbols.
To avoid manually creating the rules:
- Change the symbol type to Graduated.
- Define the symbol column, colours, intervals etc. as per normal
- Change the symbol type from Graduated to Rule-based. The symbols defined in the previous step will be carried over. Click the add symbol button, and select ELSE. Change the style as appropriate. This ELSE symbol class will catch any values that haven't been symbolised already, including null values.
- Click OK. Null values will now be symbolised.
(Tested in QGIS 3.6.0)
answered 25 mins ago
Jesse ReillyJesse Reilly
1
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f128358%2fhow-to-symbolize-features-with-null-values-in-graduated-symbology%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
As @MichaelMiles-Stimson already mentioned, there doesn't seem to be a way to symbolise NULL features. However, there is an alternative whereby you create a filter to force QGIS to treat NULL values as an integer such as 0. I've included an example where I created 3 simple polygons each with a certain value:
Here is the Graduated Symbology I used with the following command:
case when "Some_Value" IS NULL then 0 else "Some_Value" end
Hope this helps!
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
This is quite helpful and I'll probably put this into practice. The problem I anticipate is that 0 is a meaningful value in my dataset. I could probably use -1 or something. But in either case this would make the automatic identification of class breaks slightly unwieldy. Perhaps I should submit a feature request for this given it's now clear the workarounds are less than ideal.
– Richard Law
Jan 7 '15 at 19:16
Yes, includingNULLvalues could be quite useful. It's not a pretty workaround but you can always submit a feature request and hope it becomes available in the next version :)
– Joseph
Jan 8 '15 at 10:10
add a comment |
As @MichaelMiles-Stimson already mentioned, there doesn't seem to be a way to symbolise NULL features. However, there is an alternative whereby you create a filter to force QGIS to treat NULL values as an integer such as 0. I've included an example where I created 3 simple polygons each with a certain value:
Here is the Graduated Symbology I used with the following command:
case when "Some_Value" IS NULL then 0 else "Some_Value" end
Hope this helps!
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
This is quite helpful and I'll probably put this into practice. The problem I anticipate is that 0 is a meaningful value in my dataset. I could probably use -1 or something. But in either case this would make the automatic identification of class breaks slightly unwieldy. Perhaps I should submit a feature request for this given it's now clear the workarounds are less than ideal.
– Richard Law
Jan 7 '15 at 19:16
Yes, includingNULLvalues could be quite useful. It's not a pretty workaround but you can always submit a feature request and hope it becomes available in the next version :)
– Joseph
Jan 8 '15 at 10:10
add a comment |
As @MichaelMiles-Stimson already mentioned, there doesn't seem to be a way to symbolise NULL features. However, there is an alternative whereby you create a filter to force QGIS to treat NULL values as an integer such as 0. I've included an example where I created 3 simple polygons each with a certain value:
Here is the Graduated Symbology I used with the following command:
case when "Some_Value" IS NULL then 0 else "Some_Value" end
Hope this helps!
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
As @MichaelMiles-Stimson already mentioned, there doesn't seem to be a way to symbolise NULL features. However, there is an alternative whereby you create a filter to force QGIS to treat NULL values as an integer such as 0. I've included an example where I created 3 simple polygons each with a certain value:
Here is the Graduated Symbology I used with the following command:
case when "Some_Value" IS NULL then 0 else "Some_Value" end
Hope this helps!
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
answered Jan 7 '15 at 10:29
JosephJoseph
59.1k7102207
59.1k7102207
This is quite helpful and I'll probably put this into practice. The problem I anticipate is that 0 is a meaningful value in my dataset. I could probably use -1 or something. But in either case this would make the automatic identification of class breaks slightly unwieldy. Perhaps I should submit a feature request for this given it's now clear the workarounds are less than ideal.
– Richard Law
Jan 7 '15 at 19:16
Yes, includingNULLvalues could be quite useful. It's not a pretty workaround but you can always submit a feature request and hope it becomes available in the next version :)
– Joseph
Jan 8 '15 at 10:10
add a comment |
This is quite helpful and I'll probably put this into practice. The problem I anticipate is that 0 is a meaningful value in my dataset. I could probably use -1 or something. But in either case this would make the automatic identification of class breaks slightly unwieldy. Perhaps I should submit a feature request for this given it's now clear the workarounds are less than ideal.
– Richard Law
Jan 7 '15 at 19:16
Yes, includingNULLvalues could be quite useful. It's not a pretty workaround but you can always submit a feature request and hope it becomes available in the next version :)
– Joseph
Jan 8 '15 at 10:10
This is quite helpful and I'll probably put this into practice. The problem I anticipate is that 0 is a meaningful value in my dataset. I could probably use -1 or something. But in either case this would make the automatic identification of class breaks slightly unwieldy. Perhaps I should submit a feature request for this given it's now clear the workarounds are less than ideal.
– Richard Law
Jan 7 '15 at 19:16
This is quite helpful and I'll probably put this into practice. The problem I anticipate is that 0 is a meaningful value in my dataset. I could probably use -1 or something. But in either case this would make the automatic identification of class breaks slightly unwieldy. Perhaps I should submit a feature request for this given it's now clear the workarounds are less than ideal.
– Richard Law
Jan 7 '15 at 19:16
Yes, including
NULL values could be quite useful. It's not a pretty workaround but you can always submit a feature request and hope it becomes available in the next version :)– Joseph
Jan 8 '15 at 10:10
Yes, including
NULL values could be quite useful. It's not a pretty workaround but you can always submit a feature request and hope it becomes available in the next version :)– Joseph
Jan 8 '15 at 10:10
add a comment |
I know it has been answered, but just to give another option:
You can just leave the field with no filter or value (I know it works for CATEGORIZED or RULE BASED):
http://docs.qgis.org/2.0/uk/docs/training_manual/vector_classification/classification.html
I'm using QGIS 2.10 and it works.
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
Always nice to know more methods in solving or working around a problem! +1
– Joseph
Sep 21 '15 at 11:57
1
Encouraging to see this improvement since 2.6, right? Can you confirm that it works when the null values come from a joined table?
– Richard Law
Sep 21 '15 at 12:00
1
A couple of notes on this though. The blank or NULL symbology in a rule based symbology will be applied to ALL features. The rules are applied from the top down, so it may be overlayed by another rule, but the NULL will also be there. Important if it is a strong symbology. You can also "generate" you rules by first creating them in the Categorized or Graduated symbology and then switching to Rule Based/
– HeikkiVesanto
Sep 21 '15 at 14:18
@Vesanto, I don't know if I got it, or if it is a problem. In my case, I'm adding Z values to a SHP made of contour lines, that originally had no Z values (Z = NULL). I've set the features with NULL values to red and the ones with any value to black. When editing, as soon as I set a Z value, the feature (the contour line) turns from red to black, this way I know the ones that I'm yet to set the Z value.
– Marcos Saito
Sep 21 '15 at 14:50
@Marcos it won't be an issue in your case. But lets say the line was red to begin with, and you wanted to turn it invisible once it was not null anymore. That would not work.
– HeikkiVesanto
Sep 21 '15 at 18:46
|
show 1 more comment
I know it has been answered, but just to give another option:
You can just leave the field with no filter or value (I know it works for CATEGORIZED or RULE BASED):
http://docs.qgis.org/2.0/uk/docs/training_manual/vector_classification/classification.html
I'm using QGIS 2.10 and it works.
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
Always nice to know more methods in solving or working around a problem! +1
– Joseph
Sep 21 '15 at 11:57
1
Encouraging to see this improvement since 2.6, right? Can you confirm that it works when the null values come from a joined table?
– Richard Law
Sep 21 '15 at 12:00
1
A couple of notes on this though. The blank or NULL symbology in a rule based symbology will be applied to ALL features. The rules are applied from the top down, so it may be overlayed by another rule, but the NULL will also be there. Important if it is a strong symbology. You can also "generate" you rules by first creating them in the Categorized or Graduated symbology and then switching to Rule Based/
– HeikkiVesanto
Sep 21 '15 at 14:18
@Vesanto, I don't know if I got it, or if it is a problem. In my case, I'm adding Z values to a SHP made of contour lines, that originally had no Z values (Z = NULL). I've set the features with NULL values to red and the ones with any value to black. When editing, as soon as I set a Z value, the feature (the contour line) turns from red to black, this way I know the ones that I'm yet to set the Z value.
– Marcos Saito
Sep 21 '15 at 14:50
@Marcos it won't be an issue in your case. But lets say the line was red to begin with, and you wanted to turn it invisible once it was not null anymore. That would not work.
– HeikkiVesanto
Sep 21 '15 at 18:46
|
show 1 more comment
I know it has been answered, but just to give another option:
You can just leave the field with no filter or value (I know it works for CATEGORIZED or RULE BASED):
http://docs.qgis.org/2.0/uk/docs/training_manual/vector_classification/classification.html
I'm using QGIS 2.10 and it works.
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
I know it has been answered, but just to give another option:
You can just leave the field with no filter or value (I know it works for CATEGORIZED or RULE BASED):
http://docs.qgis.org/2.0/uk/docs/training_manual/vector_classification/classification.html
I'm using QGIS 2.10 and it works.
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
edited Sep 21 '15 at 12:24
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
answered Sep 21 '15 at 11:54
Marcos SaitoMarcos Saito
372314
372314
Always nice to know more methods in solving or working around a problem! +1
– Joseph
Sep 21 '15 at 11:57
1
Encouraging to see this improvement since 2.6, right? Can you confirm that it works when the null values come from a joined table?
– Richard Law
Sep 21 '15 at 12:00
1
A couple of notes on this though. The blank or NULL symbology in a rule based symbology will be applied to ALL features. The rules are applied from the top down, so it may be overlayed by another rule, but the NULL will also be there. Important if it is a strong symbology. You can also "generate" you rules by first creating them in the Categorized or Graduated symbology and then switching to Rule Based/
– HeikkiVesanto
Sep 21 '15 at 14:18
@Vesanto, I don't know if I got it, or if it is a problem. In my case, I'm adding Z values to a SHP made of contour lines, that originally had no Z values (Z = NULL). I've set the features with NULL values to red and the ones with any value to black. When editing, as soon as I set a Z value, the feature (the contour line) turns from red to black, this way I know the ones that I'm yet to set the Z value.
– Marcos Saito
Sep 21 '15 at 14:50
@Marcos it won't be an issue in your case. But lets say the line was red to begin with, and you wanted to turn it invisible once it was not null anymore. That would not work.
– HeikkiVesanto
Sep 21 '15 at 18:46
|
show 1 more comment
Always nice to know more methods in solving or working around a problem! +1
– Joseph
Sep 21 '15 at 11:57
1
Encouraging to see this improvement since 2.6, right? Can you confirm that it works when the null values come from a joined table?
– Richard Law
Sep 21 '15 at 12:00
1
A couple of notes on this though. The blank or NULL symbology in a rule based symbology will be applied to ALL features. The rules are applied from the top down, so it may be overlayed by another rule, but the NULL will also be there. Important if it is a strong symbology. You can also "generate" you rules by first creating them in the Categorized or Graduated symbology and then switching to Rule Based/
– HeikkiVesanto
Sep 21 '15 at 14:18
@Vesanto, I don't know if I got it, or if it is a problem. In my case, I'm adding Z values to a SHP made of contour lines, that originally had no Z values (Z = NULL). I've set the features with NULL values to red and the ones with any value to black. When editing, as soon as I set a Z value, the feature (the contour line) turns from red to black, this way I know the ones that I'm yet to set the Z value.
– Marcos Saito
Sep 21 '15 at 14:50
@Marcos it won't be an issue in your case. But lets say the line was red to begin with, and you wanted to turn it invisible once it was not null anymore. That would not work.
– HeikkiVesanto
Sep 21 '15 at 18:46
Always nice to know more methods in solving or working around a problem! +1
– Joseph
Sep 21 '15 at 11:57
Always nice to know more methods in solving or working around a problem! +1
– Joseph
Sep 21 '15 at 11:57
1
1
Encouraging to see this improvement since 2.6, right? Can you confirm that it works when the null values come from a joined table?
– Richard Law
Sep 21 '15 at 12:00
Encouraging to see this improvement since 2.6, right? Can you confirm that it works when the null values come from a joined table?
– Richard Law
Sep 21 '15 at 12:00
1
1
A couple of notes on this though. The blank or NULL symbology in a rule based symbology will be applied to ALL features. The rules are applied from the top down, so it may be overlayed by another rule, but the NULL will also be there. Important if it is a strong symbology. You can also "generate" you rules by first creating them in the Categorized or Graduated symbology and then switching to Rule Based/
– HeikkiVesanto
Sep 21 '15 at 14:18
A couple of notes on this though. The blank or NULL symbology in a rule based symbology will be applied to ALL features. The rules are applied from the top down, so it may be overlayed by another rule, but the NULL will also be there. Important if it is a strong symbology. You can also "generate" you rules by first creating them in the Categorized or Graduated symbology and then switching to Rule Based/
– HeikkiVesanto
Sep 21 '15 at 14:18
@Vesanto, I don't know if I got it, or if it is a problem. In my case, I'm adding Z values to a SHP made of contour lines, that originally had no Z values (Z = NULL). I've set the features with NULL values to red and the ones with any value to black. When editing, as soon as I set a Z value, the feature (the contour line) turns from red to black, this way I know the ones that I'm yet to set the Z value.
– Marcos Saito
Sep 21 '15 at 14:50
@Vesanto, I don't know if I got it, or if it is a problem. In my case, I'm adding Z values to a SHP made of contour lines, that originally had no Z values (Z = NULL). I've set the features with NULL values to red and the ones with any value to black. When editing, as soon as I set a Z value, the feature (the contour line) turns from red to black, this way I know the ones that I'm yet to set the Z value.
– Marcos Saito
Sep 21 '15 at 14:50
@Marcos it won't be an issue in your case. But lets say the line was red to begin with, and you wanted to turn it invisible once it was not null anymore. That would not work.
– HeikkiVesanto
Sep 21 '15 at 18:46
@Marcos it won't be an issue in your case. But lets say the line was red to begin with, and you wanted to turn it invisible once it was not null anymore. That would not work.
– HeikkiVesanto
Sep 21 '15 at 18:46
|
show 1 more comment
Similar to what other users have said, the best option is to use rule-based symbols.
To avoid manually creating the rules:
- Change the symbol type to Graduated.
- Define the symbol column, colours, intervals etc. as per normal
- Change the symbol type from Graduated to Rule-based. The symbols defined in the previous step will be carried over. Click the add symbol button, and select ELSE. Change the style as appropriate. This ELSE symbol class will catch any values that haven't been symbolised already, including null values.
- Click OK. Null values will now be symbolised.
(Tested in QGIS 3.6.0)
answered 25 mins ago
Jesse ReillyJesse Reilly
1
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Similar to what other users have said, the best option is to use rule-based symbols.
To avoid manually creating the rules:
- Change the symbol type to Graduated.
- Define the symbol column, colours, intervals etc. as per normal
- Change the symbol type from Graduated to Rule-based. The symbols defined in the previous step will be carried over. Click the add symbol button, and select ELSE. Change the style as appropriate. This ELSE symbol class will catch any values that haven't been symbolised already, including null values.
- Click OK. Null values will now be symbolised.
(Tested in QGIS 3.6.0)
answered 25 mins ago
Jesse ReillyJesse Reilly
1
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Similar to what other users have said, the best option is to use rule-based symbols.
To avoid manually creating the rules:
- Change the symbol type to Graduated.
- Define the symbol column, colours, intervals etc. as per normal
- Change the symbol type from Graduated to Rule-based. The symbols defined in the previous step will be carried over. Click the add symbol button, and select ELSE. Change the style as appropriate. This ELSE symbol class will catch any values that haven't been symbolised already, including null values.
- Click OK. Null values will now be symbolised.
(Tested in QGIS 3.6.0)
answered 25 mins ago
Jesse ReillyJesse Reilly
1
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Similar to what other users have said, the best option is to use rule-based symbols.
To avoid manually creating the rules:
- Change the symbol type to Graduated.
- Define the symbol column, colours, intervals etc. as per normal
- Change the symbol type from Graduated to Rule-based. The symbols defined in the previous step will be carried over. Click the add symbol button, and select ELSE. Change the style as appropriate. This ELSE symbol class will catch any values that haven't been symbolised already, including null values.
- Click OK. Null values will now be symbolised.
(Tested in QGIS 3.6.0)
answered 25 mins ago
Jesse ReillyJesse Reilly
1
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 25 mins ago
Jesse ReillyJesse Reilly
1
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 25 mins ago
Jesse ReillyJesse Reilly
1
answered 25 mins ago
Jesse ReillyJesse Reilly
1
1
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jesse Reilly is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f128358%2fhow-to-symbolize-features-with-null-values-in-graduated-symbology%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's wrong with having the same layer twice with different symbology? Perhaps use attribute filtering so that no polygon appears in both layers if you're getting confusion in identify or geoprocessing. Are the unmatched features 'null' in their join value or do they have a value that doesn't appear in the table?
– Michael Stimson
Jan 7 '15 at 3:10
1
1. Problem: if I want to control the common properties of features with a value and with a null (e.g. border colour), it has be be performed twice. This makes it much easier to forget to change one of them, or to make a slight mistake (e.g. wrong shade of grey for the outline). 2. No problems regarding confusion for geoprocessing, just the symbology: I want to symbolise the
nullfeature in the same layer. 3. Unmatched features arenullin their join value (as seen in the QGIS attribute table post-join).– Richard Law
Jan 7 '15 at 3:14
It also makes it more difficult when building a legend to include a "no data" sample, as this symbol would come from a different layer.
– Richard Law
Jan 7 '15 at 3:23
2
You're right. There is nowhere to select 'show NULL features like this' in the graduated symbol dialog, rows with NULL values are simply not shown.
– Michael Stimson
Jan 7 '15 at 3:23