opengeospatial / opengeospatial/ogcapi-processes
Retrieving inputs for a job ...
Open
@pvretano is already working on this.
Since Apr 30, 2026.
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Right now the only way to get the inputs for a job is to check the "request" member in the status info. The problem with that is that it is not mandatory and so if the job fails a client may or may not know which inputs were used to initiate the job. Perhaps we can consider making the request member required or adding a /job/{jobId}/inputs path.
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.