How Caller Location Guides NG9-1-1 Call Routing
When someone calls 9-1-1, getting the call to the right Emergency Communications Center (ECC) or Public Safety Answering Point (PSAP) is one of the first critical steps in the emergency response process.
In a Next Generation 9-1-1 (NG9-1-1) environment, that decision increasingly depends on one essential piece of information: the caller’s location.
Unlike legacy 9-1-1 infrastructure that has traditionally relied heavily on telephone numbers, static databases, and predefined routing relationships, NG9-1-1 introduces location-based call routing. The caller’s location can be evaluated against authoritative geographic information system (GIS) data to determine which PSAP should receive the emergency call.
For public safety agencies evaluating emergency call routing software or planning a transition from legacy 9-1-1 infrastructure, understanding this relationship between location, GIS, and routing is important.
What Is NG9-1-1 Call Routing?
NG9-1-1 call routing is the process of determining where an emergency call should be delivered within an IP-based 9-1-1 environment.
Under the NENA i3 architecture, the Emergency Call Routing Function (ECRF) uses the location associated with the emergency call and provisioned GIS service-boundary information to determine the appropriate emergency service or PSAP URI for routing.
In simple terms:
Where is the caller? → Which agency serves that location? → Where should the call be routed?
That sounds straightforward, but making that determination reliably requires multiple components to work together.
The caller location must be available in a usable format. The GIS data defining PSAP and emergency service boundaries must be accurate and current. And the emergency communications platform must be able to use those inputs to make the appropriate routing decision.
This is why NG9-1-1 call routing is more than simply replacing one piece of legacy equipment with newer technology. It depends on a connected ecosystem of location data, GIS, standards-based systems, and operational processes.
How Does Caller Location Guide Emergency Call Routing?
In NG9-1-1, caller location can be represented as a civic location, such as a street address, or as a geodetic location represented by geographic coordinates.
The ECRF uses that location to evaluate which emergency service or PSAP boundary applies.
For example, imagine a wireless 9-1-1 call originating near the border between two PSAP jurisdictions.
Rather than relying on legacy selective-routing mechanisms and static database relationships, NG9-1-1 enables routing decisions to be based on the location associated with the emergency call and authoritative service-boundary data.
That ability is one of the fundamental shifts from legacy 9-1-1 infrastructure toward NG9-1-1.
Location becomes part of the decision-making process.
Why Is GIS Data So Important to Caller Location Routing?
Location-based routing is only as reliable as the data supporting it.
NG9-1-1 systems rely on authoritative GIS datasets that can include:
- PSAP service boundaries
- Emergency service boundaries
- Road centerlines
- Site and structure address points
- Other locally maintained geographic information
When the location associated with a 9-1-1 call is evaluated, the system uses this GIS information to determine which PSAP or emergency service area applies.
That makes data quality a mission-critical consideration.
Gaps between PSAP boundaries can create locations where a clear route cannot be determined. Overlapping boundaries can create ambiguity about which PSAP should receive the call. Address discrepancies and outdated GIS information can create additional challenges for location validation and routing.
For agencies upgrading legacy 9-1-1 infrastructure, GIS readiness should therefore be considered alongside network and technology readiness.
What Are the ECRF and LVF?
Two important functions within NG9-1-1 Core Services are the Emergency Call Routing Function (ECRF) and the Location Validation Function (LVF).
The ECRF uses location information to determine the appropriate emergency service or PSAP for a location.
The LVF helps determine whether a civic location is valid against the authoritative GIS information provisioned for the NG9-1-1 environment.
Together, these capabilities help establish confidence that location information can be understood by the NG9-1-1 system and used appropriately for emergency call routing.
For agencies evaluating PSAP solutions or emergency communications platforms, this means the conversation should extend beyond whether a system can simply receive an emergency call.
Agencies should understand how location is validated, how routing decisions are made, what GIS information those decisions depend on, and how that data will be maintained over time.
What Should Agencies Look for in Emergency Call Routing Software?
There is no single feature that determines whether an emergency call routing solution is ready for NG9-1-1.
Agencies and 9-1-1 authorities should consider how the technology fits into their broader NG9-1-1 environment.
Important questions include:
Does the solution support standards-based NG9-1-1 architecture?
Interoperability becomes increasingly important as agencies connect multiple systems, vendors, networks, and jurisdictions.
How does the solution use caller location?
Agencies should understand how civic and geodetic location information is processed and how it contributes to routing decisions.
How is GIS data incorporated?
Accurate PSAP boundaries and other authoritative GIS datasets are foundational to location-based routing.
How are GIS changes maintained and provisioned?
NG9-1-1 GIS is not a one-time migration effort. Streets and addresses change, service boundaries evolve, and jurisdictions update their data. Agencies therefore need defined processes for maintaining authoritative GIS data and provisioning current data to the ECRF and LVF.
How resilient is the routing environment?
9-1-1 is mission-critical infrastructure. Availability, redundancy, security, performance, and operational continuity should all be part of the evaluation.
How well does the platform integrate with the broader public safety ecosystem?
Call routing is one step in an emergency response workflow that can also include call handling, mapping, CAD, dispatch, and responder systems.
How Is NG9-1-1 Routing Different From Legacy 9-1-1 Infrastructure?
Legacy 9-1-1 systems were designed for a communications environment dominated by landline telephones and circuit-switched networks.
Today, emergency calls can originate from mobile phones, VoIP services, enterprise communications systems, connected devices, and other technologies.
NG9-1-1 creates an IP-based foundation designed to accommodate this changing communications environment while providing more flexible ways to use location and data throughout an emergency.
One of the most significant differences is the move toward geospatially controlled call routing.
Rather than relying primarily on static tabular relationships, NG9-1-1 can use the location associated with the emergency call and compare it with authoritative GIS information.
For PSAPs replacing legacy infrastructure, this makes GIS part of the operational technology foundation—not simply a map displayed after the call arrives.
Location Is the Connection Between the Call and the Response
The goal of NG9-1-1 is not simply to modernize technology.
It is to improve how information moves through the emergency response workflow.
Caller location provides a critical connection between an emergency call and the public safety organizations responsible for responding to it.
Accurate location can help determine where a call should be routed. Authoritative GIS data provides the geographic context needed to make that decision. Once the call reaches the PSAP, location intelligence can continue supporting call takers, dispatchers, and responders as they work to understand where the emergency is occurring and how to respond.
That is why agencies evaluating emergency call routing software, PSAP solutions, or broader emergency communications platforms should look beyond the routing engine itself.
The more important question is:
Can the entire location ecosystem reliably deliver the right location data to the right systems at the right point in the emergency response process?
As public safety agencies continue moving from legacy 9-1-1 infrastructure to NG9-1-1, answering that question will be fundamental to building a more connected, resilient, and location-aware emergency response environment.
