GIS Project FAQ
Who is this FAQ For?
This FAQ was designed for 9-1-1 stakeholders that received a request for PSAP boundary data and other information in April of 2024 to support the Colorado 9-1-1 Resource Center's GIS Project.
What is the Resource Center’s GIS Project?
On November 29, 2023, the Colorado Public Utilities Commission designated $500,000 from a retired enforcement mechanism fund to be allocated to the Colorado 9-1-1 Resource Center “for GIS dataset development in preparation for geospatial routing of 9-1-1 calls and further deployment of Next Generation 9-1-1 systems and services.”
To make the best use of this funding, the Resource Center has created a committee of Colorado 9-1-1 GIS subject matter experts and other individuals to develop recommendations for issuance of an RFP and contract to complete this project. The committee is requesting PSAP boundary GIS data files and potentially other information from local agencies to assess the current availability of such data.
What is a GIS data file?
GIS stands for “Geographic Information System”. GIS data files contain spatial and attribute information that can be displayed on a map or analyzed via geoprocessing. They are generally found in two types: shapefile or feature class. A shapefile is a collection of several files with the same name but different file extensions, such as *.shp, *.shx, *.dbf, and *.prj. A feature class is a collection of the same information but held in a geodatabase, such as a file geodatabase ending in .gdb.
A PSAP boundaries GIS data file, for instance, can be used to visualize the shapes and extents of one or more dispatch service areas. That same data file can be used for geospatial routing using geoprocessing, which does not need a map display to function. The latitude and longitude of a caller’s location would be compared against the boundaries to determine which dispatch center should receive the call.
Is this the same as my governing body boundary file?
Possibly, depending on your governing body boundary and whether or not your PSAP serves the same area. For governing bodies that support multiple PSAPs, each PSAP will have a separate GIS boundary data file. Conversely, a PSAP supported by multiple governing bodies will have only one boundary file.
Who might have this file?
You or your GIS/mapping team may have the file. We ask that it be provided in a zipped folder.
If you have no GIS personnel within your agency: This information might be with someone else in your organization like your CAD mapping representative – such as Motorola or your local government’s GIS / IT department. See if they will send it to you. If your local government’s GIS / IT department doesn’t have one, they may be able to help you create the PSAP boundary. Any questions about the PSAP boundary can be sent to the Resource Center where we can provide guidance with the creation of the data.
If you have no GIS personnel and no other source for it: Let us know, reply with “I have no idea how to get this mapping data”. This helps us allocate the funding to places that need the most help.
Who is responsible for creating and maintaining your GIS data and what is their contact information (name, email address)?
Do you have a person on staff who maintains your GIS or do you contract out your GIS to another agency or contractor? Knowing this will help us get in contact with the proper person, agency or contractor to answer any questions we may have regarding the data delivered.
Please send the answers to these questions and the file to: director@co911rc.org
The data will be used solely by the Colorado 9-1-1 Resource Center to gain a better understanding of the strengths and shortcomings for this project and each PSAP. With your help we can begin the next step towards ensuring all calls are delivered to statewide PSAP’s as efficiently as possible.
What is geospatial routing?
Colorado is still using “legacy” 9-1-1 routing, which looks up the calling number in a tabular database to determine which PSAP should receive the call. The basis for the information in that database varies by type of telephone service.
Wireless call routing info is established per each cell tower antenna sector, which may not result in the call being connected to the most appropriate PSAP, particularly if the antenna’s signal coverage overlaps more than one PSAP service area.
Wireline and Static VoIP call routing info is based on the pre-validated address associated with the phone number. Nomadic and Mobile VoIP calls are particularly difficult to route correctly because they rely on the users to continuously update their 9-1-1 locations.
Geospatial routing, on the other hand, routes 9-1-1 calls based on the phone’s actual location. This is achieved by using geoprocessing to determine the device’s X,Y coordinates and compare them to a PSAP boundaries GIS data file. The attribute information of the matching PSAP boundary indicates which PSAP should receive the call. This will generally result in significantly more accurate routing of 9-1-1 calls and therefore less time spent determining and transferring calls to the correct PSAP.
Geospatial routing is an integral part of Next Generation 9-1-1, which is a digital, Internet Protocol-based version of 9-1-1 service based on the NENA i3 standard.
Isn’t the FCC making the wireless carriers adopt geospatial routing nationally? Why do we have to do it, too?
Colorado PSAPs need 9-1-1 network-based geospatial routing in addition to the carrier-level location-based routing for a number of reasons:
Carrier location-based routing is considered a temporary measure until 9-1-1 networks have all implemented geospatial routing. It is more like a PSAP recommendation from the carrier. The 9-1-1 network can choose to use the recommendation or not for performing the actual call routing. The carrier’s PSAP recommendation is based on their internal GIS and processes, for which we have little input and no access.
If there is a problem with the carrier’s process or PSAP recommendation, the 9-1-1 network must still be able to use its own routing decision processes for the call.
By migrating the network-based routing to geospatial routing we can specify and impact standards-based processes and use locally-sourced GIS data for increased accuracy, quality control, and speed of call routing.
The FCC requirement for location-based routing only applies to wireless carriers. Although wireless calls are the majority, there are still a significant number of wireline and VoIP calls.
Geospatial routing is a necessary step in the full implementation of NENA i3-compliant NG9-1-1. Implementing it allows for additional functionality, such as:
Specifying and impacting standards-based processes using locally sourced GIS data for increased accuracy, quality control, and speed of call routing.
In the event of an outage or PSAP abandonment, splitting alternate call routing to more than one PSAP based on the locations of the calls.
Temporarily rerouting calls from a specific geographic area to another destination for special events, such as parades or festivals, or for large critical events.
Reducing compatibility issues with call handling equipment (“CHE”) systems and computer aided dispatch (“CAD”) systems in the future.