Skip to main content
`Ctrl`+`K`

# Prep Toolset

The Prep Tools in the Oklahoma NG9-1-1 GIS Toolkit are designed to help users create and standardize GIS data so it aligns with the NG9-1-1 schema, domains, and field naming conventions. These tools ensure that all geodatabases and feature classes are properly formatted before submission.

Tip

Tip: Run the Prep Tools before performing any adjustments or submissions to confirm your data structure is fully compliant with NG9-1-1 standards.

## 0 - Assign NGUID Field

Warning

Version 3 of the Standard prescribes a different NGUID format than version 2.2. NGUIDs that were compliant with v2.2 are no longer valid!

This tool generates a unique NENA NGUID for features within a specified feature class. It can either concatenate user-defined fields (such as URN, Local, or Agency identifiers) or reformat an existing NGUID field based on user input.

Important

Many validation routines depend on NGUIDs to function properly!

The feature class does not need to be Standard-compliant to use this tool. When executed, the tool creates a new Standard-compliant NGUID field and calculates its values using the parameters provided by the user.

The assign method selected by the user determines how the new NGUID values are concatenated. Certain assign methods may require specific fields to be present in the feature class.

### Usage

1. Select the Standard feature class name.

2. Select feature class to assign NGUID.

3. Select assign method to specify which NGUID creation method to use.

   NGUID Assignment Methods

   - NGUID - Requires user-specified NGUID field. Method required for a format change.

   - LOCAL - Requires Local field.

   - SEQUENTIAL - Uses a sequential count for the Local portion of the NGUID field

4. Optional switch for Old format (@) to New format (:).

5. Optional switch to delete old NGUID field. Since the tool will create a new NGUID field to ensure that the Standard schema is followed, the user may specify whether to keep or delete the old NGUID field.

6. Optional name for the old NGUID field that will be used if user selects to not delete the old field (usage 5).

7. Field table containing field options for the NGUID, Local, and Agency fields. The filter list is based on the user-specified feature class (usage 2).

8. Execute the tool.

## 1 - Create Standard GDB

This tool creates a Standard geodatabase in a specified folder location using a user-selected coordinate reference system. Users may include none, some, or all feature classes, as long as they follow the Standard schema.

Additionally, the tool can generate blank Standard feature classes within the new geodatabase if needed.

### Usage

1. Select the folder location where you would like your NG911 geodatabase to be saved.

2. Provide output geodatabase name.

3. The Spatial Reference that is automatically chosen is Standard compliant. If `--USER SPECIFIED--` is selected, a spatial reference will need to be selected manually.

4. Select Standard feature classes or the option to create blank feature classes. If nothing is provided, nothing will be created.

5. Execute the tool.

Important

Only select the location of a specific Standard Feature Class if you know that data is compliant with the current Standard.. If you already have a feature class (e.g., `
ROAD_CENTERLINE`, `
ADDRESS_POINT`, etc.) and are not sure whether it is compliant, you should select prep-field-map. With that tool, you will be able to import your current data to into a new feature class with a compliant schema.

## 2 - Field Map Feature Class

Tip

If you have existing data that isn’t Standard-compliant, consider using this tool to import it.

This tool generates field maps that link user-specified feature class fields to Standard feature class fields following the correct schema — including field names, data types, lengths, and domains.

A blank Standard feature class is first created, after which the appropriate Standard-compliant fields are added. The tool then performs field mapping between the user’s fields and the Standard fields.

During this process, the values in the user fields are reviewed and adjusted as needed to ensure compliance with NG9-1-1 Standards.

### Usage

1. Select Standard geodatabase.

2. Select Standard feature class name.

3. Select user-specified feature class.

4. Select fields to be mapped. If no field is specified, the field will remain blank.

5. Execute the tool.

## 3 - Create Blank Standard Feature Classes

This tool creates blank Standard feature classes within a Standard geodatabase, providing a ready-to-use structure that follows the required NG9-1-1 schema.

### Usage

1. Select Standard geodatabase.

2. Select the names of Standard feature classes to create blank.

3. Execute the tool.

## 4 - Create Standard ESZ & ESB Feature Classes

Tip

Use this tool if you have an esz or esn feature class but not individual feature classes for EMS, fire, and law enforcement boundaries.

This tool processes and dissolves the Emergency Service Zone (ESZ) feature class to generate the standardized Emergency Service Boundary (ESB) feature classes within the Standard geodatabase.

Upon execution, it creates the following output feature classes:

- `
  ESZ_BOUNDARY` – Represents the combined Emergency Service Zones.

- `
  ESB_EMS_BOUNDARY` – Defines the Emergency Medical Service boundaries.

- `
  ESB_FIRE_BOUNDARY` – Defines the Fire Service boundaries.

- `
  ESB_LAW_BOUNDARY` – Defines the Law Enforcement boundaries.

These standardized layers ensure consistent and accurate representation of emergency service areas across the NG911 dataset.

### Usage

1. Select the ESZ feature class to dissolve.

It doesn’t need to be Standard-compliant, but it must include, at a minimum, fields that map to `
ESZ`, `
EMS`, `
FIRE`, and `
LAW`.

2. Select the Standard geodatabase.

This is where the resulting boundary feature classes will be created.

3. Indicate whether to assign sequential NGUIDs to the ESB feature classes.

This option applies only to the ESB feature classes and will not affect the output ESZ feature class.

4. Select the NGUID assignment method for the output ESZ feature class.

This setting affects only the output ESZ feature class. Depending on the method selected, fields may need to be mapped to one or more of the following: `
NGUID_ESZ`, `
Agency_ID`, and/or `
Local_ID`.

See also

NGUID Assignment Methods

If the NGUID method is selected, an additional option becomes available to convert existing v2.2 NGUIDs to v3 NGUIDs.

5. Indicate whether to copy ESB fields to the `
DsplayName` fields of each output feature class.

This setting affects only the ESB feature classes. For example, if selected, the source field provided for `
EMS` will also be mapped to the `
DsplayName` field of `
ESB_EMS_BOUNDARY`.

6. Select the fields to map.

Ensure all required fields are correctly aligned with their corresponding NG911 Standard fields.

7. Execute the tool.

The tool will process the inputs, perform the dissolves, and generate the standardized boundary feature classes.