-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
outputTransmission and jobControlOptions not clearly explained #326
Comments
@m-mohr I think these are gone in the next version but ...
NOTE: When I say "value" here I mean the results of processing. That could be a GeoTIFF ... for example. As I said, both these parameters are gone in the next version replaced instead with the Prefer HTTP header (and accompanying parameter). |
@m-mohr @pvretano Although The It would be good if we could link to an auto-generated draft of Processes - Part 1: Core 2.0. |
Indeed. They are not gone completely (nor should be), but rather replaced by the |
21-AUG-2023: |
I'm pretty much reading OGC API Processes - Part 1 for the first time in detail.
I found
outputTransmission
andjobControlOptions
in the specification accompanied by a schema.Unfortuantely, it is not clearly explained what these fields what they are for (or I missed it).
Also it seems the enum values defined in the JSON Schema are not explained.
The text was updated successfully, but these errors were encountered: