Africa Rangeland Watch (ARW) was designed and developed by Conservation International (CI) and is aimed at monitoring rangeland impact. ARW empowers users to quantify land-use and climate impacts on rangelands over time and space, based on remotely sensed satellite imagery supplemented by ground-based rangeland monitoring.
8.1) As a user, I want to upload data, so I am not limited to the data provided on the platform.
Acceptance Criteria:
8.1) The system allows users to upload external datasets in approved formats. These are:
Shapefile
GeotiffCSVXML
SLD
GeoPackage
GeoJSON
KML
8.2) Uploaded data should be validated before ingestion.
8.3) The system provides feedback on successful or failed uploads.
8.4) Users can view and manage uploaded datasets within their profile.
8.5) Uploaded data must include metadata, such as the source and upload date.
8.6) Size of uploaded data should be limited according to file type to avoid excessive storage.
8.7) Users can upload field data from mobile devices and computers directly to ARW through file uploads, data feeds or ground-based data collection applications such as EarthRanger, CyberTracker, SMART, Quick Capture.
In phase 2 we may allow the user to bring in data through an API connection as below.
8.8) The system has a user-friendly interface or API interface to set up the automated ingestion of field data feeds only within their area of interest.
8.9) The system validates data feed sources and provides feedback for unsupported data formats and sources (Invalid URLs or files).
8.10) The data feed feature should only be available to authenticated users or service accounts that have roles/permissions that authorise them to set up automated feeds including organisation managers and members.
8.11) Data feeds automatically pull or receive new data without manual intervention.
8.12) Notifications and alerts should be sent to the user when feed synchronizations are ingested successfully or when errors occur during ingestion. The user should be able to control which notifications/alerts they want to receive.
8.13) Users can view the status of the latest data feed: last synchronisation timestamp, successful synchronizations and failed synchronizations.
8.14) Ingested data should be stored securely and become immediately available for analysis workflows.
amyburness
commented
1 day ago
Expectation:
8.1) As a user, I want to upload data, so I am not limited to the data provided on the platform.
Acceptance Criteria:
8.1) The system allows users to upload external datasets in approved formats. These are: Shapefile GeotiffCSVXML SLD GeoPackage GeoJSON KML 8.2) Uploaded data should be validated before ingestion. 8.3) The system provides feedback on successful or failed uploads. 8.4) Users can view and manage uploaded datasets within their profile. 8.5) Uploaded data must include metadata, such as the source and upload date. 8.6) Size of uploaded data should be limited according to file type to avoid excessive storage. 8.7) Users can upload field data from mobile devices and computers directly to ARW through file uploads, data feeds or ground-based data collection applications such as EarthRanger, CyberTracker, SMART, Quick Capture.
In phase 2 we may allow the user to bring in data through an API connection as below.
8.8) The system has a user-friendly interface or API interface to set up the automated ingestion of field data feeds only within their area of interest. 8.9) The system validates data feed sources and provides feedback for unsupported data formats and sources (Invalid URLs or files). 8.10) The data feed feature should only be available to authenticated users or service accounts that have roles/permissions that authorise them to set up automated feeds including organisation managers and members. 8.11) Data feeds automatically pull or receive new data without manual intervention. 8.12) Notifications and alerts should be sent to the user when feed synchronizations are ingested successfully or when errors occur during ingestion. The user should be able to control which notifications/alerts they want to receive. 8.13) Users can view the status of the latest data feed: last synchronisation timestamp, successful synchronizations and failed synchronizations. 8.14) Ingested data should be stored securely and become immediately available for analysis workflows.