GEP supports the development, packaging, deployment, and execution of Earth Observation processing workflows for geohazard applications.
Users can build algorithms, prepare processing chains, configure inputs, run services on EO datasets, and generate outputs that can support monitoring, event response, research, or operational use.
What you can do
Processing workflows in GEP can be used to:
- Run existing GEP processing services
- Configure workflows for a specific area of interest
- Process Sentinel-1, Sentinel-2, Sentinel-3, and supporting datasets
- Generate geohazard information products
- Package algorithms for repeatable execution
- Test and validate new processing methods
- Support systematic or on-demand processing
- Prepare outputs for publication, analysis, or thematic applications
From algorithm to service
A processing workflow can start as an analysis script, notebook, or algorithm prototype.
Once the method becomes repeatable, it can be packaged and deployed so that it can be executed as a service on GEP.
Typical steps include:
- Define the input datasets and parameters
- Prepare the processing logic
- Package the workflow for reproducible execution
- Test the service with representative datasets
- Run the workflow over selected areas and time periods
- Review and validate the generated outputs
- Share results through GEP topics, workspaces, or thematic applications
Typical use cases
You may develop or run processing workflows when you need to:
- Generate displacement maps from Sentinel-1 data
- Run SAR coherence or backscatter change detection
- Produce burned area severity maps from optical datasets
- Create terrain motion products over a region
- Support event response after earthquakes, landslides, or volcanic activity
- Automate recurrent processing for monitoring activities
- Test new algorithms for geohazard analysis
- Prepare a service for wider use by a project or stakeholder community
Operational and systematic processing
Some workflows are executed on demand for a specific user request, area, or event.
Others can support more systematic activities, such as:
- Regular monitoring over predefined areas
- Recurrent product generation
- Large-scale processing campaigns
- Project-specific production workflows
- Thematic application updates
- Stakeholder-driven operational services
This makes processing workflows useful both for research experimentation and for more operational geohazard services.
Where to go next
Visit the Welcome Page to check the entry point for Earth Observation services, tools, thematic applications, support, and collaboration dedicated to geohazard monitoring, analysis, and response.
For access, service activation, subscriptions, or institutional enquiries, contact: