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

EPIC 3.1: QGIS GEOSYS Processing Algorithm #24

Closed
AndreLester opened this issue Mar 28, 2019 · 0 comments · Fixed by #37
Closed

EPIC 3.1: QGIS GEOSYS Processing Algorithm #24

AndreLester opened this issue Mar 28, 2019 · 0 comments · Fixed by #37
Assignees

Comments

@AndreLester
Copy link
Contributor

Expectation: As a QGIS Processing toolbox user, I would like be able to incorporate the retrieval and analysis of GEOSYS products into my workflows.

Acceptance Criteria:

  • Given the GEOSYS plugin is installed and my credentials are set in the options dialog, when
    I open the QGIS Processing toollbox, then the GEOSYS plugin will be available.
  • Given that I am using the GEOSYS Processing Algorithm, when I define the request criteria
    in the algorithm then the algorithm should successfully return the dataset requested.
  • Given that a date is requested, when the user presses OK, then the most recent coverage
    before the chosen date will be retrieved.
  • Given that the GEOSYS algorithm may retrieve more than one coverage, when the user
    presses OK, then the algorithm will merge the retrieved products as a single virtual raster and
    add that raster to the QGIS map canvas.
  • Given that a sensor is selected, when the user presses OK, then only coverages for that
    sensor will be returned.
  • Given that a polygon layer is selected, when the user presses OK, then the algorithm will
    iteratively search GEOSYS for each polygon by passing the WKT string representation of the
    polygon.
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

Successfully merging a pull request may close this issue.

2 participants