Links to #14

Check if plumber and R natively (and it HTTP server) supports charset UTF-8 for all requests and responses.
Please, provide some references.

Links to #14

Implement API function to support CORS.
See implementation in OpenSTAC's example.

Pre-defined Processes

Links to #7

Functionality Description

• GET /processes:

  • Valid response with at least processes and links as arrays
  • Works without authentication
  • Works with authentication
  • All processes are returned if no limit parameter is provided

• GET /processes > processes:

  • Missing properties in the process objects are not set to null if not valid according to the OpenAPI schema

File Formats

Links to #7

Functionality Description

• GET /file_formats:

  • Valid response with input and output properties
  • Works without authentication
  • Works with authentication

• GET /file_formats > output:

  • At least one output file format available

• GET /file_formats:

  • File format names get accepted case Insensitive
  • Each format has at least gis_data_types and parameters

Collections

Links to #7

Functionality Description

• GET /collections:

  • Valid response with at least collections and links as arrays
  • Works without authentication
  • Works with authentication
  • Supports a valid STAC version (0.9.0 or later, preferably 1.0.0)
  • All collections are returned if no limit parameter is provided
  • All collections are valid according to the STAC specification 0.9 or later (stac_version, id, description, license, extent, and links are required)
  • Missing properties in the collection objects are not set to null if not valid according to the OpenAPI schema

• GET /collections/{id}:

  • Is supported
  • Response is valid according to the STAC specification 0.9 or later (additionally, cube:dimensions and summaries are required)
  • Works without authentication
  • Works with authentication
  • All collections provide their actual data cube dimensions

API fundamentals

Links to #7

Functionality Description

1. All > CORS:

   • OPTIONS method with all headers
   • Access-Control-Allow-Origin for GET, POST, PUT, PATCH, DELETE
   • Access-Control-Expose-Headers for GET, POST, PUT, PATCH, DELETE

2. All > HTTPS:

   • HTTPS supported

3. All > UTF-8:

   • Charset is UTF-8 for all requests and responses

4. All > Error Handling:

   • Returns HTTP status codes between 400 and 599 for errors
   • Returns a JSON object with at least code and message properties

5. All > Process Graphs:

   • Callback support

Data Processing

Links to #7

Functionality Description

• status:

  • Job follows described status changes (see description of status property in GET /jobs/{id})

• At least one of batch jobs, secondary web services or synchronous processing is implemented

Provide in inst/ folder the plumber.R file defining the endpoints and calling openeocraft functions. openeocraft doesn't need to depends on plumber.

Well-known Discovery

Links to #7

Functionality Description

• GET /.well-known/openeo:
  • Valid response with at least url and api_version per instance (without authentication)

If there are more than one tile, mosaic them before send the result.
For multiple CRS user could provide a global CRS like 'OGR:WGS84'.
The CRS could be optionality passed as parameter to this function.

Links to #14

Implement API error handling.
Please, see implementation in OpenSTAC.

First draft set up.

Use Bearer base process.

Links to #20

Improve collection definitions:

• Include ranges (temporal and spatial)
• Improve some fields (e.g. description)

Links to #21, #18

Implement api_jobs() function to support /jobs endpoint.
Please, see OpenEO documentation on jobs endpoint.

How to select values from a stars object using dimensions.

stars_obj --> array_element() --> stars_obj

array_element() can receive index or labels, where labels selects some band.

https://openeo.org/documentation/1.0/developers/profiles/api.html#l1-minimal

• API fundamentals
• Well-known Discovery
• Capabilities
• File Formats
• Authentication
• Pre-defined Processes
• Collections
• Data Processing

Capabilities

Links to #7

Functionality Description

• GET /:

  • Valid response with at least api/backend/stac_version, id, title, description, endpoints and links (w/o auth)

• GET / > endpoints:

  • All implemented endpoints listed with methods

• GET / > endpoints:

  • No endpoints listed that are not implemented or faulty

• GET / > api_version:

  • Implements openEO API version 1.2.0 (or 1.1.0)

• GET / > stac_version:

  • Implements STAC version 1.0.0 (or 0.9.0)

Authentication

Links to #7

Functionality Description

• #31

• All that require a Bearer token > Error Handling:

  • Returns HTTP status codes 401 if no authentication details are provided
  • Returns HTTP status codes 403 if invalid credentials or credentials with insufficient permissions are provided

• GET /credentials/*:

  • At least one authentication method is supported (HTTP Basic or OIDC)