Why do raster band values have different values than raster statistics in QGIS?different data range of raster...
Why is my explanation wrong?
Finding integer solution to a quadratic equation in two unknowns
Is it appropriate to ask a former professor to order a library book for me through ILL?
Paper published similar to PhD thesis
Use Mercury as quenching liquid for swords?
Can I negotiate a patent idea for a raise, under French law?
What is the best index strategy or query SELECT when performing a search/lookup BETWEEN IP address (IPv4 and IPv6) ranges?
Do I need a return ticket to Canada if I'm a Japanese National?
Was it really inappropriate to write a pull request for the company I interviewed with?
Precision notation for voltmeters
Why do phishing e-mails use faked e-mail addresses instead of the real one?
What exactly is the meaning of "fine wine"?
Should I apply for my boss's promotion?
Can I frame a new window without adding jack studs?
Vector-transposing function
How does a sound wave propagate?
Why isn't P and P/poly trivially the same?
How do property taxes on school district bonds work?
Multi wire circuit or 2 separate 120V 20A dedicated circuits?
Is the differential, dp, exact or not?
What can I do if someone tampers with my SSH public key?
Did Amazon pay $0 in taxes last year?
Why does a car's steering wheel get lighter with increasing speed
Having the player face themselves after the mid-game
Why do raster band values have different values than raster statistics in QGIS?
different data range of raster file in mapserver and qgisWhy are my raster mean and standard deviation -1?Issues calculating range with QGIS 2.0 raster calculatorHow to get for a given pixel the values from different overlapped rasters?“Points To Raster Tool”- Output pixel values differ from original point valuesQGIS 2.4.0 Setting raster layer to singlebandpseudocolor using minimum and maximum raster valuesRaster statistics - incorrect and apparently arbitrary minimum valueHow to extract values from a raster using R?Redefining nodata values into zero in QGIS without changing the other values?Unreasonable Raster Statistics from NetCDF file in ArcGISExtracting data from multiple raster layers in QGIS
I am working on a raster file (1 Band).
According to the raster metadata, my minimum value is 0 and maximum is 7458. This seems to be confirmed by the Style options that return some category values in the value range mentioned above. In addition, these numbers make total sense with the nature of my data.
However, when I use the "Identify Features" tool, I get some values completely out of the range (these values look like this one generally: 4.5761380462188e-315).
I don't understand why and it's a problem because I would like sometimes to get the value of a single pixel. Do you have an idea why I have this discrepancy between the Identify Feature tool and the raster statistics?
I use QGIS 2.2.0-Valmiera on Windows 7.
qgis raster
add a comment |
I am working on a raster file (1 Band).
According to the raster metadata, my minimum value is 0 and maximum is 7458. This seems to be confirmed by the Style options that return some category values in the value range mentioned above. In addition, these numbers make total sense with the nature of my data.
However, when I use the "Identify Features" tool, I get some values completely out of the range (these values look like this one generally: 4.5761380462188e-315).
I don't understand why and it's a problem because I would like sometimes to get the value of a single pixel. Do you have an idea why I have this discrepancy between the Identify Feature tool and the raster statistics?
I use QGIS 2.2.0-Valmiera on Windows 7.
qgis raster
4.5761380462188e-315 is not out of your data range. It is a very small postive number, which is between 0 and 7458.
– bogatron
Mar 28 '14 at 20:07
Correct. I was not clear. The problem is that I know that pixel has a value around 2500. It is confirmed by the style I applied. Indeed, Qgis applies to that pixel the color I chose for the value between 2400 and 2600.
– Bap
Mar 31 '14 at 2:57
add a comment |
I am working on a raster file (1 Band).
According to the raster metadata, my minimum value is 0 and maximum is 7458. This seems to be confirmed by the Style options that return some category values in the value range mentioned above. In addition, these numbers make total sense with the nature of my data.
However, when I use the "Identify Features" tool, I get some values completely out of the range (these values look like this one generally: 4.5761380462188e-315).
I don't understand why and it's a problem because I would like sometimes to get the value of a single pixel. Do you have an idea why I have this discrepancy between the Identify Feature tool and the raster statistics?
I use QGIS 2.2.0-Valmiera on Windows 7.
qgis raster
I am working on a raster file (1 Band).
According to the raster metadata, my minimum value is 0 and maximum is 7458. This seems to be confirmed by the Style options that return some category values in the value range mentioned above. In addition, these numbers make total sense with the nature of my data.
However, when I use the "Identify Features" tool, I get some values completely out of the range (these values look like this one generally: 4.5761380462188e-315).
I don't understand why and it's a problem because I would like sometimes to get the value of a single pixel. Do you have an idea why I have this discrepancy between the Identify Feature tool and the raster statistics?
I use QGIS 2.2.0-Valmiera on Windows 7.
qgis raster
qgis raster
edited 2 mins ago
PolyGeo♦
53.6k1781243
53.6k1781243
asked Mar 28 '14 at 18:15
BapBap
3222523
3222523
4.5761380462188e-315 is not out of your data range. It is a very small postive number, which is between 0 and 7458.
– bogatron
Mar 28 '14 at 20:07
Correct. I was not clear. The problem is that I know that pixel has a value around 2500. It is confirmed by the style I applied. Indeed, Qgis applies to that pixel the color I chose for the value between 2400 and 2600.
– Bap
Mar 31 '14 at 2:57
add a comment |
4.5761380462188e-315 is not out of your data range. It is a very small postive number, which is between 0 and 7458.
– bogatron
Mar 28 '14 at 20:07
Correct. I was not clear. The problem is that I know that pixel has a value around 2500. It is confirmed by the style I applied. Indeed, Qgis applies to that pixel the color I chose for the value between 2400 and 2600.
– Bap
Mar 31 '14 at 2:57
4.5761380462188e-315 is not out of your data range. It is a very small postive number, which is between 0 and 7458.
– bogatron
Mar 28 '14 at 20:07
4.5761380462188e-315 is not out of your data range. It is a very small postive number, which is between 0 and 7458.
– bogatron
Mar 28 '14 at 20:07
Correct. I was not clear. The problem is that I know that pixel has a value around 2500. It is confirmed by the style I applied. Indeed, Qgis applies to that pixel the color I chose for the value between 2400 and 2600.
– Bap
Mar 31 '14 at 2:57
Correct. I was not clear. The problem is that I know that pixel has a value around 2500. It is confirmed by the style I applied. Indeed, Qgis applies to that pixel the color I chose for the value between 2400 and 2600.
– Bap
Mar 31 '14 at 2:57
add a comment |
1 Answer
1
active
oldest
votes
I assume that 4.5761380462188e-315 is intended as a null / no data value, so when you look at the raw data (e.g. using the Identify Features tool) you will see these values (all the nulls should have the same values). On the other hand the raster metadata is ignoring these null values, because they aren't really values...
Yes, but all the pixels seems to have that sort of very small value when I use the "Identify Features" tool.
– Bap
Mar 31 '14 at 3:01
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%2f91291%2fwhy-do-raster-band-values-have-different-values-than-raster-statistics-in-qgis%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I assume that 4.5761380462188e-315 is intended as a null / no data value, so when you look at the raw data (e.g. using the Identify Features tool) you will see these values (all the nulls should have the same values). On the other hand the raster metadata is ignoring these null values, because they aren't really values...
Yes, but all the pixels seems to have that sort of very small value when I use the "Identify Features" tool.
– Bap
Mar 31 '14 at 3:01
add a comment |
I assume that 4.5761380462188e-315 is intended as a null / no data value, so when you look at the raw data (e.g. using the Identify Features tool) you will see these values (all the nulls should have the same values). On the other hand the raster metadata is ignoring these null values, because they aren't really values...
Yes, but all the pixels seems to have that sort of very small value when I use the "Identify Features" tool.
– Bap
Mar 31 '14 at 3:01
add a comment |
I assume that 4.5761380462188e-315 is intended as a null / no data value, so when you look at the raw data (e.g. using the Identify Features tool) you will see these values (all the nulls should have the same values). On the other hand the raster metadata is ignoring these null values, because they aren't really values...
I assume that 4.5761380462188e-315 is intended as a null / no data value, so when you look at the raw data (e.g. using the Identify Features tool) you will see these values (all the nulls should have the same values). On the other hand the raster metadata is ignoring these null values, because they aren't really values...
edited Mar 28 '14 at 19:32
answered Mar 28 '14 at 18:32
nmtokennmtoken
7,98642766
7,98642766
Yes, but all the pixels seems to have that sort of very small value when I use the "Identify Features" tool.
– Bap
Mar 31 '14 at 3:01
add a comment |
Yes, but all the pixels seems to have that sort of very small value when I use the "Identify Features" tool.
– Bap
Mar 31 '14 at 3:01
Yes, but all the pixels seems to have that sort of very small value when I use the "Identify Features" tool.
– Bap
Mar 31 '14 at 3:01
Yes, but all the pixels seems to have that sort of very small value when I use the "Identify Features" tool.
– Bap
Mar 31 '14 at 3:01
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%2f91291%2fwhy-do-raster-band-values-have-different-values-than-raster-statistics-in-qgis%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
4.5761380462188e-315 is not out of your data range. It is a very small postive number, which is between 0 and 7458.
– bogatron
Mar 28 '14 at 20:07
Correct. I was not clear. The problem is that I know that pixel has a value around 2500. It is confirmed by the style I applied. Indeed, Qgis applies to that pixel the color I chose for the value between 2400 and 2600.
– Bap
Mar 31 '14 at 2:57