opengeospatial / opengeospatial/ogcapi-processes
Content Negotiation for sub-output results
@pvretano is already working on this.
Since Mar 16, 2026.
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
referenced in https://github.com/Unidata/netcdf/issues/42#issuecomment-3923360842
When a process is submitted for execution with a content negotiation (or auto-resolved it by N>1 outputs requested) to results.yaml structure, the per-output format: {mediaType: ...}} can be provided to request their specific content-negotiation.
https://github.com/opengeospatial/ogcapi-processes/blob/a1c3cd36baaeb90c68d3cb5561f7dddd8f635187/openapi/schemas/processes-core/output.yaml#L1-L4
https://github.com/opengeospatial/ogcapi-processes/blob/a1c3cd36baaeb90c68d3cb5561f7dddd8f635187/openapi/schemas/processes-core/format.yaml#L1-L11
However, certain media-types might require additional profile negotiation, such as distinguishing a profile=cloud-optimized or a profile=netcdf3/4. In cases like profile=cloud-optimized, they are already included in mediaType by definition, but other media-types might not officially integrate this parameter.
Therefore, it might be worth indicating a "profile" parameter along the "mediaType" within the "format".
Multiple profile URI/Safe-CURIE can be provided. Therefore, profile in the I/O definition would be an array.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.