opengeospatial / opengeospatial/ogcapi-processes

Need to provide the `jobs/{jobId}/outputs/{outputId}/{N}` definitions

Open
#583 0 comments 0 reactions 1 assignee View on GitHub

@pvretano is already working on this.

Since Apr 27, 2026.

Part 1 (Core)
Dominant language
AsciiDoc
Stars
63
Forks
46
Avg merge
2d 1h
Merged PRs (30d)
8

Description

The endpoint jobs/{jobId}/outputs/{outputId}/{N} is defined in OpenAPI schema: https://github.com/opengeospatial/ogcapi-processes/blob/master/openapi/paths/processes-core/pResultOutputValue.yaml

However, the requirements are not provided.
The above reference mentions

For more information, see Section 7.14.

However, this is not correct. The sc_retrieve_job_results_one pointer refers to the following endpoint, which is about retrieving "one output" (as in "only 1 {outputID} requested", not N=1 item within a given multi-value/array {outputID} result).

https://github.com/opengeospatial/ogcapi-processes/blob/4a4a1dce7b919f969b681cf96186e85ed3f5da1f/core/sections/clause_0_front_material.adoc?plain=1#L31

https://github.com/opengeospatial/ogcapi-processes/blob/4a4a1dce7b919f969b681cf96186e85ed3f5da1f/core/sections/clause_7_core.adoc?plain=1#L1423-L1426

https://github.com/opengeospatial/ogcapi-processes/blob/4a4a1dce7b919f969b681cf96186e85ed3f5da1f/core/requirements/core/REQ_job-results-success-async-one.adoc?plain=1#L1-L29

This distinction also highlights that mention like "The number of requested outputs is 1. or "N requested outputs" can be easily misinterpreted with that N array parameter (as described in https://github.com/opengeospatial/ogcapi-processes/issues/580#issuecomment-4314034921).

One or multiple dedicated /req/... definitions must be provided to clarify that distinction, and also to include it in the AST since it needs a dedicated (or additional part) operation to actually test the index-based access.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.