8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions

8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions

Quick Answer: Boundary polygons in Next Generation 9-1-1 are the spatial engines that determine emergency call steering and multi-agency dispatch. The PSAP Boundary polygon layer governs initial call delivery: the Emergency Call Routing Function (ECRF) executes a point-in-polygon calculation against this layer to return the authoritative primary PSAP Session Initiation Protocol (SIP) Uniform Resource Identifier (URI). Distinct from the PSAP Boundary, Emergency Service Boundaries (ESBs) define statutory operational response territories for Law Enforcement, Fire/Rescue, and Emergency Medical Services (EMS), which Computer Aided Dispatch (CAD) systems query to assign responding units or execute secondary selective transfers. All public safety boundary layers must form strict planar partitions—exhibiting zero gaps and zero overlaps across adjacent jurisdictions. Boundary gaps trigger catastrophic fallback to Default Routing, while overlaps trigger ambiguous routing conflicts. Resolving border disputes requires formal Interlocal Agreements (ILAs) and precise edge-matching workflows.

---

1. Boundary Polygons in NG911: The Spatial Determinants of Call Delivery & Dispatch

In legacy circuit-switched E9-1-1, jurisdictional boundaries were represented by abstract text entries in the Master Street Address Guide (MSAG), mapping telephone exchange prefixes (NXX) and house number ranges to numeric Emergency Service Numbers (ESNs). When a caller dialed 9-1-1, the tandem switch used the tabular ESN to select an outgoing physical trunk group.

In Next Generation 9-1-1, physical boundaries are represented as two-dimensional polygon geometries residing within the Next Generation Core Services (NGCS) spatial database. Call routing and unit dispatch decisions are executed through geometric point-in-polygon (PIP) intersections: the caller's geodetic coordinates (latitude/longitude from GPS, Wi-Fi, or cellular positioning) or geocoded civic address point is projected into the spatial plane, and the system determines which polygon encompasses that coordinate.

                     BOUNDARY POLYGON FUNCTIONAL DICHOTOMY

     [CALLER GEODETIC / CIVIC LOCATION OBJECT]
                        │
       ┌────────────────┴────────────────┐
       ▼                                 ▼
[PSAP BOUNDARY POLYGON]        [EMERGENCY SERVICE BOUNDARIES (ESBs)]
- Queried by ECRF via LoST     - Queried by CAD / Secondary Policy
- Determines INTAKE POINT      - Determines FIELD DISPATCH UNITS
- Returns Target PSAP SIP URI  - Law Enforcement Boundary (Police/Sheriff)
- Delivers voice/media stream  - Fire/Rescue Boundary (Engine/Ladder)
                               - EMS Boundary (Paramedic/Ambulance)
                               - Governs Selective Transfers

---

2. The PSAP Boundary Polygon Layer

The PSAP Boundary polygon layer defines the exact geographic territory for which a primary Public Safety Answering Point has operational responsibility for answering incoming 9-1-1 calls.

Operational Call Routing Flow

1. Call Arrival: An emergency call arrives at the Emergency Service Routing Proxy (ESRP) inside the Emergency Services IP Network (ESInet).
2. LoST Query: The ESRP extracts the caller's Location Object from the SIP INVITE (conveyed in a Presence Information Data Format Location Object [PIDF-LO]) and sends a Location-to-Service Translation (LoST, RFC 5222) <findService> request containing the service URN urn:service:sos to the Emergency Call Routing Function (ECRF).
3. Point-in-Polygon Resolution: The ECRF tests the coordinates against the authoritative PSAP Boundary polygon layer.
4. Service URI Extraction: The ECRF extracts the polygon's ServiceURI attribute (e.g., sip:oakville-911@esinet.state.gov) and returns it to the ESRP.
5. Call Delivery: The ESRP uses the SIP URI to route the call signaling and audio/video media stream to the primary PSAP's call handling equipment.

Physical vs. Virtual Answering Boundaries

In consolidated regional authorities or hosted cloud NGCS environments, a single physical facility may answer calls for multiple political jurisdictions, or multiple virtual answering pods may share call loads. Regardless of physical staffing arrangements, each individual PSAP Boundary polygon represents a distinct legal answering entity with its own dedicated routing URI and contingency failover policies.

---

3. Emergency Service Boundaries (ESBs): Law, Fire, and EMS

While the PSAP Boundary directs the incoming call to the telecommunicator, Emergency Service Boundaries (ESBs) define the statutory operational response territories for field emergency units. NENA-STA-006 mandates three primary ESB layers:

┌─────────────────────────────────────────────────────────────────────────────────┐
│                 THE THREE MANDATORY EMERGENCY SERVICE BOUNDARIES                │
│                                                                                 │
│  1. LAW ENFORCEMENT BOUNDARY         2. FIRE / RESCUE BOUNDARY                  │
│     - Municipal Police Precincts        - Municipal Fire Response Districts     │
│     - County Sheriff Patrol Sectors     - Rural Fire Protection Districts       │
│     - State Highway Patrol Troops       - Volunteer Fire Company Zones          │
│                                                                                 │
│  3. EMERGENCY MEDICAL SERVICES (EMS) BOUNDARY                                   │
│     - Fire-Based Paramedic Rescue Zones                                         │
│     - Third-Service Public County Ambulance Districts                           │
│     - Contracted Private Emergency Medical Transport Sectors                    │
└─────────────────────────────────────────────────────────────────────────────────┘

Crucial Distinction: PSAP Boundary vs. ESB

A frequent point of confusion on the ENP examination is the distinction between the PSAP Boundary and ESBs:

• The PSAP Boundary determines where the call rings (call intake).
• The Emergency Service Boundaries determine which field responders are dispatched or which secondary PSAP receives a selective transfer.

In a typical county, a single PSAP Boundary polygon covers the entire county jurisdiction. However, within that single PSAP Boundary, there may exist five municipal police departments, ten rural fire protection districts, three private ambulance zones, and the county sheriff's department. Each discipline requires its own independent, non-overlapping planar polygon layer.

Secondary Policy Routing & Selective Handoffs

When a primary PSAP call taker determines that an incident requires dispatch by an external agency (such as a specialized regional fire dispatch center or university police), NG911 utilizes ESBs to execute automated selective transfers. The ESRP or CAD system evaluates the caller's location against the specific discipline's ESB layer and forwards the call directly to the secondary PSAP's routing URI.

---

4. Strongly Recommended Boundary Layers

Beyond the required PSAP and ESB layers, NENA-STA-006 includes strongly recommended administrative boundaries that support address validation, and recommended reference layers such as cell site and sector locations:

Municipal / Incorporated Community Boundaries

Municipal boundary polygons delineate legal city, town, village, and unincorporated township borders. In public safety addressing, the legal municipal tax community frequently conflicts with the United States Postal Service (USPS) preferred mailing city. For example, a resident's postal mailing address may indicate "Springfield," while their home sits inside the legal municipal boundary of "Pleasant Valley." The Municipal Boundary layer provides authoritative verification inside the Location Validation Function (LVF), ensuring that subscriber addresses validate against the correct municipal tax and dispatch entity rather than an arbitrary postal delivery route.

Cell Site and Cell Sector Location Data

When a wireless caller's device-based or Phase II location is not available at call setup, the carrier can still provide Phase I data: the serving cell site and sector. Legacy E9-1-1 routes these calls with a pseudo-ANI (ESRK or ESRD) assigned to that sector, and NG9-1-1 routing uses the sector location the carrier supplies.

• What NENA-STA-006 includes: Cell site and cell sector location layers are Recommended layers used for mapping and analysis. They are not required routing layers.
• Why sector routing needs care: A sector's radio footprint can cross PSAP boundaries, so the 9-1-1 authority and carrier agree on which PSAP receives each sector's calls, and telecommunicators confirm location and transfer when needed.
• Better location first: Under the FCC's 2024 location-based routing rules, wireless carriers must route voice calls on device-based location when it is timely and accurate enough, which reduces reliance on sector routing.

---

5. Strict Planar Topology Rules for Boundary Polygons

NENA-STA-006 mandates that the PSAP Boundary layer and each individual Emergency Service Boundary layer must form an independent planar partition across the entire service territory.

The Mathematical Planar Partition

A planar partition is a continuous geometric tessellation of two-dimensional space that satisfies four rigid topological rules:

1. Complete Spatial Coverage: Every coordinate location within the territory must fall inside a polygon.
2. Zero Gaps: There can be no voids, holes, or unassigned buffer strips between adjoining polygons.
3. Zero Overlaps: No two adjacent polygons may share interior surface area.
4. Coincident Vertices: Shared boundary lines separating two adjoining agencies must possess identical coordinate vertices snapped together with zero tolerance.

                     BOUNDARY TOPOLOGY DEFECTS IN NG911

      TOPOLOGICAL GAP ERROR                   TOPOLOGICAL OVERLAP ERROR
   (Unassigned Territory Void)               (Ambiguous Jurisdictional Conflict)
┌─────────────────┐ ┌─────────────────┐   ┌───────────────────────────────┐
│                 │ │                 │   │  PSAP A Territory             │
│     PSAP A      │ │     PSAP B      │   │         ┌─────────────────────┼─────────┐
│    Territory    │ │    Territory    │   │         │ OVERLAP ZONE        │ PSAP B  │
│                 │ │                 │   │         │ (Two Competing URIs)│Territory│
└─────────────────┘ └─────────────────┘   └─────────┼─────────────────────┘         │
          ▲                 ▲                       └───────────────────────────────┘
          │                 │                                       ▲
          └────────┬────────┘                                       │
                   │                                                │
             GAP DETECTED!                                   OVERLAP DETECTED!
      Caller location lands here:                    Caller location lands here:
      ECRF finds no PSAP polygon (no route)          ECRF returns multiple routes;
      Call forced to DEFAULT ROUTING                 Triggers policy routing delays

Catastrophic Consequences of Boundary Defects

• Failure Mode 1: Boundary Gaps: If an emergency caller dials 9-1-1 from a location falling inside a topological gap between two PSAP boundary polygons, the ECRF point-in-polygon lookup fails to intersect any valid polygon. The ECRF has no PSAP to return, so the upstream ESRP falls back to Default Routing, sending the call to a distant regional default center. The telecommunicator must then interview the caller, determine the true physical location, and execute a manual transfer, adding minutes of delay during life-threatening emergencies.
• Failure Mode 2: Boundary Overlaps: If an emergency caller is located within an overlapping polygon zone, the ECRF finds two or more competing PSAP boundaries. Depending on the implementation, the ECRF may return one of the competing answers or no reliable answer, so a call can reach the wrong PSAP. Overlaps must be caught by Spatial Interface validation and corrected in the source GIS data.
• Failure Mode 3: Sliver Polygons: Slivers are microscopic boundary gaps or overlaps (often only inches or feet wide) created when two neighboring GIS analysts digitize a shared border independently (such as tracing opposite banks of a river or using different aerial photography base layers). Slivers must be eliminated through automated geometric clean-up tools and coincident vertex snapping.

---

6. Resolving Border Disputes & Cross-Jurisdictional Edge-Matching

Emergency incidents frequently occur directly along municipal, county, or state borderlines: major interstate collisions, multi-vehicle crashes, wildland-urban interface fires, or river rescues. Establishing cross-jurisdictional boundary coordination is a foundational ENP operational responsibility.

Edge-Matching Protocols

• Edge-Matching Defined: The technical process where two adjoining GIS authorities reconcile shared boundary lines and road networks so that coincident vertices align with zero tolerance.
• Coincident Vertex Sharing: Neighboring GIS departments must agree upon a single, authoritative geometric line representing their shared border. When an agency edits its boundary (e.g., following a river channel shift or municipal annexation), both agencies must update their layers simultaneously.
• Road Centerline Edge-Snapping: Where a roadway crosses a jurisdictional border, the road centerlines from both jurisdictions must snap to a single common junction node at the boundary line. Address ranges must be coordinated so that the high address in Jurisdiction A connects seamlessly to the low address in Jurisdiction B without numerical overlaps or voids.

Interlocal Agreements (ILAs) and Governance

Technical GIS alignment is impossible without administrative governance. Public safety authorities must establish formal Interlocal Agreements (ILAs) or Memoranda of Understanding (MOUs):

• Dispute Resolution Framework: The ILA defines an objective procedure for arbitrating boundary disputes. When two municipalities contest an annexation line, the agreement establishes an interim operational dispatch protocol to ensure calls are never dropped while surveying occurs.
• Joint Approval for Edits: Neither agency may unilaterally alter a shared boundary in the NGCS Spatial Interface without written concurrence and simultaneous provisioning by the adjoining agency.
• Neutral Regional Arbitration: In multi-county regions, state 9-1-1 offices or regional councils of government (COGs) often serve as the neutral arbiter and central repository for statewide boundary edge-matching.

---

7. Comparative Table: Public Safety Boundary Layers

---

8. Operational Traps & ENP Exam Watch

• PSAP Boundary vs. ESB Functional Roles: Remember that the PSAP Boundary directs the incoming voice/media stream to the call taker console. The Emergency Service Boundaries (ESBs) direct CAD unit dispatch recommendations and secondary selective transfers. Do not confuse the answering facility with the field responding agency.
• Gaps Cause Default Routing; Overlaps Cause Misroutes: Boundary gaps leave the ECRF with no PSAP to return, so calls fall to Default Routing and a discrepancy report should follow. Boundary overlaps produce conflicting answers that can send calls to the wrong PSAP, so they must be fixed in the GIS data before provisioning.
• Sliver Polygons are Fatal Defects: Even a tiny sliver gap between two boundaries can cause a call located inside it to fail ECRF lookup and drop into default routing.
• Edge-Matching Requires Coincident Nodes: Snapping road centerlines to a jurisdictional border requires a single shared topological node where the centerline intersects the boundary polygon.