v0.6

This release contains minor improvements regarding openEO API v1.0 compatibility as well as a few UI improvements and bug fixes. The interface now aligns with the layout of the general openEO website and is more suitable for non-tech-savvy people. The biggest new feature is that the Hub now also crawls and displays UDF runtimes. It is now enforced that all backends must support HTTPS. The crawling has become a bit more resilient against bad input from backends.

v0.5

The Discovery section of the Hub now supports openEO API v1.0-rc.2. Most changes were under the hood, but there are also new features: Users can now explore information like input file formats, links about the backend or the production-readiness flag.

In return, support for crawling backends that work with the outdated openEO API v0.3.x was dropped. Backends running on v0.4.x are still supported.

The Exchange section is not yet openEO API v1.0-ready and was thus temporarily removed -- it needs substantial improvements anyway. This work is on the roadmap for the Hub's v0.7 release.

It is now expected that all service providers implement well-known discovery -- in fact, a backend can only be crawled when it is indexed in a well-known document (and will be removed from the Hub once it's no longer indexed in that document). The permitted structure of the config.json was adapted accordingly, which may be a breaking change for old configuration files!

Besides, this release makes the server and the various scripts more robust by implementing better error handling. Additionally, the crawl script now features more accurate and understandable reporting, generally cleaner code, and some fixes for more successful crawls (SSL bug, longer timeout). Also, changes in other openeo-* repositories were factored into the Hub (common components etc.)

Note: Because names of database indices changed, the old indices must be dropped from the database before crawling again.

v0.4

The Discover section now provides a sidebar with filters, which allow the user to narrow down the list of backends by various criteria. This new feature replaces the old Search section - they provide almost the same functionality, but the filters are a lot nicer.

The Hub now officially boasts its own API, compatible with openEO API v0.4.2 where applicable, including a capabilities document and correct CORS headers. The endpoints are situated under /api/* (instead of the previous /* (which was never official though)). Documentation can be found in the Readme.

Further work was done on the crawl script and the process graph exchange.

This is the last version that will support openEO API v0.3 (according to current plans).

v0.3

The Hub now fully supports openEO API version 0.4! Support for this was added to the backend API and the frontend rendering. The frontend received another big change: Backends can now be grouped by their provider -- different versions of "the same" backend will appear in separate tabs under the same top-level heading. Also, lazy-loading was improved, and the main Vue component was refactored to achieve a clearer hierarchy.

v0.2.2

The crawler now supports backends that run openEO API v0.4. Additionally, backend URLs can now be supplied in the /.well-known/openeo format. The most notable frontend change is that the backends are now sorted. Other than that, there were just a few updates and fixes.

v0.2.1

Most changes were under the hood: Refactoring of the server code and refactoring of where the frontend components are imported from (using the new common openeo-vue-components repository). Other than that, changes notable to the user include that the UI became clearer/neater/tidier, now features lazy loading, and provides connectivity to the openEO Web Editor.

v0.2

Presentation of data on the frontend was improved significantly. The "Discover" and "Exchange" (and "About") areas were added - for this, both frontend UI and backend API were greatly amended. Additionally, the existing backend API changed too, causing breaking changes. This results in a version that provides some (by far not all) major features, but does so still on an "alpha" maturity level.

v0.1

Allows crawling of strictly openEO API spec compliant backends into a local database. Once that is completed, the user can search for backends, collections and processes using a web interface. This web interface requires some knowledge of the openEO API.

This is a very early version, so please note that error handling is at a minimum.