SSAP to RCL Synchronization

The SSAP Site Structure Address Point to RCL Road Centerline Synchronization quality control (QC Quality Control) check identifies where the Site/Structure Address Point (SSAP) address data is inconsistent with Road Centerline (RCL) data. This ensures that every address in the SSAP layer can be properly placed onto a corresponding road segment in the RCL layer.

Note: For all field comparisons, null and empty/blank values are considered equal values. This includes ESN Emergency Service Number. A three to five digit number representing a unique combination of emergency service agencies (law enforcement, fire and emergency medical service) designated to serve a specific range of addresses within a particular geographical area, or Emergency Service Zone (ESZ). The ESN facilitates selective routing and selective transfer, if required, to the appropriate PSAP and dispatching of the proper service agency(ies)., Community, and street name field comparisons. For example, in SSAP to RCL Synchronization, if an address point and its associated road have an ESN of null and blank respectively, this will not cause a fallout as neither record contains an ESN. To create a fallout for a required field when it does not contain a value, utilize the Null Value in Field check.

Tip: Projection-Based Unit is used in this check. Projection-Based Unit indicates the unit of measurement is pulled from the Spatial QC Projection this data target uses. If no Spatial QC Projection is used in this data target, the unit is pulled from the Data Target's projection.

To run this check, the SSAP and RCL feature classes are required.

Configurations for QC check parameters contain filters to prevent selecting incompatible field types.

The following parameters can be specifically configured for the SSAP to RCL Synchronization QC check.

  • Run On: Non-configurable. This QC check inspects the target dataset.

  • Severity: Sets the importance level of this QC check’s fallouts. Critical fallouts prevent export package outputs but will still provide fallouts.

  • SSAP Layer Name: The name of the SSAP layer.

  • SSAP - Reporting Unique ID: A unique identifier in the SSAP layer that can be used to uniquely identify a singular feature.

  • SSAP - Address Number Prefix: Represents the SSAP's address number prefix. Populate this parameter to have address prefix information included in the extended information field of the fallout report if one exists.

  • For example, if the Address Number Prefix is configured and the record includes a prefix value of 3W2N, the report will show 3W2N-1600 Venice Blvd in the extended information field, not 1600 Venice Blvd.

  • SSAP - Address Number: Represents the SSAP's address number.

  • SSAP - Address Number Suffix: Represents the SSAP's address number suffix. Populate this parameter to have address suffix information included in the extended information field of the fallout report if one exists.

    For example, if the Address Number Suffix is configured and the record includes a suffix value of B, the report will show 1600 B Venice Blvd in the extended information field, not 1600 Venice Blvd. Note that null, empty strings, or whitespace do not count as a value.

  • SSAP - Street Full Name: A list of street name fields that form the entire street name. For example: St_PreMod, St_PreDir, St_PreTyp, St_PreSep, St_Name, St_PosTyp, St_PosDir, and St_PosMod.

  • SSAP - Sub-addressing: Represents sub-addressing fields such as structure/building, wing, or unit to better distinguish the specific address point in question. Order listed here will reflect in the fallout messaging. Populate this parameter to have sub-addressing included in the extended information field of the fallout report if one exists.

    For example, if the sub-addressing parameter is configured, and the record includes a sub-addressing value of Room 305, the report will show 1600 Venice Blvd, Room 305 in the extended information field, not 1600 Venice Blvd.

  • SSAP - Emergency Service Number (ESN): Represents the SSAP's Emergency Service Number (ESN).

  • SSAP - MSAG Community: Represents the SSAP's Master Street Address Guide (MSAG) Community.

  • Road Centerline (RCL) Layer Name: The name of the road centerline layer.

  • RCL - Reporting Unique ID: A unique identifier in the Roads layer that can be used to uniquely identify a singular feature.

  • RCL - Left Address Number Prefix: Represents the address number prefix on the left side of the road segment.

  • RCL - Right Address Number Prefix: Represents the address number prefix on the right side of the road segment.

  • RCL - Left FROM Address: Represents the address number on the FROM node on the left side of the road segment.

  • RCL - Left TO Address: Represents the address number on the TO node on the left side of the road segment.

  • RCL - Right FROM Address: Represents the address number on the FROM node on the right side of the road segment.

  • RCL - Right TO Address: Represents the address number on the TO node on the right side of the road segment.

  • RCL - Parity Left: Indicates whether the left side of the road segment contains odd, even, both, or zero address range values.

  • RCL - Parity Right: Indicates whether the right side of the road segment contains odd, even, both, or zero address range values.

  • RCL - Street Full Name: A list of street name fields that form the entire street name. For example: St_PreMod, St_PreDir, St_PreTyp, St_PreSep, St_Name, St_PosTyp, St_PosDir, and St_PosMod.

  • RCL - ESN Left: Represents the Emergency Service Number (ESN) on the left side of the road segment.

  • RCL - ESN Right: Represents the Emergency Service Number (ESN) on the right side of the road segment.

  • RCL - MSAG Community Name Left: Represents the MSAG Community name on the left side of the road segment.

  • RCL - MSAG Community Name Right: Represents the MSAG Community name on the right side of the road segment.

  • RCL - Offset Distance (Projection-Based Unit): The distance to offset a point from the road when calculating its position for the Wrong Block subcheck.

  • Case Sensitivity: Select Match Case to enable and maintain the integrity of upper or lower case text in your data. See Case Sensitivity.

The following information is included for this QC check's fallout output.

  • QC check name
  • Description of the QC check
  • Unique identifier of the SSAP record not matching road centerlines
  • Specific failure information - A description of what caused the SSAP record to fail. The fallout message values are added to the Extended Information description field in the fallout report. The message identifies specific fallout messaging values to assist in the identification of mismatching SSAP records or road centerline features.

The examples below shows possible error messages you may receive when a record fails the SSAP to RCL Synchronization QC check. The extended information provides the detected and expected results when verifying that addresses in the SSAP can be properly placed onto a corresponding road segment in the RCL layer.

Here is an image of an example of the SSAP to RCL Synchronization Fallout Report.

Here is an image of an example of the SSAP to RCL Synchronization Fallout Report.

Here is an image of an example of the SSAP to RCL Synchronization Fallout Report.

Here is an image of an example of the SSAP to RCL Synchronization Fallout Report.

There are many examples when completing SSAP to RCL Synchronization QC checks. Below are some examples.

This fallout occurs when an address point is missing an address number, or the address number is malformed. In the example below, an error occurs with the following records:

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout occurs when an address point matches a road segment, fits within its ranges, and matches community/ESN, but can be placed on multiple road segments. This is typically caused by overlapping road ranges. In the example below, the error is identified because the address point can be placed into both road segments.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout occurs when an address point matches a road segment, but can be placed on either side. In the example below, the error is identified because 123 can be placed into both the left and right ranges.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when an address point's street name is not present in the RCL. In this example, the error is identified because Main Street is not present in the RCL layer.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when and address point matches one or more road segments that have no addressable ranges (0-0 on both sides). In this example, the error is identified because Main Street has no addressable ranges.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when an address point matches one or more road segments but falls below all ranges. In this example, the error is identified because 123 falls below all ranges.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when an address point matches one or more road segments, but falls above all ranges. In this example, the error is identified because 123 falls above all ranges.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when an address point matches a road segment and fits within its ranges, but does not match its ESN. In this example, the error is identified because 456 does not match 789.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when an address point matches a road segment and fits within its ranges, but does not match its community. In this example, the error is identified because Springfield does not match Franklin.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when an address point matches a road segment and fits within its ranges, but does not match its ESN or community. In this example, the error is identified because Springfield does not match Frankliin and 456 does not match 789.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

This fallout is produced when an address point matches one or more road segments, but falls between any of the addressable ranges. In this example, the error is identified because 123 does not fall within any of the addressable ranges.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

Here is an image of a SSAP to RCL Synchronization QC check fallout example.

 

For information on using exception codes see Exception Code Basics or to view a list of subchecks completed when running the SSAP to RCL Synchronization QC check and any exception codes for each subcheck, see SSAP to RCL Synchronization Subchecks.