What was built Four analytical GIS maps covering Afghanistan mineral resource distribution, Belt and Road Initiative infrastructure corridors, and regional transportation networks — delivered over 13 months under analyst direction.
Who it was for DoD-affiliated internal research — government analysts requiring rapid spatial outputs with direct operational relevance.
Why it mattered In this domain, spatial inaccuracy carries operational consequences. Each output had to be defensible under internal review before delivery — no room for ambiguity in the data or the methodology.

The Challenge

Over 13 months, four analytical GIS maps were produced supporting internal government research and planning. The subject matter covered Afghanistan's mineral resource distribution, Belt and Road Initiative infrastructure corridors, and regional transportation networks — domains where spatial accuracy carries direct operational consequences. Each output was built to enable spatial analysis in areas where reliable datasets are incomplete, contested, or unavailable through standard sources.

Work was executed under analyst direction: research requirements came in, spatial products went back out. The primary dataset — Belt and Road infrastructure — required integration into the GIS environment, spatial relationship analysis, and verification against regional basemap data before outputs were delivered. Rapid turnaround was required. Precision was not negotiable.

This engagement required a specific analytical discipline: understand the intelligence question before touching the data, structure the spatial framework to answer it directly, and produce outputs that hold up to internal review under time pressure. That discipline — applied consistently across four maps over 13 months — is the transferable product of this work.

"Analytical GIS under operational pressure has one standard: the spatial output has to be defensible. Structure the data correctly, verify the output, and don't deliver until it holds up — that discipline carries across every domain."

Process

  1. 1
    Research Reviewed analyst research requests; identified spatial scope and data requirements; sourced Belt and Road infrastructure dataset.
  2. 2
    Data Prep Integrated infrastructure dataset into ArcGIS environment; verified spatial alignment with regional basemap data.
  3. 3
    GIS Work Mapped mineral resource distribution, infrastructure corridors, and transportation networks; produced rapid-turnaround cartographic outputs.
  4. 4
    Output 4 analytical maps delivered over 13 months; used for internal planning and research.
Principle 01
Structure before software

In high-stakes analytical work, the framework — what you're mapping, what question it answers, what counts as correct — must be established before any data is processed. This discipline was forged under conditions where imprecision had real consequences.