This Sentinel‑1 Hackathon is a collaborative event bringing together Earth Observation scientists and developers from the Digital Earth teams (among others) to explore the power of Synthetic Aperture Radar (SAR) for remote sensing mapping applications. Over the course of this two-day hackathon, participants will deepen their skills in Sentinel‑1 theory and analysis, develop practical use‑case notebooks, prototype new Sentinel‑1–derived products, and showcase the impact of adding new satellite datasets to the Digital Earth Australia/Antarctica catalogues. This is an opportunity to experiment, share knowledge, and create tangible outputs that can guide future SAR‑based applications.
A number of resources and instruction have been written to help you get started, use the TOC below to find the resource you need.
Importantly, at the bottom of this README is a table outlining potential SAR use cases, please use this table to decide which project you would like to pursue, and then use the link provided to assign yourself to a given project - a github projects board has been created to track assignments.
- Getting Started and python environment set up
- Data availability
- Contributing notebooks
- Example data loading
- External resources
- SAR use cases
If using DEA's Sandbox, no environment set up is required. Though you will need to clone this repository into your Sandbox (see below).
🚀 If you prefer, you can also launch a GitHub CodeSpace cloud instance by clicking the badge below. The session will contain all the necessary python libraries and the notebooks and code in this repo.
Tip
Allow CodeSpaces a few minutes to bootup and for all python libraries to install.
To open Jupyterlab within the default VSCode session (if you perfer that IDE), in the terminal run jupyter lab --no-browser --NotebookApp.token=''
, and jupyter lab will open in a seperate browser tab. Note, you may have to disable any pop-up blockers in your browser. Alternatively, you can configure your Github CodeSpaces settings to open Jupyterlab by default; go to Editor preferences.
Warning
When you open a Codespace, the compute time is billed to your own GitHub account (using your free monthly allowance or any paid plan you may have). Free users get 120 compute hours per month. The compute size set up for this repo is 4 cores, 16GB RAM, 15GB of storage. On a free account, this means you have 30 free hours of usage per month.
To instead use your own environment, follow the instructions below.
To access and run the iPython notebooks, you will need to clone this repository into your local computing environment, or the DEA Sandbox.
In a terminal, navigate to where you wish to keep the repository and run
git clone https://github.com/cbur24/sentinel-1-hackathon.git
If using your own computer to run the STAC API notebook, you will need a Python environment with the required packages.
You can follow the instructions in the virtual_env_instructions to set this up.
Geoscience Australia's Sentinel-1 data is published across multiple products, one for each polarisation mode used to capture the data. You can see the distribution of captured data over time and space in the DEA Dev Explorer:
Use-case notebooks developed throughout this hackathon should be pushed into the notebooks
folder within this repo. Create a folder with a simple name describing your project, and then push all notebooks, python scripts, and ancillary data into this folder. This will ensure your work does not clash with another group's project, thereby reducing the chances of git conflicts. An example has been created under notebooks/urban_classifier to demonstrate the pattern.
⚠️ Please use the DEA-notebooks-template for creating use case examples, this will ensure less work is required to tidy up and document notebooks if/when it comes time to port them into thedea-notebooks
repository.
This repository provides examples for how to load data in two ways:
- Using DE's STAC API, which can be run on any computer.
- Using DE's dev Open Data Cube, which is only available in DE's Dev Sandbox environment.
If you are not a Geoscience Australia employee, you will need to use the STAC API approach.
Links to lectures or other content explaining SAR principles.
- Alaska Satellite Facility Hackathon intro; Alex Lewandowski
- SAR 101 Hackathon Intro
- Lecture series on SAR and its applications
- SAR-Training
- NASA ARSET Introduction to Synthetic Aperture Radar (SAR) and it's applications, Part 1/3
These links direct to existing jupyter notebooks that use SAR data
- Alaskan Satellite Facility (ASF)
- Digital Earth Africa
- FrontierSI:
- ESA/Copernicus
- MS Planetary Computer
In the table below we list a number of potential SAR use cases. For the hackathon, you can assign yourself to one of these project ideas by clicking on the "assign youself" link below, which will take you to a github projects board where you can click on the corresponding card title and assign yourself within the pop-up box.
SAR data use | SAR requirements | Added value | Scientific maturity and suitability for operationalisation | Existing notebooks |
---|---|---|---|---|
Historical floodwater extent and depth | Backscatter. VV + VH. C-band. L-band will provide under-canopy inundation. | Value added via observing through clouds and potential to produce a harmonised product. A historical product will inform community preparedness and hazard modelling. | Advanced. An operational dynamic surface water extent algorithm has been developed by NASA/ASF. It is intended to apply this at a 30 m resolution globally (including Aus) to Sentinel 1 A/B scenes. Many other scientific algorithms exist for flood mapping applications. DSWx Product Suite • HydroSAR • NASA PROTEUS • Opera DSWX-SAR |
HYDRO30_Stack_Processing |
Ground Displacement - Ground water - Earthquakes - Volcanic activity - Landslides - Mine displacement |
InSAR, pixel offset tracking | Not hazards DEA has immediate interests in investigating. Geodesy team is piloting continental-scale ground line-of-sight displacement. The Community Safety Branch would be interested in earthquake impact tools and possibly landslides. | Advanced. Often requires scientific oversight. In the future the NISAR displacement product could be rolled out over Australia. DISP Product Suite |
|
Coastal erosion / shoreline extraction | Geo-located backscatter. HH is likely the best, and X-Band > L-Band > C-Band for detectability. C-band won’t detect inundation below canopies well. | Different overpass times allow observation of different tides vs optical. Combines sources to increase temporal resolution for models. Improved mapping in cloudy areas. Potential for tidal inundation detection under mangroves. Could remove tidal coverage bias in monsoon cloud areas. | Developed. Algorithms exist but need QC for speckle, rough seas, bright coastal targets. Validation with Landsat/Sentinel-2 needed. Problems may occur at low tide. Sub-aperture interferometric processing may detect waves and delineate shorelines. Wave conditions limits apply. Sentinel-1 algorithms • Coastline extraction L-band • Observation geometry L- & X-band |
|
Vegetation mapping and Land-Cover | Dual-pol or quad-pol backscatter. C-band and L-band. InSAR (coherence) | SAR can determine woody from non-woody vegetation via double-bounce scattering. Coherence improves classification accuracy. | Developed. Proof-of-concepts in QLD show biomass-SAR relationships. More work needed for integration into classifiers. Multi-sensor classifier • Structural classification • Crop mapping |
ASF OpenSARlab Ecosystems Notebooks |
Forest Stand Height | InSAR (interferometry) | Provides age/history of forest, habitat info, biomass monitoring. Estimated by combining repeat-pass InSAR with DEM. | Developed. Applied to large-scale mosaics. Forest height mapping |
|
Flood mapping and wetlands | Single-pol (HH) backscatter. C- and L-band. InSAR (coherence, interferometry) | Real-time mapping done by Community Safety Branch (ICEYE). Longer-term DEA monitoring possible. SAR backscatter can separate water and land; coherence helps map wetland vegetation. L-band penetrates canopy. | Developed. Used RADARSAT-2 for flood/wetland mapping. Challenges include coherence loss and atmospheric phase delay. Review paper |
ASF OpenSARlab Ecosystems Notebooks |
Urban cover | Dual-pol or quad-pol backscatter. C-band and L-band | Improves distinction between urban and bare land vs optical alone. Structural insights from polarimetry. | Developed. Many proofs-of-concept and global mapping efforts. SAR+Optical mapping • Sentinel-1+2 workflow • OpenSARUrban dataset |
DEA Africa Notebook |
Coastal habitat separation | Backscatter, all polarisations C- and L-band. InSAR/Top-of-canopy DEM | Potential to distinguish saltmarsh, mangrove, supratidal habitats based on canopy height and backscatter. | Experimental. No established algorithm; NISAR quad-pol may help. Fusion with optical enhances results. Mangrove polarimetry • Inundated vegetation classification |
|
Historical burn area mapping | Backscatter, VV + VH. C-band. L-band can observe under-canopy fires. | Detects burns under canopy, through clouds/smoke. Informs preparedness and hazard modelling. | Experimental. Difficult to map accurately at large scales; requires ML and change detection tuned to vegetation/landscape type. Burn area mapping |
|
Crop classification and yields | Dual-pol or quad-pol backscatter + coherence. Time series/change detection. C-band | Could enhance DEA land-cover agriculture information. | Experimental. Successful in Wales (Sentinel-1) but coverage higher than Australia’s. Living Wales approach |
ASF Agriculture Mapping with SAR Using CoV |
Soil Moisture | Backscatter and emissivity | No known DEA value add. | Operational product exists — ESA CCI daily active+passive SAR soil moisture product. ESA CCI Soil Moisture |
|
Ice shelf front, ice calving events and iceberg tracking | Backscatter HH + HV | Cloud free and winter observations. | Advanced. An existing IceLines product exists. An events-based database and iceberg tracking could be built from this dataset. IceLines • Iceberg Detection • Iceberg Tracking |
|
Ice Crevasse detection | Backscatter HH | Can detect crevasses that may be hidden in optical imagery. | Advanced. Some limitations exist due to SAR image quality, observation geometry and terrain. Continental-scale algorithm |
|
Snow classification (dry/wet/permafrost) and melting | Backscatter, polarimetry | High resolution meltwater dynamics and freezing/thawing dynamics. | Advanced. Snow classification • Melt detection • Melting algorithm |
|
High-resolution sea-ice concentration and extent | Backscatter – all polarisations | Cloud-free, over winter high resolution sea-ice can provide more detailed observations that will benefit ocean modellers and Antarctic researchers. Information on types of sea-ice may also be distinguished. | Developed. Most sea-ice concentration algorithms have been developed using CNN or U-net. Cross-pol images can help classify types of sea-ice. Collaboration with sea-ice group would be required to produce an operational product. Denmark Antarctic Product • Baltic product • Sentinel-1 CNN |
|
Meltwater and supra-glacial lakes | InSAR, coherence, backscatter HH, VH | High-resolution data. Cloud-free and observations over winter. | Developed. PhD work ongoing at IMAS on supra-glacial lake collapse detection. InSAR more common in literature but harder to operationalise. Review • S1+L8 method • S1 neural network |
|
Fast-ice extent | InSAR, coherence, offset tracking backscatter HH, VH | Cloud-free and observations over winter. | Experimental. ARC Future Fellowship developing operational algorithm. InSAR fast-ice • Fast-ice monitoring • Displacement tracking |
|
Grounding line | InSAR | High-coverage repeat-pass motion detection to monitor change. | Experimental. Algorithm appears robust but dependent on observation geometry. Grounding line extraction |
|
Ice velocity and basal melt | Backscatter offset tracking, InSAR, Multi-temporal DEM | Regional, high-quality InSAR products could provide additional value to existing products, in slow moving areas. | Operational product exists. ITS_LIVE provides continental-scale elevation change and ice velocity from offset tracking. InSAR robustness depends on observation/flow geometry; only valuable in slow areas <50 m/yr. Multiple Aperture InSAR may allow fast glacier measurement. ITS_LIVE • Ascending/Descending InSAR |