Skip to main content
`Ctrl`+`K`

# Workflows

The NG9-1-1 GIS Toolkit Workflow provides a high-level overview of the major steps that GIS authorities must complete to prepare and transform their local data for NG9-1-1.

While specific workflows may vary depending on the condition and maturity of each dataset, the overall process outlines how to:

1. Develop Standard-compliant data.

2. Validate datasets using the Toolkit’s validation and comparison tools.

3. Prepare and submit the NG9-1-1 geodatabase to the statewide repository.

## Submitting Data to the Oklahoma NG9-1-1/GIS Repository

The Submission Toolset finalizes and packages compliant data for submission to the Oklahoma NG9-1-1/GIS Repository.

Data that passes all validation checks is exported as a .zip file, uploaded by the GIS authority, validated again by the repository, and—once approved—merged into OKMaps.

For detailed instructions on these steps, refer to:

- The Submission Toolset section of this manual.

- The Oklahoma NG9-1-1/GIS Repository User Guide for post-submission requirements and management guidance.

## Resources for GIS Authorities Without Required NG9-1-1 Feature Classes

GIS authorities may be starting from different points—some with fully developed datasets, others with few or no required layers. The NG9-1-1 GIS Toolkit supports both scenarios by providing tools to generate, validate, and standardize key datasets.

The Toolkit helps produce the following Standard-compliant feature classes:

- Address Points

- Road Centerlines

- PSAP Boundaries

- Discrepancy Agencies Boundaries

- Emergency Service Zones (ESZs)

- Law Emergency Service Boundaries (ESB_LAW_BOUNDARY)

- Fire Emergency Service Boundaries (ESB_FIRE_BOUNDARY)

- EMS Emergency Service Boundaries (ESB_EMS_BOUNDARY)

For GIS authorities with limited data, the Prep Tools can help generate Standard-compliant layers from existing local or regional datasets.

These tools, combined with guidance from this manual, allow authorities to progressively build, enhance, and maintain compliant GIS data in preparation for NG9-1-1 submission.

## Example Step-by-Step Workflow

### Step 1: Readiness & Training

- Review Oklahoma NG9 1 1 & Address Standard (v3.0).

- Complete Oklahoma NG9 1 1 GIS training (Authority videos/materials).

Outcome: Team understands standards, tools, and responsibilities.

### Step 2: Assess Local GIS Data

- Inventory existing datasets (Address Points, Road Centerlines, PSAP, ESZ/ESB, etc.).

- Identify gaps, schema differences, domains, topology needs.

- Decide effort to align data and plan the transition.

Decision A: Do you have a geodatabase with the correct domains configured?
→ No: Go to 3a and create a new one.
→ Yes: Continue.
Decision B: Do you have Address, Road, and PSAP data?
→ No: Go to 3b and create blank ones.
→ Yes: Go to 3c and import existing data.
Decision C: Do you have ESZ and ESB (EMS/FIRE/LAW)?
→ No, none: Go to 3b and create blank ones.
→ ESZ only: Go to 3d to generate ESBs.
→ Yes, all: Continue.

### Step 3: Prep (Build the Standard Geodatabase)

Tools: Assign NGUID • Create Standard GDB • Field Map Feature Class • Create Blank Standard FCs • Create Standard ESZ & ESB

1. Create a Standard geodatabase with correct spatial reference and domains.

2. Create blank Standard feature classes as needed.

3. Field Map local classes to Standard schema (names, types, lengths, domains).

4. If missing, generate ESBs from an existing ESZ feature class.

5. Assign NGUIDs (format v3) and, if needed, convert from v2.2.

Outcome: Standard-compliant structure populated with mapped data.

### Step 4: Validation (Conformance Checks)

Tool: Validate Geodatabase

- When running for the first time, selecting Run All Available Routines is recommended.

- On subsequent runs, you may select only the routines that apply to the

Results: Validation issues written to TemplateCheckResults and FieldValuesCheckResults.

Outcome: Understand issues with NG911 data.

Decision D: Any Errors?
→ Yes: Fix issues (return to 2/3 as needed) and re run Validation.
→ No: Proceed.

### Step 5: Enhancement (Quality & Structure)

Tools: Add Topology • Calculate/Convert/Fix Fields

- Apply topology rules (overlap, gaps, dangles, self intersections, etc.).

- Calculate/convert Next Gen vs Legacy fields, FullName/FullAddr, parity, MSAG fields.

- Clean data (spaces, case, domains, level fields, etc.).

Outcome: Data structurally sound and attribute consistent.

### Step 6: Comparison (Optional QA)

Tools: Compare NG911 Feature Classes • Compare NG911 Geodatabases

- Compare versions (pre/post edit, local vs staging) to confirm intended changes.

Outcome: Verified edits and version consistency.

### Step 7: Submission (Packaging)

Tools: Check All and Zip • Export to Shapefiles • Export to Zip

- Run Check All and Zip (all required validations). - No validation errors → Export .zip for submission. - Validation error(s) → Return to Step 4.

- Alternative exports: Shapefiles or .zip of GDB when needed.

Outcome: Submission package created.

### Step 8: Repository & Post-Submission

- Upload .zip to the Oklahoma NG9-1-1/GIS Repository.

- Repository validates; when approved, data is merged into OKMaps.

- Maintain change logs; schedule periodic validations and comparisons.

Outcome: Data published statewide; establish ongoing maintenance cadence.