Skip to content
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

ndvi_planetscope notebook unexpected NDVI values #66

Closed
craigdsouza opened this issue Nov 12, 2018 · 4 comments
Closed

ndvi_planetscope notebook unexpected NDVI values #66

craigdsouza opened this issue Nov 12, 2018 · 4 comments

Comments

@craigdsouza
Copy link

not sure this is the right place, but I have a query regarding one of the notebooks , 'ndvi_planetscope'
I ran the notebook for a scene I was interested in,
Scene id: '20181002_045628_0f1a'
item_type = 'PSScene4Band'
asset_type = 'analytic_sr'
everything runs ok, however the resulting NDVI I get is completely unexpected, largely in the range of 0.6-0.8 A Sentinel 2 image (TOA not SR) for the same date shows NDVI values, much smaller. Any idea what the issue might be? or if there is one

@jreiberkyle
Copy link
Contributor

To compare apples to apples, I suggest comparing TOA to TOA. For that, you can look at the 'analytic' asset_type. Do the resulting NDVI's match up?

@craigdsouza
Copy link
Author

so i looked at TOA(reflectance & radiance) instead , the discrepancy is still there, but in this case NDVI is being underestimated vis-a-vis Sentinel. I'm attaching histograms and thumbnail images for reference.

While I understand the histograms for the two images won't match exactly, what I don't get is why NDVI over built up land and even river water is being overestimated to such a large degree upto values of 0.1-0.2 which is definitely unexpected.
However note, the raw radiance image does show expected values over built up areas but here the histogram is skewed far left of the Sentinel histogram. Besides S2 is a reflectance image, not radiance so the two aren't comparable.

1. TOA Planet Scope Reflectance Image 2nd Oct 2018

toa_reflectance-ndvi-histogram
toa-reflectance-ndvi

2. TOA Planet Scope Radiance Image 2nd Oct 2018

toa-radiance-ndvi-histogram
toa-radiance-ndvi-fig

3. TOA Sentinel 2 Image 29 Sep 2018

s2-ndvi-hist
s2-ndvi-fig

3. SR Planet Scope Image 2nd Oct 2018

sr-ndvi-histogram
sr-ndvi-fig

@craigdsouza
Copy link
Author

Hey,
any thoughts here?

Best
Craig

@jreiberkyle
Copy link
Contributor

Hey Craig,

Sorry for the delay over the holidays. So first of all, what comes into mind is the fact that NDVI indices are really best used for comparison within a sensor type. This is primarily because the spectral bands differ between sensors (e.g. the 'red' band is actually measuring different wavelengths). This is true for Landsat, Sentinel, and most sensors. Within a sensor 'family', such as Landsat, the design is such that those differences are minimized as much as possible. Planetscope sensors have a different spectral response than Sentinel, so I would expect NDVI to be different regardless of the target (water, vegetation, built-up areas). It is possible to minimize these differences by 'calibrating' the NDVI values using known targets, but that requires care to avoid introducing errors.

A good starting point is the description of the spectral response of the PlanetScope sensors, given here (click the link to Download Full Specs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants