8.1 NG911 GIS Data Layers: Road Centerlines & Address Points

8.1 NG911 GIS Data Layers: Road Centerlines & Address Points

Quick Answer: In Next Generation 9-1-1 (NG911), Geographic Information Systems (GIS) become the authoritative core routing engine, completely replacing legacy tabular Master Street Address Guides (MSAG) and Selective Routing Databases (SRDB). Under the NENA Standard for NG9-1-1 GIS Data Model (NENA-STA-006, current edition NENA-STA-006.3-2026), provisioned layers use WGS84 geographic coordinates (EPSG:4326) and carry NENA Globally Unique Identifiers (NGUIDs, formatted urn:emergency:uid:gis:[Layer]:[Local Unique ID]:[Agency Identifier]). The required layers are Road Centerlines (with parity, address ranges, and elevation levels), Site/Structure Address Points (SSAP, including sub-addresses), the PSAP Boundary (governing primary call routing), Emergency Service Boundaries (ESBs for law, fire, and EMS), and the Provisioning Boundary (defining each data provider's area of authority). Other layers, such as county and incorporated municipality boundaries, are strongly recommended or recommended.

---

1. The Paradigm Shift: From Tabular MSAG to Spatial Geospatial Routing

For nearly four decades, Enhanced 9-1-1 (E9-1-1) relied on a tabular, text-based data architecture to route emergency calls and deliver location data to telecommunicators. In that legacy circuit-switched environment:

• The Master Street Address Guide (MSAG) stored tabular alphanumeric street names, house number ranges, parity indicators, and community names.
• Each MSAG record mapped directly to an Emergency Service Number (ESN) representing an Emergency Service Zone (ESZ).
• Central Office switches and E9-1-1 Selective Routers indexed the incoming calling number (ANI) against the Selective Routing Database (SRDB) to locate the ESN and steer the call over a dedicated CAMA or PRI trunk group to the primary PSAP.

While functional for static wireline telephony, tabular routing suffered from severe structural limitations. It possessed no intrinsic concept of physical geography, ground truth geometry, or spatial relationships. Tabular systems could not dynamically route wireless emergency calls based on real-time geodetic coordinates (latitude and longitude), nor could they natively resolve complex three-dimensional campus structures, vertical high-rises, or mobile VoIP endpoints.

┌─────────────────────────────────────────────────────────────────────────────────┐
│                     LEGACY E9-1-1 TABULAR ROUTING ARCHITECTURE                   │
│                                                                                 │
│  Subscriber ANI ──► [Selective Routing Database] ──► ESN ──► Physical Trunk Group│
│                             │                                                   │
│                             ▼                                                   │
│                 [MSAG Text Table: Ranges & ESN]                                 │
└─────────────────────────────────────────────────────────────────────────────────┘
                                         │
                                         ▼ [MIGRATION TO NG911]
┌─────────────────────────────────────────────────────────────────────────────────┐
│                      NG911 SPATIAL CORE ROUTING ARCHITECTURE                     │
│                                                                                 │
│  Caller Location ──► [Emergency Call Routing Function] ──► SIP URI (PSAP Route) │
│  (GML / Civic)                     │                                            │
│                                    ▼                                            │
│                     [Authoritative GIS Polygon Layers]                          │
│                 - Road Centerlines   - Address Points (SSAP)                    │
│                 - PSAP Boundaries    - Emergency Service Boundaries             │
└─────────────────────────────────────────────────────────────────────────────────┘

In Next Generation 9-1-1, GIS transitions from a secondary visualization display in Computer Aided Dispatch (CAD) to the primary, mission-critical infrastructure for call routing and location validation. The Emergency Call Routing Function (ECRF) and the Location Validation Function (LVF) inside Next Generation Core Services (NGCS) execute real-time spatial calculations directly against authoritative GIS layers. A 9-1-1 call is routed by performing a geometric point-in-polygon (PIP) calculation: the caller's geodetic coordinates or geocoded civic address point is plotted in spatial coordinates and intersected with the authoritative PSAP Boundary polygon layer to instantly return the receiving agency's Session Initiation Protocol (SIP) Uniform Resource Identifier (URI).

---

2. NENA NG9-1-1 GIS Data Model Standard (NENA-STA-006)

To ensure complete spatial interoperability across municipal, county, state, tribal, and national boundaries, NENA published NENA-STA-006, the NENA Standard for NG9-1-1 GIS Data Model (first issued as NENA-STA-006.1-2018; the current edition is NENA-STA-006.3-2026). This standard defines the exact database schemas, required attribute fields, domain values, and spatial constraints necessary for public safety GIS datasets.

Global Model Requirements

1. Coordinate Reference System (CRS): All spatial data provisioned to NG911 core services must be delivered in unprojected geographic coordinates based on the World Geodetic System 1984 (WGS84) datum, cataloged under EPSG code 4326. Coordinates are expressed in decimal degrees, stored with enough precision to preserve the accuracy of the source data (six decimal places is about 0.1 meter). Local GIS authorities may maintain their internal source data in localized State Plane Coordinate Systems (SPCS) or Universal Transverse Mercator (UTM) projections to satisfy public works surveying workflows, but data must be transformed to WGS84 EPSG:4326 before ingestion into the NG911 core.
2. NENA Globally Unique Identifier (NGUID): Every feature (every road segment, address point, and boundary polygon) carries a globally unique identifier. Since NENA-STA-006.2, the NGUID is a URN built from a layer indicator, a locally unique ID, and the agency identifier (typically the agency's domain name): urn:emergency:uid:gis:[Layer Indicator]:[Local Unique ID]:[Agency Identifier] For example, a road centerline segment with local ID 84920 maintained by oakvillecounty.gov combines the road centerline layer indicator, 84920, and oakvillecounty.gov. Pairing the local ID with the agency identifier keeps identifiers unique when regional and statewide datasets merge.
3. Date and Lifecycle Tracking: Every feature requires ISO 8601 compliant UTC timestamp attributes: DateUpdate (date and time the record was last modified) and EffectiveDate (date and time the change takes operational effect in routing engines).
4. Discrepancy Agency Attribution: Every record must identify the DiscrpAgID (Discrepancy Agency Identifier), establishing which public safety authority or GIS department is legally responsible for remediating data discrepancies reported by NGCS engines.
5. CLDXF Alignment: Attribute naming and field structures align with NENA-STA-004, the NENA Standard for Civic Location Data eXchange Format (CLDXF), which adapts the federal FGDC and IETF RFC 5139/6848 standards into granular civic address components (e.g., separating prefix directionals, street names, street types, and sub-address attributes into discrete database columns).

---

3. Required NG911 GIS Data Layers

NENA-STA-006 designates a small set of layers as Required. The four operational layers below drive routing and validation, and a fifth required layer, the Provisioning Boundary, defines the area each data provider is authoritative for. Without these layers, the ECRF cannot route calls spatially and the LVF cannot validate addresses:

┌─────────────────────────────────────────────────────────────────────────────────┐
│                      REQUIRED NG911 GIS ROUTING LAYERS                          │
│                                                                                 │
│  1. ROAD CENTERLINES (RCL)           2. SITE/STRUCTURE ADDRESS POINTS (SSAP)    │
│     - Linear polyline network           - Discrete building points              │
│     - Left/Right address ranges         - Primary access points / curb cuts     │
│     - Parity (Odd, Even, Both, Zero)    - Sub-addresses (Floor, Suite, Unit)    │
│     - Z-elevation levels (-1, 0, +1)    - Used by LVF and CAD pinpoint geocode  │
│                                                                                 │
│  3. PSAP BOUNDARY                    4. EMERGENCY SERVICE BOUNDARIES (ESBs)     │
│     - Planar partition polygon          - Distinct disciplinary polygons        │
│     - Zero gaps, zero overlaps          - Law Enforcement Boundary              │
│     - Direct ECRF SIP URI routing       - Fire/Rescue Boundary                  │
│     - Governs primary call intake       - Emergency Medical Services (EMS)      │
└─────────────────────────────────────────────────────────────────────────────────┘

Required, Strongly Recommended & Recommended Layers

NENA-STA-006 sorts layers into three categories:

• Required Layers: Road Centerlines, Site/Structure Address Points, PSAP Boundary, Emergency Service Boundaries (law, fire, EMS), and the Provisioning Boundary.
• Strongly Recommended Layers: Administrative boundaries such as state, county, incorporated municipality, and unincorporated community boundaries, which help resolve municipal versus postal community names during validation, along with supporting alias and landmark tables.
• Recommended Layers: Reference layers such as railroad centerlines, hydrology, cell site and cell sector locations, and mile markers. They support CAD mapping and situational awareness but are not provisioned into the LVF or ECRF.

---

4. Road Centerlines (RCL) Deep Dive

Road Centerlines represent the physical centerline of all traveled roadways, public thoroughfares, private roads, and shared access easements. In NG911, centerlines serve dual operational functions: validating civic address ranges in the LVF when a specific address point does not exist, and powering Computer Aided Dispatch (CAD) vehicular network routing engines.

                  ROAD CENTERLINE TOPOLOGY & DIGITIZATION

  CORRECT DIGITIZATION DIRECTION (Low to High Address Numbers)
  From-Node (100) ──────────────────────────────────────────► To-Node (198)
                  [Left Side: ODD]    [Right Side: EVEN]
                  FromAddr_L = 101    FromAddr_R = 100
                  ToAddr_L   = 199    ToAddr_R   = 198
                  Parity_L   = O      Parity_R   = E

  GRADE-SEPARATED CROSSING (Overpass / Underpass - NO NODE)
        Highway Overpass (Elev = 1)
  ──────────────────────┼──────────────────────► (Continuous segment, Elev = 1)
                        │
                        │ Surface Road (Elev = 0)
                        ▼ (Continuous segment, Elev = 0; NO INTERSECTION NODE)

Critical Road Centerline Attributes

• Address Ranges: Four distinct numeric attributes define the address span along the segment: FromAddr_L (start of left side), ToAddr_L (end of left side), FromAddr_R (start of right side), and ToAddr_R (end of right side).
• Parity Attributes: Parity_L and Parity_R define address parity for each side of the roadway using standard NENA domain values:
  • O (Odd): Segment side contains exclusively odd-numbered addresses (e.g., 101, 103, 105).
  • E (Even): Segment side contains exclusively even-numbered addresses (e.g., 100, 102, 104).
  • B (Both): Segment side contains both odd and even numbers (common in irregularly numbered rural areas).
  • Z (Zero / None): Segment side possesses no addressable structures (e.g., alongside a national park or body of water).
• Direction of Digitization & The Inversion Trap: In GIS geometry, the "Left" and "Right" sides of a vector are determined by looking down the line from the From-Node toward the To-Node. NENA data model guidance and most state GIS standards expect road centerlines to be digitized in the direction of increasing address numbers (from low to high), which keeps left and right ranges consistent:
  • If digitized correctly, FromAddr_L=101 and ToAddr_L=199 align with the actual physical left side.
  • The Digitization Trap: If an analyst accidentally digitizes a line segment in reverse (from high address to low address), the mathematical Left and Right sides are inverted. The LVF and CAD systems will assume odd addresses sit on the even side of the roadway, causing address validation rejections and directing emergency responders to the incorrect side of a divided highway.
• CLDXF Street Name Elements: Roadway names must be parsed into discrete fields to enable exact string matching: PreDir (Prefix Directional, e.g., "N"), PreTyp (Prefix Type, e.g., "Avenue"), PreSep (Prefix Separator, e.g., "of the"), StreetName ("Main"), PostTyp (Street Suffix/Type, e.g., "St"), PostDir (Postfix Directional, e.g., "NW"), and PostMod (Postfix Modifier).
• One-Way Indicators: Attribute values govern legal vehicular flow: B (Two-way travel permitted), FT (One-way travel from From-Node to To-Node), or TF (One-way travel from To-Node to From-Node). This attribute is critical for CAD dynamic unit routing, preventing algorithms from directing fire apparatus wrong-way down one-way streets.
• Speed Limit & Impedance: Posted speed limits and travel impedance values allow CAD routing engines to calculate accurate estimated times of arrival (ETA) and recommend the fastest response units.
• Integer Z-Elevation Levels: Assigned to line endpoints to model relative grade separations: -1 for tunnels/sub-grade, 0 for surface at-grade roadways, and +1 or higher for elevated overpasses and bridges. Grade-separated crossings must not be split into intersection nodes. If an analyst places an intersection node where a highway overpass crosses a surface street, CAD vehicular routing algorithms will assume vehicles can make an impossible 90-degree turn from the ground street directly onto the overhead bridge deck.

---

5. Site/Structure Address Points (SSAP) Deep Dive

Site/Structure Address Points (SSAP) are discrete point geometries representing individual addressable physical locations. In legacy E9-1-1, addresses were approximated by linear interpolation along a road centerline range. For example, address 150 Main St was mathematically placed at the exact 50% midpoint of a 100–200 centerline segment, even if the actual structure was located near the far end of the block. In NG911, SSAPs provide exact, unambiguous location validation and dispatch precision.

               SSAP PLACEMENT & SPATIAL VALIDATION

   ┌──────────────────────────────────────────────────────────────┐
   │                                                              │
   │   [Structure Centroid SSAP]                                  │
   │   - Placed on primary building roof footprint                │
   │   - Captures Sub-addresses: Floor 3, Suite 305               │
   │                                                              │
   │              ┌─────────────────────────────┐                 │
   │              │ Primary Structure Footprint │                 │
   │              └─────────────────────────────┘                 │
   │                             │                                │
   │                             │ Long Private Driveway          │
   │                             ▼                                │
   │   [Site Access Point SSAP]                                   │
   │   - Placed at curb cut / vehicular ingress                   │
   │   - Guides emergency apparatus to property entrance          │
   │                                                              │
   └─────────────────────────────┬────────────────────────────────┘
                                 ▼ Curb Cut
  ═══════════════════════════════╧═════════════════════════════════ Road Centerline
   From-Node (100) ───────────────────────────────► To-Node (198)

Point Placement Methodologies

1. Structure Centroid: The point is placed in the center of the primary building roof footprint. This is standard for single-family residences, standalone commercial buildings, and urban structures where the building sits adjacent to the roadway.
2. Site Access Point / Driveway Entrance (Curb Cut): The point is placed at the driveway entrance or curb cut where an emergency response vehicle must enter the property from the public road network. This placement is mandatory for large rural parcels, gated communities, industrial complexes, or properties with long winding driveways. Placing the point only on the distant building centroid could cause CAD routing engines to guide apparatus to an impassable rear fence or adjacent parcel rather than the legitimate driveway entrance.
3. Sub-Address Points: For multi-tenant complexes, strip malls, high-rise office towers, and apartment complexes, individual address points are generated for each discrete tenant space, capturing CLDXF sub-address attributes: Building (BLDG), Floor (FLR), Unit (UNIT), Room (ROOM), and Seat (SEAT).

---

6. Complementary Layers: Landmark Points & Points of Interest (POI)

Many high-density emergency calls originate from locations that lack standard numeric street addresses: athletic stadiums, municipal parks, public beaches, highway rest areas, monuments, hiking trailheads, and amusement facilities. The Landmark Point layer correlates common place names (e.g., "Centennial Olympic Park" or "Oakville High School Football Stadium") with geographic coordinates and designated access gates, allowing instant CAD geocoding when a stressed caller cannot provide a numeric street address.

---

7. Comparative Architecture: Road Centerlines vs. Address Points

---

8. Operational Traps & ENP Exam Watch

• Digitization Direction Inverts Parity: Road centerlines are expected to be digitized in the direction of increasing address numbers. If a line is digitized backwards, the Left and Right attributes are inverted in the database, causing the LVF and CAD systems to assign even addresses to the odd side of the road.
• Z-Elevation vs. Vertical Height Above Ellipsoid: Do not confuse the integer Elevation attribute on a Road Centerline (-1, 0, +1) with the 3D Z-coordinate (vertical ellipsoidal height / HAE in meters) of a geodetic location object. Centerline Z-elevation is an abstract topological indicator used to separate grade-separated overpasses from surface streets; it is not a measurement of altitude.
• SSAP Placement for Rural Driveways: On rural parcels with long driveways or gated campuses, the SSAP must be placed at the Site Access Point (curb cut) or dual-pointed (both centroid and access point) to ensure emergency vehicles are guided to the driveway rather than navigating toward an inaccessible building centroid across open fields or security fences.