Architecture
Designing a UNCCD-Style Web GIS Observatory (Prototype)
Convention to Combat Desertification workflows translated into a practical semi-project
Designing a UNCCD-Style Web GIS Observatory (Prototype)
This is a semi-project, not a claim of official UNCCD production ownership.
I built it as a realistic prototype based on the kind of responsibilities that show up in Web GIS and information-management roles connected to the Convention to Combat Desertification (UNCCD).
If you want to see the companion case study page, start here: UNCCD Land Restoration Observatory (Prototype)
Why This Prototype Exists
Most technical interviews and consulting screens ask the same thing:
- Can you build the map and database stack?
- Can you maintain it after launch?
- Can you produce reliable reporting and backups?
This prototype was built to answer all three in one coherent system.
Scope of the Semi-Project
- Map-first UX for geospatial layer browsing
- SQL/PostGIS data model for land indicators
- Monitoring hooks for usage and traffic trends
- Monthly and quarterly reporting workflow
- Daily incremental + weekly full backup design
- Documentation-first handoff for mixed technical teams
Architecture Snapshot
React + Leaflet/OpenStreetMap
|
Node.js / Express APIs
|
PostgreSQL + PostGIS
|
Monitoring + Reporting + Backup JobsCore stack:
- Frontend: React, TypeScript, Leaflet
- Backend: Node.js, Express
- Database: PostgreSQL, PostGIS, SQL
- Ops: GitHub workflows, scheduled reports, backup routines
Example Query: Land Indicator Rollup
SELECT
district_code,
COUNT(*) AS parcels_tracked,
ROUND(SUM(ST_Area(geom::geography)) / 10000.0, 2) AS area_hectares,
ROUND(AVG(restoration_score), 2) AS avg_restoration_score
FROM land_parcels
WHERE observation_date >= DATE_TRUNC('month', CURRENT_DATE)
GROUP BY district_code
ORDER BY area_hectares DESC;This gives a district-level monthly summary that can feed KPI dashboards and narrative reporting.
Monitoring and Reporting Model
The model in this prototype uses:
- Monthly reports for traffic and engagement trends
- Quarterly summaries for management-level insights
- Anomaly alerts for unusual spikes/drops
- Audit-friendly logs for troubleshooting and transparency
What This Proves
Even as a semi-project, it demonstrates practical readiness for UNCCD-style delivery:
- Web/database implementation
- Geospatial data handling
- Operational maintenance thinking
- Reporting discipline
- Backup and retention planning
Lessons Learned
- Prototype work is strongest when it mirrors real operational constraints
- Monitoring/reporting should be designed with the data model, not added later
- GIS projects become easier to maintain when modules are explicitly separated
- Documented cadence (monthly/quarterly/daily/weekly) helps teams execute consistently