Crosswalk between openEO API and OCG API - Processes#494
Crosswalk between openEO API and OCG API - Processes#494
Conversation
m-mohr
force-pushed
the
ogcapi-processes
branch
3 times, most recently
from
a9fbc3e to
a645bae
Compare
|
Maybe important to mention that openEO also defines the actual processes? I know this is not part of the api strictly speaking, but it is the key difference. The other one probably being how processes graphs can be chained and nested. |
|
@jdries The process chaining is mentioned in the Process Discovery chapter, but I made it a bit more explicit now. I also added a reference to the pre-defined processes in the same chapter. And there's now a "tl;dr" at the beginnning. |
| - The relation type to link to the conformance classes is `conformance` in openEO (originating from | ||
| OGC API - Features / STAC API) and `http://www.opengis.net/def/rel/ogc/1.0/conformance` in OAP1. | ||
| Two links with the same target but different relation types will be required. | ||
| - The existance of API endpoints in openEO is primarily checked through `endpoints`, which is |
|
I suggest to raise the point about 'data access' to the level of key differentiators. |
2 participants
This document gives a brief overview over the similarities and differences between