Timeline for Export all pixel NDVI values from a region using Earth Engine
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 16, 2022 at 14:47 | comment | added | kwgeo | Your geometry region is a vector polygon so it has no native scale in terms of pixels/meter. You must decide for yourself what the appropriate scale would be for retrieving NDVI values from the image. In this case as I had mentioned, using a scale higher than 10m/px (say 5m/px as you had done originally), gives you no more information because the Sentinel2 data you are creating the NDVI image from is natively created at 10m/px. | |
| Dec 16, 2022 at 14:47 | comment | added | kwgeo | I'm not sure I've explained the scale/pyramiding concept well enough. Depending on what scale you are zoomed in at, the number of lines and columns in the image changes because Earth Engine is dynamically changing the resolution of the image. | |
| Dec 16, 2022 at 12:19 | comment | added | D3usM4tos | The reason to use sample() is to get a FeatureCollection by a image, so the export() function works. Is there another way to do this rather than sample()? | |
| Dec 16, 2022 at 12:19 | comment | added | D3usM4tos | Great. I could change the scale and the number of values changed. But I'm trying to understand the correct relation to set in scale parameter. For instance, the geometry region in this case has 351x452 pixels but I can't get 158.652 (351x452) ndvi values. | |
| Dec 16, 2022 at 0:40 | vote | accept | D3usM4tos | ||
| S Dec 15, 2022 at 22:09 | review | First answers | |||
| Dec 15, 2022 at 22:12 | |||||
| S Dec 15, 2022 at 22:09 | history | answered | kwgeo | CC BY-SA 4.0 |