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

Query Regarding Shoreline Analysis and Image Extraction Compatibility with SAET #2

Open
Qikewen69 opened this issue Dec 20, 2023 · 4 comments

Comments

@Qikewen69
Copy link

Dear developer,

I would like to analyze shorelines along my Area of Interest (AOI) spanning the past 20 years. However, I have observed that I am unable to acquire satellite images predating the launch of Sentinel-2 and Landsat. Consequently, I need to obtain satellite images from alternative sources for the period 10 years ago. Could you please confirm whether this SAET allows users to extract shorelines from images obtained from sources other than Sentinel-2 and Landsat?

image
@jpalomav
Copy link
Owner

jpalomav commented Dec 20, 2023 via email

@Qikewen69
Copy link
Author

Thank you for your prompt response and clarification regarding the satellite sources currently supported by SAET. I appreciate the detailed information provided.

I noticed that Landsat 7 images, despite not being officially supported, seem to work when downloaded and placed in the "data" folder. The SAET successfully generated shorelines from these older Landsat 7 images. Can you confirm if SAET is indeed compatible with Landsat 7? If so, are there any specific considerations or limitations I should be aware of?

Thanks for your assistance.
image

@jpalomav
Copy link
Owner

Hi.
Thanks for your interest. In this case , if SAET has been able to extract the shoreline, probably the result is not correct (or not so correct as we will expect). SAET works with water indexes (AWEInsh, AWEish and MNDWI). These indexes combine some bands to emphasize the difference between water and non water surface. Mayority of these water indexes use Green, blue, NIR, SWIR1 and SWIR2 bands. The problem is that there is no correspondence for these bands in all satellites. For example, SWIR1 (short-infrared) band for Landsat 8-9 is the band B6 but for Landsat 7 and 5, this is the band B5. So , the mathematical equation for one water index is taken onto account different bands for L8-9 and L5-7, and the water index result wont't be correct. If you dive into the script "sp_processing_functios.py", in the line 2484 there is a function called "aweinshLandsat" where you can see the expression to compute the AWEInsh water index. For L8-9 the suitable bands are: green(B3), nir(B5), SWIR1(B6) and SWIR2(B7). For L5-7 this expression should be: green(B2), nir(B4), SWIR1(B5) and SWIR2(B7).

Other point is that L7 satellite had a problem on 2011 and from this year L7 images present a "gap" effect (SLC-off data). So these images must be processed taken this fact into account.

We know the importance to be able to analyze coastal sectors from ahistorical point of view and take advantage of all image resources. So we are thinkig of include L5 and L7 in the SAET workflow, but it won't be inmediatly, may be in the next months.

In any case, we will announce it through this website.

Best regards,

SAET team.

@Qikewen69
Copy link
Author

Thank you for the clarification. I appreciate your efforts and look forward to potential updates. Your commitment to enhancing SAET is commendable.

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