NOTE: This Use Case Summary serves as a template for documenting research workflows. As an example - dengue outbreak risk assessment in Ghana - this Markdown-based approach enables teams to collaboratively define data requirements, harmonization strategies, and analysis plans. This example is illustrative and not validated. Looking ahead, we aim to integrate automated documentation tools that generate summaries directly from curated metadata, reducing manual effort and ensuring consistency across use cases.
1. Use Case Specification
|
|
| Disease under study |
Arboviral diseases |
| Spatial coverage |
Ghana (GHA) |
| Highest-level shape |
Country (admin0) |
| Lowest-level |
District (admin2) |
| Resolution applicable to use case |
Region (admin1) |
| Temporal coverage |
2020-01-01 - 2025-12-31 |
| Highest-level |
Year |
| Lowest-level |
Day |
| Resolution applicable to use case |
Month |
| Maintenance & Updates |
|
| Update frequency |
[e.g., ad-hoc / weekly / monthly / annually] |
| Responsible |
[Team member(s)] |
2. Data Requirements
Original data shall be uploaded here:
Link: [URL]
- Avoid pre-processing original data to match use-case resolution. Instead, provide data at its native resolution. The Data Hub handles aggregation and harmonization automatically, allowing us to apply different strategies depending on the use case
- Do not clean your datasets for spatial boundary changes; document any changes you encounter instead (to be added in the Data Layer metadata). The Data Hub is developing centralized handling for spatial mismatches across all layers, so these issues can be addressed consistently platform-wide
3. Access Methods
|
|
| Shapefiles |
|
| API |
template available for Python and R |
| Downloables |
GeoPackage, GeoJSON, CSV (WKT) |
| Data Layers |
|
| API |
template available for Python and R |
| Downloables |
CVS, Excel |