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

Use gamma-0 backscatter convention for RTC output #39

Closed
maawoo opened this issue Aug 25, 2022 · 2 comments
Closed

Use gamma-0 backscatter convention for RTC output #39

maawoo opened this issue Aug 25, 2022 · 2 comments

Comments

@maawoo
Copy link

maawoo commented Aug 25, 2022

Hi all,
I was wondering why you chose to stick to the beta-0 backscatter convention instead of gamma-0 for the RTC output?
Isn't the entire point of applying David Small's RTC algorithm [1] to get a terrain-flattened, gamma-0 normalized backscatter product? Furthermore, you might have heard of the CEOS CARD4L Normalised Radar Backscatter specification [2], which also endorses the gamma-0 backscatter convention.

Great software and I'm looking forward to hearing from you!

[1] https://doi.org/10.1109/tgrs.2011.2120616
[2] https://ceos.org/ard/files/PFS/NRB/v5.5/CARD4L-PFS_NRB_v5.5.pdf

@alexamici
Copy link
Member

@maawoo I must admit I don't understand what you mean with:

beta-0 backscatter convention

Do you refer only to the attributes (that I agree are wrong, we forgot about them)? Or do you mean that the values need to have a different normalisation?

@maawoo
Copy link
Author

maawoo commented Aug 29, 2022

Hi @alexamici,
thanks for your quick reply! Table 1 in Small (2011) gives a good overview of backscatter normalization conventions and how they're calculated:
Small2011_table1

So you're indicating that the values of output rasters created with sarsen rtc are correctly normalized to gamma nought, while their attributes wrongly refer to beta nought?

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