Level 1: System Context¶
At the highest level, the System Context Diagram depicts AClimate as a single box surrounded by its external entities, such as users, external systems, and data sources. This diagram provides a broad view of the system and its interactions with the outside world.
Diagram¶
Users¶
The platform serves as a comprehensive solution to support decision making process, catering to the needs of researchers, decision-makers, farmers, and extension agents.
| Actor | Description |
|---|---|
| Farmers / Producers | Benefit from information and recommendations for agricultural practices to make informed decisions about their crops. |
| Technical Assistants / Extensionists | Facilitate effective communication and support between the platform and farmers. They use analytics to advise on crop management. |
| Researchers | Analyze and configure data into the system. They access historical climate data and processed indicators for analysis, model calibration, and validation. |
| Administrators | Configure system parameters, manage geographic entities, crop configurations, and user access. |
| Decision-makers | Rely on insights from the system to make informed choices at organizational or sectoral level. |
External Systems¶
| System | Description | Interaction |
|---|---|---|
| Weather Stations | Network of meteorological stations from IDEAM and other providers. | Provide real-time and historical climate observations (temperature, precipitation, humidity, solar radiation). |
| Satellite / Spatial Data | Global gridded climate datasets including ERA5 (JRC) and CHIRPS (UCSB). | Provide spatial climate data for areas without station coverage. Used for historical analysis and indicators. |
| IDEAM | Instituto de Hidrolog\u00eda, Meteorolog\u00eda y Estudios Ambientales (Colombia). | Official source of national climate data. Provides station data and seasonal forecasts. |
Key Interactions¶
- Data Ingestion: ETL pipelines fetch data from weather stations and spatial sources (ERA5, CHIRPS), process it, and store it in the database.
- Data Access: The WebAPI exposes data through RESTful endpoints, authenticated via Keycloak.
- User Consumption: The Frontend and Admin Portal consume the WebAPI to present data to end-users and administrators.
- External Consumption: External systems can consume the WebAPI for integration purposes.