Open aapopescu opened 7 months ago
Currently the first draft of sen4ama Amazonas integration is on https://eodash-trilateral-testing.eox.at/amazonas-sen4ama/ The visualisation seems fine and working to me but maybe we could also show the origina Snetinel1 data that it was based on? Up to decide. In that case evalscript color would need to be changed from grayscale to some other color to contrast with S1 better.
Please have a look @AlessandroScremin @aapopescu and suggest if leaving like this is OK or we should reference other layers as well.
[x] @santilland check if we can do requests from monthly steps if SH can handle the response.
[x] The data seems to be as expected when comparing to original.
[x] S1 display not needed for now, set S2 cloudless as default backgorund.
[X] @AlessandroScremin to change color to red
@santilland color changed to RED.
- [x] @santilland check if we can do requests from monthly steps if SH can handle the response.
- [x] The data seems to be as expected when comparing to original.
- [x] S1 display not needed for now, set S2 cloudless as default backgorund.
- [x] @AlessandroScremin to change color to red
All integrated.
@AlessandroScremin Are there any updates on the markdown description for Sen4Ama data?
markdown is ready
Thank you. Prepared https://github.com/eurodatacube/eodash/pull/2505 to staging and created STAC catalog reference YAML and copied assets. Closing the issue as done.
@aapopescu PR merged to staging.
An attempt for a standard custom area chart integration is now in a branch here: https://eodash-trilateral-testing.eox.at/amazonas-sen4ama-chart/?indicator=sen4ama
Nevermind, with @santilland we agreed on an approach of time series of "detections pixels vs nodata pixels". I will redo the chart interpretation. Reopening the issue
@lubojr
I was looking at the chart...but it doesn't seems much useful with all values set to 1.
The map is a binary mask no data value = 0) and 1. the idea was to compute the bumber of pixels with value 1 in the custom AOI and compute the area knowing the resolution of the pixel and the number of pixels
what I see in the dashboard is this:
Nevermind, with @santilland we agreed on an approach of time series of "detections pixels vs nodata pixels". I will redo the chart interpretation. Reopening the issue
@AlessandroScremin Yes. In the last comment I confirm that the current implementation is not final. We will change it in the nearby future (using the same principle as for WSF dataset)
https://sen4ama.gisat.cz/
https://github.com/gisat/s14amazonas
contact: https://github.com/sivasanarul
@AlessandroScremin cc: @dmoglioni
-> to be included in trilateral dashboard