Study guide

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

NENA Emergency Number Professional ENP

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the NENA ENP Exam

2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture

1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1

3 Chapter 2: Modern Location Technologies & MLTS

2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act

4 Chapter 3: NG911 i3 Core Network & Security

3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow

5 Chapter 4: NG911 Location Services & Call Routing

4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements

6 Chapter 5: Public Safety Radio, Broadband & FirstNet

5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services

7 Chapter 6: Call Processing, Accessibility & Protocol Systems

6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment

8 Chapter 7: Computer Aided Dispatch & Information Systems

7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents

9 Chapter 8: GIS for Next Generation 9-1-1

8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management

10 Chapter 9: Cybersecurity & CJIS Compliance

9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning

11 Chapter 10: Telecommunications Policy, Funding & Civil Rights

10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws

12 Chapter 11: PSAP Governance, Strategy & Facility Design

11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning

13 Chapter 12: Power Redundancy, COOP & Disaster Recovery

12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases

14 Chapter 13: Emergency Incident Management & NIMS/ICS

13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS

15 Chapter 14: Procurement, Contracts & Financial Management

14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management

16 Chapter 15: Staffing Models, Scheduling & Wellness

15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD

17 Chapter 16: Training, CTO Coaching & Quality Assurance

16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service

18 Chapter 17: Employee Relations, Labor Standards & Legal Protections

17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act

19 Chapter 18: Records Governance, Liability & Public Relations

18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach

20 Chapter 19: Recruiting, Hiring, Compensation & Retention

19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning

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

Key Takeaways Explain This Topic AI

In NG911, boundary polygons are the spatial determinants of emergency call delivery and field dispatch, with the PSAP Boundary determining initial call intake and Emergency Service Boundaries (ESBs) determining discipline-specific response (Law, Fire, EMS).

The PSAP Boundary layer is queried in real time by the Emergency Call Routing Function (ECRF) using the Location-to-Service Translation (LoST) protocol, performing point-in-polygon calculations to return the primary answering point's SIP URI.

All authoritative boundary layers must form strict planar partitions across the service region, adhering to zero-gap and zero-overlap topological constraints with shared coincident vertices between adjacent jurisdictions.

A boundary gap leaves the ECRF with no PSAP polygon to return, so the call falls to default routing and the gap should be reported and fixed; an overlap produces conflicting answers that can misroute calls and must be corrected in the source GIS data.

Neighboring public safety authorities must resolve boundary disputes and border discrepancies through formal Interlocal Agreements (ILAs) and edge-matching workflows, including snapping road centerlines to common border junction nodes.

Last updated: September 2026

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

Call Arrival: An emergency call arrives at the Emergency Service Routing Proxy (ESRP) inside the Emergency Services IP Network (ESInet).

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).

Point-in-Polygon Resolution: The ECRF tests the coordinates against the authoritative PSAP Boundary polygon layer.

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.

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:

Complete Spatial Coverage: Every coordinate location within the territory must fall inside a polygon.

Zero Gaps: There can be no voids, holes, or unassigned buffer strips between adjoining polygons.

Zero Overlaps: No two adjacent polygons may share interior surface area.

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

Boundary Layer Governing Standard Querying Engine Primary Operational Purpose Planar Partition Mandate

PSAP Boundary NENA-STA-006 ECRF (LoST) Determines primary 9-1-1 call answering point (returns SIP URI) Mandatory (Zero gaps, zero overlaps)

Law Enforcement Boundary NENA-STA-006 CAD / ESRP Determines primary police/sheriff dispatch and selective transfer Mandatory (Zero gaps, zero overlaps)

Fire/Rescue Boundary NENA-STA-006 CAD / ESRP Determines fire station response districts and alarm boxes Mandatory (Zero gaps, zero overlaps)

EMS Boundary NENA-STA-006 CAD / ESRP Determines ambulance transport service and paramedic response Mandatory (Zero gaps, zero overlaps)

Cell Site / Sector Location NENA-STA-006 CAD mapping & analysis Shows the serving cell site and sector for wireless calls; sector routing is agreed with carriers Recommended

Municipal Boundary NENA-STA-006 LVF (LoST) Disambiguates civic address tax communities vs postal delivery cities Strongly Recommended

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.