Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Part 4: job type - enum or not #447

Closed
m-mohr opened this issue Oct 19, 2024 · 0 comments
Closed

Part 4: job type - enum or not #447

m-mohr opened this issue Oct 19, 2024 · 0 comments
Labels
Part 4 (Job Management) OGC API - Processes - Part 4: Job Management

Comments

@m-mohr
Copy link

m-mohr commented Oct 19, 2024 •
edited
Loading

Should this be made a simple string with examples?
Do we want to create the same situation as statusCode needing an override because of the new created status?

If the long term use is to have job management available for an OGC API, maybe it would be better to define a Requirements class that say for openEO, type: openeo MUST be used, and process for OGC API - Processes. A "long" Coverage processing could then easily define their own requirement class with type: coverage, without causing invalid JSON schema definitions.

Originally posted by @fmigneault in #437 (comment)
@gfenoy gfenoy added the Part 4 (Job Management) OGC API - Processes - Part 4: Job Management label Oct 21, 2024
@gfenoy gfenoy mentioned this issue Oct 31, 2024
Merged
@gfenoy gfenoy closed this as completed in 9d7c973 Oct 31, 2024
gfenoy added a commit that referenced this issue Oct 31, 2024
@gfenoy
Merge pull request #468 from GeoLabs/feature/fix-issue-447
b11ebfb 
Typo in processes-types.yaml (closes #447)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Part 4 (Job Management) OGC API - Processes - Part 4: Job Management
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gfenoy @m-mohr