Humanitarian GIS Methodology, OCHA P-Codes & Symbology Standards

Engineering specifications for administrative P-Code joins, WGS84 facility coordinate deduplication, friction-surface travel-time isochrones, and accessible humanitarian cartographic symbology.

1. Administrative P-Code Normalization Across Arabic Transliterations

String-matching Arabic place names across humanitarian spreadsheets consistently breaks automated health dashboards. A single governorate or district frequently appears under multiple Latin transliterations—for example, Al Hudaydah, Hodeidah, and Al-Hodeida, or Ad Dali' versus Al-Dhale'e. In conflict zones where operational control splits district health offices, field teams also rename sub-districts or merge catchment zones locally without updating master UN registries.

OCHA Place Codes (P-Codes) solve this ambiguity by assigning an immutable alphanumeric key to every administrative unit in the Common Operational Dataset (COD). For Yemen, Admin-1 governorates carry codes from YE-11 through YE-32 (22 units), Admin-2 districts span 333 four-digit identifiers, and Admin-3 sub-districts (uzlah) map rural primary health clinics down to village clusters. Every analytical table on this observatory stores P-Codes as primary join keys before rendering human-readable English place labels.

2. Facility GPS Validation & Spatial Deduplication Pipeline

Emergency clinic surveys collected via mobile ODK or KoboToolbox forms in low-connectivity environments suffer four recurring coordinate defects: (1) decimal-degree sign or axis swaps placing Yemeni clinics in the Indian Ocean or Central Asia, (2) zero-coordinate defaults (0.0, 0.0) when handheld GPS locks time out inside concrete triage rooms, (3) duplicated district-capital coordinates applied uniformly to dozens of rural outreach posts, and (4) stale WGS84 datum shifts against legacy Soviet or British military topographic sheets.

Before publishing facility readiness rates, our spatial QA pipeline runs deterministic bounding-box validation (latitude 12.00 N to 19.05 N, longitude 42.50 E to 54.55 E for mainland and Socotra corridors), spatial-join verification confirming the clinic point falls inside its declared Admin-2 district polygon, and 150-meter proximity clustering to merge duplicate clinic entries reported separately by nutrition and trauma partners.

3. Conflict Friction Surfaces vs. Naive Euclidean Catchments

Drawing a 10-kilometer circular buffer around a district hospital severely overestimates true healthcare accessibility across Yemen's western highlands and contested frontlines. Two villages separated by 8 kilometers in straight-line distance across the Haraz or Taiz escarpments may require four hours of rough mountain switchbacks—or become completely severed when a bridge washout or active checkpoint closes the connecting spur.

Cost-distance friction surfaces assign travel impedance values (minutes per 100-meter raster cell) derived from road surface class, digital elevation slope gradients, seasonal wadi flood masks, and documented transport checkpoint delays. Generating 30-minute, 60-minute, and 120-minute travel-time isochrones around functional comprehensive emergency obstetric and newborn care (CEmONC) centers exposes the exact rural populations stranded beyond the golden hour for obstructed labor or trauma stabilization.

4. Humanitarian Symbology & Low-Ink Map Legibility

Field coordination maps must remain legible whether inspected on a sunlit tablet screen or printed in monochrome inside a provincial operations tent. Cartographic hierarchy therefore restricts high-saturation emergency vermilion exclusively to closed facilities, active outbreak clusters, or impassable road segments, while pairing distinct geometric markers (circles for primary clinics, squares for cold-storage depots, triangles for mobile outreach teams) so color-vision-deficient analysts never rely on hue alone.

5. Offline MBTiles Packaging & Open-Data Licensing

Emergency health deployments across governorates with intermittent satellite or GSM backhaul cannot depend on live vector-tile CDNs to inspect road closures or clinic coordinates. Field GIS workflows compile baseline Common Operational Datasets—administrative boundary polygons down to ADM3 sub-district level, hydrographic wadi crossings, elevation contours at 50-meter intervals, and validated health facility points—into self-contained SQLite MBTiles archives under 180 MB per regional theater. Compressing raster hillshades alongside simplified vector road centrelines allows field coordinators running QField or OsmAnd on standard Android tablets to perform offline shortest-path routing and attribute inspection with zero cellular connectivity.

Equally critical is transparent open-data provenance and attribution discipline across interagency archives. Spatial layers derived from Humanitarian Data Exchange (HDX) repositories, OpenStreetMap road-network edits, and non-sensitive facility master lists retain explicit CC BY 4.0 or ODbL metadata headers specifying publication date, coordinate reference system (EPSG:4326 geographic storage paired with EPSG:32638 UTM Zone 38N metric distance calculations across western and central Yemen), and custodian agency. Where conflict-sensitivity review restricts exact GPS dissemination for trauma stabilization points or active mobile medical clinics, public archival tables intentionally generalize locations to ADM2 district centroids while recording the spatial precision tier inside dedicated quality columns.

Standardizing both offline packaging and coordinate disclosure metadata protects field medical staff from unintended targeting risks while enabling external researchers, epidemiologists, and civil infrastructure planners to reproduce historical catchment analyses without proprietary licensing barriers.

Archival practitioners reproducing corridor accessibility surfaces should also record datum transformation tolerances alongside digital elevation model resolution. Shuttle Radar Topography Mission (SRTM) 30-meter elevation grids introduce localized slope smoothing across narrow canyon passes in Al Mahwit, Raymah, and Ta'izz, which underestimates steep highland switchback grades unless verified against GPS tracklogs collected by mobile clinic drivers. Cross-checking modeled drive-time bands against empirical ambulance dispatch logs keeps emergency referral planning grounded in real-world mechanical wear, checkpoint delays, and fuel availability across mountainous governorates.