Nathaniel Pyron on GIS and the Installation Common Operating Picture: Mapping the Mission

A GIS mapping application with layered geospatial data — the foundation of modern installation master planning. (Stock photo)

Every installation master plan is, at its core, a stack of maps. The airfield clear zones. The noise contours. The floodplain. The explosives safety arcs. The historic districts. The utility corridors. The wildlife hazard zones. The standoff distances. No planner can hold all of that in their head, and no static PDF keeps it current. The geographic information system — GIS — is where the installation's many realities live together, and the planner who masters it masters the plan.

The common operating picture

The phrase comes from military operations, but it fits planning perfectly: a common operating picture is a single, shared, geospatial view of everything that matters, current enough to act on. On an installation, the GIS is that picture. When the public works director, the environmental manager, the airfield manager, and the master planner all open the same map layers, decisions stop being made from stale drawings in separate offices. A proposed barracks site can be checked against the noise contour, the accident potential zone, the historic district, and the stormwater network in minutes rather than weeks.

This is why the Department of Defense has invested so heavily in installation geospatial standards. Common data models mean a planner at one installation can read another's data, and enterprise systems let higher headquarters roll up installation data for portfolio-level decisions. The planner's job at the local level is less about collecting data — much of it already exists — and more about curating it: making sure the layers are current, documented, and actually used in planning decisions.

Layers that earn their keep

Not every layer matters equally. The layers that consistently decide installation planning outcomes are the constraint layers: the ones that say "no" or "not here." Airfield imaginary surfaces and clear zones. Explosives safety arcs around munitions areas. Floodplains and tsunami zones. Endangered-species habitat and wetlands. Noise contours. Accident potential zones. Antiterrorism standoff distances. Historic districts. Contaminated sites.

The planner's discipline is to keep these layers authoritative. A noise contour from a decade-old study, an explosives arc drawn before a magazine was demolished, a floodplain that predates the latest flood maps — each one is a decision waiting to go wrong. Nathaniel Pyron has learned that the most dangerous layer in any installation GIS is the one everyone trusts but nobody has updated. Data governance — who owns each layer, how often it is refreshed, what source it came from — is unglamorous work that prevents expensive mistakes.

Analysis the paper map could never do

GIS earns its keep not just as a map but as an analytical engine. Suitability analysis can score every parcel on the installation against a weighted set of criteria — mission compatibility, environmental sensitivity, infrastructure access, cost — and produce a defensible ranking of development sites. Viewshed analysis can test whether a proposed tower penetrates an airfield's imaginary surfaces before a single drawing is made. Buffer analysis can instantly show every building inside a revised standoff distance. Network analysis can model how closing one gate redistributes traffic across the installation.

For airfield planning specifically, GIS is close to indispensable. The airfield's imaginary surfaces are three-dimensional geometries — approach slopes, transitional surfaces, horizontal and conical surfaces — that must be evaluated against terrain and structures. Doing that by hand is slow and error-prone; in GIS, it is a repeatable computation. When a proposed antenna or wind turbine near the installation raises an obstruction question, the planner can answer it with geometry rather than guesswork.

The planner's data check

Three habits separate planners who use GIS from planners who are used by it. First, verify the currency of every constraint layer before it enters a planning alternative — check the study date, not just the layer name. Second, document the assumptions: which noise scenario, which flood map version, which explosive-arc standard. A map that does not say what it assumes is a rumor with a legend. Third, keep the picture shared: the GIS only works as a common operating picture if the people who need it can see it. Export the key maps, brief them in project meetings, and make sure the decision-makers are looking at the same picture the planner is.

Nathaniel Pyron's rule of thumb: the master plan is only as current as its GIS. A planner who treats the geodatabase as the plan's living memory — maintained, governed, and shared — gives every project on the installation the same head start: decisions made against reality, not against last year's drawing. Map the mission, and the plan follows.

About the author

Nathaniel Pyron is a military urban planner specializing in military master planning with an airport/airfield focus. A U.S. Navy veteran who served in 1995, he later spent three years as a civilian community planner working with the U.S. Marine Corps at Camp Blaz and Darwin, Australia. He studied at the Arizona State University School of Urban Planning, class of 2007, and is an active LEED AP BD+C. Based in Honolulu, Hawaii, he writes about installation planning, airfield land use, and where military readiness meets community design. His LinkedIn title is Urban Planner (Land Use & Airspace).

Comments

Popular posts from this blog

The Sky Is Zoned Too: What Special-Use Airspace Means for Base Master Planning

The 15-Minute Base: Bringing Walkable-City Thinking to Military Installations

AICUZ, Explained: What Can Be Built Near a Military Runway