I hope I’m not off-topic, but I could really use some help as I’ve hit a wall. I’m not an expert in satellite systems or data analysis; I specialize in server-side logic development.
Our team has a task at hand: to create a monitoring system for identifying hazardous breakthroughs in mountainous water bodies. This involves aggregating data from various sources(local equipment, meteorological information), including satellite systems. The goal is to enable decision-making to prevent flooding when these water bodies pose a threat.
We have geodata for over 200 water bodies (areas of interest). We need to gather information about the surface area of these water bodies weekly. I’ve gathered that we can utilize NDWI and then compute the area based on this data.
Here are the specific queries I have:
Where should we start to obtain satellite data, and which APIs can we use for this purpose?
How can we acquire terrain images?
Is it possible to obtain graphical data about the water body surface?
Obtaining data on the surface area of water bodies (Is this feasible, or will we need to compute these figures ourselves?)
Generating a temporal animation of the terrain over a specified time period (GIF)
Currently our specialists use Google Earth Engine, now we need make a automated dashboard to more effective work.
Can openeo facilitate all these tasks is there ready-made solutions? If so, what avenues could we explore to achieve this?
Currently, we’re using nodejs, but we’re open to switching to Python if certain functionalities are exclusively available in Python.
There are so many sources available that I’ve become quite overwhelmed and unsure of which direction to proceed in next.
I would greatly appreciate any guidance or assistance you can offer, and sorry if i’m off topic.
your use case can indeed be supported fully by openEO.
Many of the questions are indeed answered in our documentation, but I’ll try to give a more concrete pointer: the ESA worldwater toolbox is an open source algorithm on top of openEO that classifies water pixels in any AOI, you can find it here:
At the end of the toolbox, it creates a binary classification. OpenEO also allows you to convert this to vector data if needed, for instance to compute surface area, or you could simply count the number of water pixels in your AOI.
There’s also other examples, like this one:
But these were built as project use cases rather than operational services, so be aware that I mostly post them as an example of working with openEO.
I hope this already helps, and that these examples allow you to get an idea of the capabilities. Feel free to ask more specific questions, or to contact the orginal authors of the notebooks for thematic questions.