An independent initiative of G-ynthetic LabsCompany website ↗

GIS & jurisdiction data

Real geography.
A controlled exercise world.

Begin with the place you are responsible for—its roads, boundaries, facilities, and available current context. Then capture a separate exercise copy for a scenario you can control.

G-ynthetic concept illustration of an emergency coordination room overlooking a city, with geographic data panels
Concept illustration · GIS coordination environment. Displayed feeds are illustrative; the browser preview uses sample data.

Load the jurisdiction

City, county, or state:
define the right area.

The repository supports city-name search through Nominatim and base-map data acquisition through OpenStreetMap / Overpass.

Bring county, state, or other jurisdiction-specific layers into the full application through GIS imports. GeoJSON and GeoPackage imports support local context without requiring one universal dataset.

Coverage, detail, and update frequency depend on the source and the area loaded. Building acquisition is bounded around the city center for query performance; a city search does not imply complete statewide coverage.

A clear distinction

Geography is real.
Freshness is source-dependent.

“Live” describes a connected source and its timestamp—not an assumption that every layer is current everywhere.

Data supported by the full repository application
DataHow it entersWhat to verify
Roads, buildings, boundariesCity-name search, OSM / Overpass acquisitionGeographic extent, completeness, and source freshness
Jurisdiction GIS layersGeoJSON or GeoPackage import in the full applicationLayer ownership, coordinate system, and as-of date
Weather, air, and maritime contextAvailable source-specific feeds and watchersProvider access, local coverage, and last update
Facilities and resource contextAvailable facility data and configured exercise inputsMeasured values versus assumptions or estimates
Cameras and sensorsAssumed positions in the documented prototypeNo real device network is bound by those illustrations

Forking the loaded picture

One moment becomes
the exercise starting point.

01 / Input

Loaded jurisdiction

Geography, available feeds, resources, and the world state currently held by the application.

02 / Capture

Known-time snapshot

A human initiates the exercise fork. The capture records the originating jurisdiction and the fork time.

03 / Exercise

Independent scenario

Live feeds are cut for the exercise copy. Scenario activity is marked EXERCISE and recorded separately.

Read-only data intake and an isolated exercise world support a simple boundary: rehearse policy and procedure without writing simulated changes back to operational systems.

Human-directed scenario design

The place sets the context.
You set the question.

Customize the hazard, severity, conditions, objectives, participants, and inject sequence. AI can support scenario development and fill response positions; deterministic controls provide a comparison baseline.

The person running the exercise decides which policies and procedures are being examined, when to advance the exercise, and what the findings mean.

Connect the geography to the evaluation ↗

An accountable exercise starts with a clear question

Make the next exercise a better test.

Discuss an exercise ↗