-
Notifications
You must be signed in to change notification settings - Fork 8
Imagery Request app v1 User Story document
Problem: When planning to acquire aerial and satellite imagery, it is difficult to coordinate who will capture, share when and where the capture will happen, and communicate completion progress. Multiple stakeholders are involved in the planning, capture, processing, and distribution and it is difficult to communicate between these stakeholders.
Goal: Share progress of the work. What is the AOI, what has been collected, who is collecting, how much has been completed? Where is the completed product?
- Collection Planner
- Surveyor
- Imagery end user (needs to be defined more)
-
As a collection planner, be able to review on a map existing imagery in OAM/PacDID and other imagery web services/catalogs (WMS, WMTS, TMS) and then determine whether existing imagery will suffice for use or if there needs to be a new collection.
-
As a collection planner, create a new task by manually drawing the AOI on a map or by uploading a KML/GeoJSON file. Need to communicate purpose and other information for why this needs to be collected.
-
As a surveyor or party responsible for acquiring imagery, be able to select an AOI to collect. Then be able to provide updates on task progress and upload final imagery and mission report.
-
As the imagery end user, be able to see AOIs and understand overall progress of surveys and imagery acquisitions. When is a collection planned, when is it completed, and where can I get access to the final products.