Sentinel1 composites - bands and properties

[karelvancamp]

Sentinel 1 images reductions/composites are best done using consistent selections of image properties. Current def does not allow to separate ascending and descending orbits. This causes loss of visuals clues s.a. elevation when these are reduced together.

For example: https://code.earthengine.google.com/?scriptPath=users%2Fkarelvancamp%2Ftutorials%3ACOPERNICUS_S1_GRD_properties

The problem is mentioned here https://developers.google.com/earth-engine/guides/sentinel1

Possible solution could be to also allow [dict] input for bands rather than [str]. Dict could contain property filters desidred. When using [str], fall back to safe defaults. (IW, ascending)

Then reduce them seperatly. Then join again. Should be feasible.

Minimalistic approach is to add some input parameters for filtering same properties entire collection.

ps: if using dict approach, I would consider adding support for selecting expressions instead of bands. This enables RGB mappings.
Was looking into making Pauli color coded Sentinel1_legacy_timelapse()

[giswqs]

Thank you for the suggestions. Could you submit a PR? The result I changed the function is make all timelapse functions use the create_timelapse() functions under the hood. Different sensors can have different methods for compositing and creating image collections. Once an image collection is constructed, the create_timelapse function can be used to create timelapse.

[karelvancamp]

make all timelapse

I really liked the refactor.

Only understood figured bands availability & some nuances today. [HH-HV] mostly artic and the lakes. [VV-VH] on land. Rarerly all 4. So not needed to reduce seperatly (as you can't combine) as i suggested above.

Once image collection is constructed

Ah i see, I should be able to extract imgcoll parsing inside sentinel1_timeseries and apply before calling create_timelapse.

pr
Will see if i can find time. On holidays 1e-11e.