TUGIS March 15, 2016 Next Generation 911 Data Management TUGIS 2016

TUGIS March 15, 2016 Agenda Spatial Systems Background Data preparation and maintenance with SpatialMap 911 Questions

TUGIS March 15, 2016 Spatial Systems Associates, Inc. Founded in 1995 Based in Columbia, Maryland GIS and FMIS implementation services company Clients include Federal, State, and Local governments, as well as private organizations Services include: Data Development Application Development Consulting Cloud/Web Hosting Esri Business Partner

TUGIS March 15, 2016 Spatial Systems’ Background in 911 Data Projects Created and maintained street centerline and structure address data for: 8 Maryland Counties 2 Virginia Counties Address verification projects in: Maryland, Pennsylvania, Tennessee 911 data QC, analysis, and modeling for 5 counties in Northern Virginia Developed and refined address maintenance tools over the past 12 years Brought together functionality from various internal toolsets to create SpatialMap 911

TUGIS March 15, 2016 NextGen 911 – Data Management is Critical Data Preparation Emergency Service Boundaries Site Data Street Centerlines Data Management and Synchronization Topology Issues (Cross Jurisdictional) Gaps Overlaps Automated Models for Synchronization Communication Portal Across Jurisdictions

TUGIS March 15, 2016 Key Components of SpatialMap Provide the flexibility to support a variety of addressing systems 2.Improve the address maintenance workflow 3.Provide measurable data quality

TUGIS March 15, 2016 Supporting Multiple Address Systems Grid Based The first and last house numbers for the street are interpolated from a grid. Distance Based All streets share a common starting house number. The ending house number is calculated using a defined address density requirement. Century Based House numbers are set to break at 100 intervals at street intersections. SpatialMap 911 currently supports the following address systems:

TUGIS March 15, 2016 Supporting Address Systems (cont.) SpatialMap 911 supports all address systems by using an address system boundary layer. SpatialMap 911 automatically recognizes which system is appropriate for the street being addressed. Flexibility is increased by allowing the user to select another addressing system when exceptions are encountered.

TUGIS March 15, 2016 Improving the Address Maintenance Workflow Assigns/suggests address ranges to streets Assigns/suggests house numbers to structures SpatialMap 911 improves the address maintenance workflow by reducing errors and increasing efficiencies while the user:

TUGIS March 15, 2016 Improving Address Maintenance Addressing Streets Avoid errors Creating non-unique address ranges Assigning an odd or even numbered range to the wrong side of a street Assigning a street an invalid street name Not allowing for enough addresses along a street (address density). Manual data entry errors Incorrect interpolation from addressing grid Increase efficiency Automatically discover overlapping address ranges Automatically allocate address ranges when splitting a street The grid orientation of a street is stored along with the list of valid street names Automatically update misspelled street names when the master street name list is updated Provide the ability to swap field values such as left zip code and right zip code without manual entry

TUGIS March 15, 2016 Improving Address Maintenance Addressing Structures Avoid errors like: Assigning duplicate house numbers Inconsistent spelling of street names Increase efficiency Simultaneously assign house numbers to structures from multiple feature classes Derive street name and zone field values directly from the street feature Provide the user with access to a subset of fields without the need to access a table or native attribute editing form

TUGIS March 15, 2016 Measurable Data Quality Provide quantitative measure of address data quality Evaluations can be performed on individual streets, subdivisions, or the entire region. Identify potential violations of addressing system rules such as: Overlapping street address ranges Gaps in street address ranges Structures that do not connect to a street via an access line House numbers that are on the wrong side of the street House numbers that are outside of the valid address range of a street House numbers that are out of sequence

TUGIS March 15, 2016 Address Range Overlap Verifies That: Streets with the same name do not contain address ranges that overlap. Street segments have overlapping address ranges

TUGIS March 15, 2016 Access Line Evaluation Verifies That: Structures are snapped to an access line feature Structures are only snapped to a single access line features Access line features connect to connect to a street feature

TUGIS March 15, 2016 Street Name Evaluation Verifies that: Structures contain the same street name attributes as the street feature they are connected to. Corner lot addressed to the wrong street

TUGIS March 15, 2016 Odd and Even House Number Evaluation Verifies that: The even and odd house numbers are on the correct side of a street. Odd address on the even side of street

TUGIS March 15, 2016 House Numbers are Within Range Evaluation Verifies that: The house numbers along a street are within that street’s address range Address is lower then the minimum address for this street.

TUGIS March 15, 2016 House Number Sequence Evaluation Verifies that: The house numbers along a street are sequential House number is out of sequence.

TUGIS March 15, 2016 What are the benefits? Maximize Efficiency  Increase Productivity Maximize Data Integrity  Higher Quality Automated Toolset  Maintain Workflow Data Validation Reports  Help Eliminate & Prevent Errors Product Integration  Uses ArcMap at the Basic, Standard, Advanced license levels Flexibility  Use suggested address ranges or override system suggestions

TUGIS March 15, 2016 Questions? Patrick McLoughin, GISP