Skip to main content
`Ctrl`+`K`

# Enhancement Toolset

These tools are designed to automate key tasks involved in data creation and revision that improve the accuracy, consistency, and overall integrity of the data.

## Add Topology

This tool verifies that spatial data within a Geodatabase follow the rules and relationships required by the Standard by adding a topology dataset to the required feature dataset. It checks the geometric relationships among geographic features—such as roads, boundaries, and address points—to ensure that the data are clean, accurate, and logically consistent.

See also

Topology Rules and Exceptions

### Purpose

By running the Topology Tool, users can:

- Validate that all spatial data conform to NG911 topology standards.

- Detect and correct spatial errors before submission.

- Ensure statewide consistency and data integrity across all NG911 datasets.

## Calculate/Convert/Fix Field(s)

The Field Calculation and Conversion Tool automates the process of calculating, converting, and cleaning fields in the Standard NG911 feature classes. It ensures that address points, road centerlines, and related datasets comply with both Next Generation (Next-Gen) and, as applicable, Legacy data standards.

### Usage

1. Select the NG911 geodatabase.

2. Choose the desired analysis type (e.g., calculate, convert, or fix fields).

3. Set any required and optional parameters.

4. Run the tool to perform all necessary calculations or corrections automatically.

### Available Analyses

#### Calculate `FullName` and/or `LgcyFulSt`

Calculates the `
FullName` (if NEXT-GEN is selected) and `
LgcyFulSt` (if LEGACY is selected) fields for `
ADDRESS_POINT` and/or `
ROAD_CENTERLINE`.

The Next-Gen street fields are used to compute `
FullName`, and the Legacy street fields are used to compute `
LgcyFulSt`.

Tip

If only one set of street fields are populated (i.e., either Next-Gen or Legacy street fields), consider first running ccf-convert-type and/or ccf-convert-direction.

#### Calculate `FullAddr` and/or `LgcyFulAdd`

Calculates the `
FullAddr` (if NEXT-GEN is selected) and `
LgcyFulAdd` (if LEGACY is selected) fields for `
ADDRESS_POINT`.

The Next-Gen street/address fields are used to compute `
FullAddr`, and the Legacy street/address fields are used to compute `
LgcyFulAdd`.

Tip

If only one set of street fields are populated (i.e., either Next-Gen or Legacy street fields), consider first running ccf-convert-type and/or ccf-convert-direction.

#### Calculate `Parity_L` and `Parity_R`

Uses the address range fields to compute `
Parity_L` and `
Parity_R` in `
ROAD_CENTERLINE`.

#### Calculate Null Values to `N`

Automatically replaces null values in fields with the `
YESNO` domain with `N`.

#### Calculate `RCLMatch` and `RCLSide`

Links `
ADDRESS_POINT` features to their corresponding `
ROAD_CENTERLINE` features by performing the following operations:

- Creating dataframes for both feature classes

- Matching concatenated street field strings

- Comparing address numbers, parity, and MSAG community fields

- Assigning `
  NGUID_RDCL` to matching address point’s `
  RCLMatch`

If multiple matches occur, the tool labels them as `TIES` and returns all related IDs as a pipe-separated list. If there is no match, the attribute is set to `NO MATCH`.

#### Calculate `MSAGComm`

In `
ADDRESS_POINT`, sets null `
MSAGComm` attributes to the value of `
City`, or, if it is also null, to the value of `
County`.

It does the same for `
ROAD_CENTERLINE`, but with the left and right equivalent fields, as well as setting `
GeoMSAG_L` and `
GeoMSAG_R` to either `N` if the corresponding MSAG community field is null or `Y` if it is not null.

#### Convert `Type` (`Legacy` or `NEXT GEN`)

In `
ADDRESS_POINT` and `
ROAD_CENTERLINE`, uses the values of `
PreType` and `
StreetType` to compute `
LgcyPreTyp` and `
LgcyType`, respectively, or vice-versa.

#### Convert `Direction` (`Legacy` or `NEXT GEN`)

In `
ADDRESS_POINT` and `
ROAD_CENTERLINE`, uses the values of `
PreDir` and `
SufDir` to compute `
LgcyPreDir` and `
LgcySufDir`, respectively, or vice-versa.

#### Fix Leading/Trailing Spaces

Removes unnecessary spaces from the beginning and end of text attributes.

#### Fix Domain Case

Adjusts capitalization of attributes to match domain values. For example, if a `
PreDir` attribute is `North`, this analysis would change the letter case to `NORTH`, as in `
DIRECTION`.

#### Fix Level Fields

Converts `
FromLevel` and `
ToLevel` fields from numeric to text format for consistency in `
ROAD_CENTERLINE` data.