Skip to content

NG911 - build GIS representation of cell-sector routing spreadsheets #561

Description

@eneemann

Benefit

A GIS representation of cell tower sector routing can clarify the way cell tower sectors are configured to route wireless calls so the PSAPs have a better understanding and can make better decisions when PSAP boundaries change. When a cellular 911 call is made and the caller's location can't be determine within 1.5 seconds, the call is routing with a fallback method based on the cell tower and sector that the call is hitting. Right now, those sectors are configured to route to specific PSAPs based on spreadsheets. A GIS representation of these sheets would make them much easier to understand and facilitate decisions to change routing when misroutes occur or PSAP boundaries change. Demonstrating this analysis to PSAPs may help motivate them to analyze their areas, make adjustments, and decrease call transfers. UGRC could perform PSAP-level analysis upon request with an SBA.

Acceptance Criteria

  • Build demo GIS polygon layer that represents sample of cell tower sectors and PSAPs they route to in fallback scenarios
  • Acquire and add ECaTS call locations for a given period of time
  • Perform analysis of calls by cell sector and PSAP, ID misroutes, show where calls in sector primarily originate
  • Determine number/percentage of calls within City PSAP boundaries that would fall in UHP buffer
  • Present analysis capability to group of PSAP directors

Notes

  • Collect cell-sector routing sheets from all Utah PSAPs/carriers with UCA/Motorola assistance
  • Combine cell-sector routing sheets into 1 dataset
  • Plot coordinates of each cell tower/sector
  • Build polygon representation of sectors w/ routing attributes (azimuth, beamwidth)

Risks

  • Carriers might not be willing to share all routing sheets
  • Routing sheets may have different schemas and information
  • Poor data quality may render this task infeasible

Issue Reference

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestuncommittedThis feature has not been committed to the plan

Fields

No fields configured for Feature.

Projects

Status
Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions