Repository files navigation

openEO back-end driver forGoogle Earth Engine.

This back-end implementsopenEO API version 1.2.0.

If you are interested in using openEO together with Google Earth Engine,express your interest with the Google Earth Engine Team, please.

The demo instance is running athttps://earthengine.openeo.org

To log in, you can use your Google Account to authenticate as long as it's signed up for Google Earth Engine.As a non-commercial user, you canregister for Google Earth Engine for free.

If you are unable to register for Google Earth Engine, we can also provide a demo account.Please contactopeneo.psc@uni-muenster.de.

The driver is written innode.js and requires at least version 20.0.0.Install node.js and npm according to the official documentation of each software package.

Afterwards either download the files in this repository or clone it. Runnpm install to install the dependencies

There are several important configuration options in the fileconfig.json:

• hostname: The address of the server running the openEO GEE driver. For local deployments usually127.0.0.1, for public instances the ip or domain name of the server, e.g.earthengine.openeo.org.
• port: The port the HTTP instance of the openEO GEE driver is running on.
• ssl: Configuration to enable HTTPS (secured HTTP with SSL).
  • port: The port the HTTPS (secured) instance of the openEO GEE driver is running on.
  • key: If you want to create an HTTPS server, pass in a private key. Otherwise set tonull.
  • certificate: If you want to create an HTTPS server, pass in a PEM-encoded certificate. Otherwise set tonull.

Generally, information about authentication with Google Earth Engine can be found in theEarth Engine documentation.

If you want to run all processing through a single account you can use service accounts. That's the most reliable way right now.The server needs to authenticate with aservice accounts using a private key. The account need to have access rights for earth engine. You need to drop your private key file into a secure place specify the file path of the private key in the propertyserviceAccountCredentialsFile in the fileconfig.json.

Alternatively, you can configure the driver to let users authenticatie with their User Accounts via OAuth2 / OpenID Connect.For this you need to configure the propertygoogleAuthClients in the fileconfig.json.

You want to have at least client IDs for "Web Application" from theGoogle Cloud Console.

For example:

[  {"id":"1234567890-abcdefghijklmnop.apps.googleusercontent.com","grant_types": ["implicit"    ],"redirect_urls": ["https://editor.openeo.org/","http://localhost/"    ]  }]

After configuration, the server can be started. Runnpm run up to start the server.

After finishing work, you can stop the server by runningnpm run down.

To manage the user accounts that are not authenticting through their Google Accounts:

• Add a new user:npm run adduser
• Delete a user:npm run deluser
• List all users:npm run users

For both the demo servers or your own instance you can use theopenEO API to communicate with Google Earth Engine.

There are various clients for the openEO API, e.g.

• Web Editor
• Python
• R
• JavaScript
• Julia

There are various process graph examples in the following folder:examples

Other known issues:

• Ideally, all computations - including the datacube management - run on GEE's side.Currently, some smaller checks still run in the proxy implementation due to the issue that we can't easily abort execution on GEE in case we identify anomalies or other issues.