Applying openEO processes for visual data exploration
Earth Observation (EO) data processing becomes accessible and powerful with Python-based openEO workflows. openEO Python allows data analysis to formulate their workflows in a familiar language and leave the data loading and workflow execution to interoperable backends.
openEO Studio adds another layer of convenience by providing a browser-based workflow development and execution environment where the openEO Python algorithm and a map to view the result are the only elements an analyst needs to deal with - no installation or execution. Log in, select your data, define the workflow, and view the result right away on a map, computed on-the-fly and only at the level of detail required.
- React JS frontend application
- Integration with third-party authentication and authorisation
- Client-side openEO Python code execution with Pyodide
- Tile-based openEO data processing titiler-openeo
The steps below will walk you through setting up the project locally.
To set up the development environment for this website, you'll need to install the following on your system:
- Node (see version in .nvmrc) (To manage multiple node versions we recommend nvm)
- pnpm Install using corepack (
corepack enable pnpm)
If you use nvm, activate the desired Node version:
nvm installInstall Node modules:
pnpm installThe application uses dot.env files with environment variables for configuration. A template file .env.example is provided as a template.
To configure the application:
- Copy
.env.exampleto.env - Modify the
.envfile with your specific configuration values - Never modify
.env.exampledirectly as it serves as documentation
pnpm devCompiles the sass files, javascript, and launches the server making the site available at http://localhost:9000/
The system will watch files and execute tasks whenever one of them changes.
The site will automatically refresh since it is bundled with livereload.
To prepare the app for deployment run:
pnpm buildor
pnpm stageThis will package the app and place all the contents in the dist directory.
The app can then be run by any web server.
When building the site for deployment provide the base url trough the VITE_BASE_URL environment variable. Omit the leading slash. (E.g. https://example.com)