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

Can we define our WPS input types in a generic library to support our own WPS Profile? #7

Closed
agstephens opened this issue Mar 12, 2020 · 1 comment
Closed

Can we define our WPS input types in a generic library to support our own WPS Profile? #7

agstephens opened this issue Mar 12, 2020 · 1 comment
Assignees
@agstephens

Comments

@agstephens
Copy link
Collaborator

agstephens commented Mar 12, 2020 •
edited
Loading

See examples of time and lat/lon inputs here:
https://github.com/bird-house/finch/blob/master/finch/processes/wpsio.py

More generally, we will have some inputs that are common across our packages. These might include data_refs or resources - that specify ESGF datasets. Maybe we should define these as part of daops in a generalised way that rook can use.
@ellesmith88 ellesmith88 transferred this issue from roocs/proto-lib-34e Mar 30, 2020
@agstephens agstephens changed the title Should we re-use Finch input types? Can we define our WPS input types in a generic library to support our own WPS Profile? Apr 3, 2020
@agstephens agstephens self-assigned this Apr 3, 2020
@agstephens
Copy link
Collaborator Author

The roocs-utils package now manages the Parameters in a generic way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@agstephens agstephens

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@agstephens