Open-EO / openeo.org

openeo.org landing page
https://openeo.org
Apache License 2.0
5 stars 15 forks source link

documentation: replace earthengine.openeo.org with openeo.cloud? #60

Closed soxofaan closed 2 years ago

soxofaan commented 2 years ago

some parts of the docs use earthengine.openeo.org as example back-end:

documentation/1.0/javascript/index.md
50:For this tutorial we will use the openEO instance of Google Earth Engine, which is available at `https://earthengine.openeo.org`.
56:var con = await OpenEO.connect("https://earthengine.openeo.org");
64:OpenEO.connect("https://earthengine.openeo.org").then(function(con) {
74:  var con = await OpenEO.connect("https://earthengine.openeo.org");
342:  var con = await OpenEO.connect("https://earthengine.openeo.org");

documentation/1.0/r/index.md
35:For this tutorial we will use the openEO instance of Google Earth Engine, which is available at `https://earthengine.openeo.org`.
42:gee = connect(host = "https://earthengine.openeo.org")
290:gee = connect(host = "https://earthengine.openeo.org",user = user,password = pwd,login_type = "basic")

documentation/1.0/python/index.md
28:For this tutorial we will use the openEO instance of Google Earth Engine, which is available at `https://earthengine.openeo.org`.
36:connection = openeo.connect("https://earthengine.openeo.org")
324:con = openeo.connect("https://earthengine.openeo.org")

Shouldn't we avoid GEE in docs as this is one of the lesser maintained back-ends? Replace it with openeo.cloud ?

m-mohr commented 2 years ago

No, I think it should be the one that people can easily access and experiment with. For GEE credentials are publicly available. Before you can run examples on openeo.cloud you need to go through a lengthy process. We can discuss this again once we have a simple onboarding process for openeo.cloud.

Also, the openeo.cloud examples are available similarly on docs.openeo.cloud.