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.

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

Subclass for EO processes #10

Open
huard opened this issue Apr 6, 2018 · 4 comments
Open

Subclass for EO processes #10

huard opened this issue Apr 6, 2018 · 4 comments

Comments

@huard
Copy link

huard commented Apr 6, 2018

All the EO COPERNICUS processes share a common set of inputs and outputs. We should propose an elegant way to use subclasses rather than copy-pasting the same code. I've tried something with the ocgis_func, we might want to review and improve it.

class GenericEOProcess
    common_inputs = [
        LiteralInput('BBox', 'Bounding Box', ...),
        LiteralInput('start', 'Start Date',
         ...
        ]
@huard
Copy link
Author

huard commented Apr 13, 2018

@nilshempelmann
Also, why not use the BoudingBoxInput ? I've never used it myself, so really just a question. Is it complicated to use it ?

@nilshempelmann
Copy link
Member

BoundingBoxInput was disabled.
@cehbrecht : Any news if its worling now? Can we give it a try?

@cehbrecht
Copy link
Member

I need to check it. But what I remember is that PyWPS does it right but OWSLib does not.

@nilshempelmann nilshempelmann transferred this issue from bird-house/flyingpigeon Dec 5, 2018
@cehbrecht
Copy link
Member

See also examples to avoid code duplication provided by PR bird-house/birdhouse-docs#35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants