GIS Strategic Plan Summary

Stages I and II
February 7, 2011

Appendix 4
Addressing Data Development Plan, September 13, 2010
 Montgomery County Planning Department
Montgomery County, Maryland
GIS Strategic Plan Update
Phase II
Addressing Data Development Plan

FINAL
September 13, 2010

Submitted to:

Richard Debose, Chief

Research and Technology Center
Montgomery County Department of Park and Planning
Maryland National Capital Park and Planning Commission
Dedrick Annex
1400 Spring Street. Suite 500
Silver Spring, Maryland 20910-2748
301.650.5603

Submitted by

KCI Technologies, Inc.

36 Ridgebrook Rd
Sparks, MD 21152
 VERSION CONTROL

Version Date Description

1.0 April 19, 2008 Draft

2.0 September 13, 2010 Final

 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

TABLE OF CONTENTS

INTRODUCTION ........................................................................................................................................ 1
DATA DEVELOPMENT PLAN ................................................................................................................. 2
ACTIVITY 1 PROJECT MANAGEMENT AND COORDINATION ................................................................... 2
ACTIVITY 2 FINALIZE DATA MODEL...................................................................................................... 2
ACTIVITY 3 UPDATE ADDRESS DATA MAINTENANCE APPLICATIONS ................................................... 2
ACTIVITY 4 DEVELOP ENHANCED ADDRESS POINTS LAYER ................................................................. 3
ACTIVITY 5 DEVELOP BUILDING LAYER ................................................................................................ 5
ACTIVITY 6 IMPLEMENT UNIT NUMBERING ........................................................................................... 5
ACTIVITY 7 REVIEW ALL BUILDINGS WITH MULTIPLE ADDRESS POINTS ................................................. 6
ACTIVITY 8 IMPLEMENT REPLICATED SERVERS..................................................................................... 6
ACTIVITY 9 IMPLEMENT GIS PORTAL .................................................................................................... 7
ACTIVITY 10 CENTERLINE MODERNIZATION ...................................................................................... 7
ACTIVITY 11 UPDATE PUBLIC SAFETY DATA PROVISIONING.............................................................. 8
ACTIVITY 12 IMPLEMENT ADDRESSING ONLINE TOOLS...................................................................... 8
WORKPLAN—SCHEDULE ...................................................................................................................... 9
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

INTRODUCTION

Montgomery County, Maryland and the Maryland-National Capital Park and Planning
Commission Planning Department have undertaken an update of the County GIS
Strategic Plan. Phase I of the plan update recommended that the addressing data
maintenance workflows be improved and streamlined and that a plan be developed to
enhance critical address data resources to support Public Safety and other key County
GIS requirements.

Under Phase II, the existing and proposed Workflows have been documented and
reviewed with the County project team. New workflows include streamlining address
assignment, error reporting, address data maintenance, and data publishing. The
addressing workflows and results of Phase II Tasks 1 and 2 are presented in two
documents:

“Phase II Task 1&2 Final_041222010-2.pdf”

“Addressing_Workflows_04122010.pdf”

This document describes all of the activities required to enhance address, building, and
centerline data and to support the streamlined data maintenance process and to effectively
publish data and support applications. The plan is organized into 12 activities with
subtasks defined within the activities.

1. Project Management and Coordination

2. Finalize Data Model
3. Update Address Data maintenance Applications
4. Develop Enhanced Address Points Layer
5. Develop Merged Building Layer
6. Implement Unit Numbering
7. Review all buildings with multiple address points
8. Implement Replicated Servers
9. Implement GIS Portal
10. Centerline Modernization
11. Update Public Safety Data Provisioning

The activities will be accomplished by teams consisting of County and Planning

Department staff and KCI Technologies as appropriate for each activity. Consulting
support will be utilized on specific tasks as needed. The Cities of Gaithersburg and
Rockville will participate in the activities as needed.

Each activity and subtasks are described in the following sections, followed by a project
workplan/schedule.

Page 1
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

DATA DEVELOPMENT PLAN

Activity 1 Project Management and Coordination

The Addressing Data Development project will be managed by a team consisting of the
Planning Department Research and Technology Center, the Montgomery County
Department of Technology Services (DTS), the Department of Fire and Rescue Services,
the ECC CAD Manager, and the consultant, KCI Technologies. The oversight of the
project will be provided by the Chief of the Research and Technology Center. Key
project management tools will include the team organization chart, the establishment of
work groups for specific technical areas, a Communication Plan, a Workplan, and
regularly scheduled status meetings. KCI will be responsible for the development of all
project documents, with review and input by the team members.

1.1 Project Initiation and Kick-off Meeting

1.2 Establish Project Team and Work Groups
1.3 Create Communication Plan and Project Web Site
1.4 Update and Refine Workplan
1.5 Bi-weekly Status Meetings

Activity 2 Finalize Data Model

Recommendations for data model enhancements were made as part of the GIS Strategic
Plan Update Phase II database enhancements task. Some of the recommendations have
been implemented by the Planning Department RTC GIS Team. A detailed review of all
recommended changes should be made with the project team and a final design
completed. Management and integration of address data resources by Gaithersburg and
Rockville should be considered. A development database should be created to support the
data development process. The final additional modifications should be made to the
development model.

2.1 Hold Data Model Review Worksession

2.2 Finalize requirements/changes
2.3 Identify application impacts
2.4 Update data model if necessary
2.5 Implement data model changes

Activity 3 Update Address Data Maintenance Applications

The current address data maintenance tools and environment must be updated for the
revised data model. Review existing functionality and redesign to manage the additional

Page 2
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

address data relationships and status and tracking fields. Modify the application as
needed and test. Develop automated QA/QC tools as well as a manual review process.
Design and implement the versioned editing environment to support all editing and
QA/QC steps.

3.1 Determine Requirements for application changes

3.2 Document addressing procedures
3.3 Develop addressing QA/QC Plan
3.4 Design application changes
3.5 Implement application changes
3.6 Test application
3.7 Finalize changes
3.8 Revised applications into production

Activity 4 Develop Enhanced Address Points Layer

The current address points layer in the Master Address Repository (MAR) is not
complete and has not been validated against other address data sources. In its current
state, it does not provide the accuracy required to support the call-taking function or other
emergency response and public safety applications. There are several sources of address
data that may be used for validation to ensure that the MAR is as complete as possible.
These sources include the building layer that contains address information, and several
database including Motor Vehicle Registration, Voter Registration, Solid Wastes,
Permitting, MCPS, and WSSC. Any dataset that is selected for use may have private or
confidential information such as customer name or billing information removed from it
so that only the address portion is available for the validation process. Final checks will
include the USPS, the centerline address ranges, and the parcel/lot address labels. All
errors and inconsistencies identified during the data validation process will be flagged for
field verification. A field address review will be performed for all flagged locations. A
detailed methodology for each validation task will be developed as well as a QA/QC plan
for the overall process.

4.1 Develop QA/QC Plan

4.2 Establish Data Editing Environment
4.3 Compare to DTS Building Layer
4.3.1 Move address points to buildings (any remaining)
4.3.2 Normalize building address street names
4.3.3 Overlay points with buildings and pair addresses
4.3.4 "Compare addresses, identify errors and mis-matches"
4.3.5 Add missing addresses to points
4.3.6 Flag errors for field investigation
4.4 Compare to Other Data Sources

Page 3
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

4.4.1 "Obtain available data (VR, MVA, Permits, Solid Wastes…)"

4.4.2 "Normalize sources (street names, data format)"
4.4.3 "Compare sources, identify non-matching addresses"
4.4.4 Develop list of all missing addresses
4.4.5 Add missing addresses to points if possible
4.4.6 Flag errors for field investigation (2)
4.5 Compare to USPS Data
4.5.1 Perform match to USPS database
4.5.2 Identify un-matched records
4.5.3 Correct all zip codes to match USPS
4.5.4 Document street name and address range mis-matches
4.6 Compare to Parcel Data
4.6.1 Capture street number annotation in parcel
4.6.2 Match parcel address to address point
4.6.3 Identify miss-matches
4.6.4 Correct address points if needed
4.6.5 Develop lot address labeling from points
4.7 Compare to Centerline
4.7.1 Perform geo-coding to centerline
4.7.2 Flag all addresses not matching
4.7.3 Review street name problems
4.7.4 Review address range problems
4.7.5 Flag centerline corrections
4.7.6 Transmit centerline corrections to DTS
4.7.7 Flag address point corrections
4.7.8 Review and correct address points
4.7.9 Flag errors for field investigation (3)
4.8 Perform Field Investigation of Building Addresses
4.8.1 "Sort addresses by zip, street, number"
4.8.2 Develop investigation routes
4.8.3 Perform investigation
4.8.4 Create/correct addresses (hand held)
4.8.5 Perform QA/QC on Field Results
4.8.6 Reconcile/Post updates to the database
4.9 Perform Final Quality Control of Addresses in MAR
4.9.1 Develop Final QC Procedures
4.9.2 Perform QC Procedures
4.9.3 Perform final edits
4.9.4 Migrate new MAR to Production

Page 4
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

Activity 5 Develop Building Layer

There are currently two building layers that contain two representations of building
footprints. One was derived solely from photogrammetric compilation and represents
more accurate building locations. The other was developed from a combination of
planimetric features, digitzed buildings, and approximate representations. In order to
support the call-taking function, it is necessary to develop a merged layer containing
useful attributes from both sources and selecting the most accurate building footprint
from either layer. Each building must be linked to the address points layer and the
addrerss points must be placed within the correct building so that the accurate structure
addressing can be determined and labels generated to support the call-taking process.

5.1 Normalize DTS Building Source field

5.2 Overlay DTS Buildings and Planning Buildings
5.3 Flag all DTS buildings not in Planning
5.4 Flag all buildings that do not match spatially
5.5 Review all non-matches and select best representation
5.6 Delete and append buildings to Planning layer based on flags
5.7 Populate codes to denote source of each building
5.8 Merge Building attributes from both sources
5.9 Generate Building_ID
5.10 Overlay final buildings w/addresses
5.11 Verify points within buildings
5.12 Populate Building_ID in Address Points

Activity 6 Implement Unit Numbering

The capture of unit numbers within commercial and residential buildings must be
completed. Condominium units have been captured due to the tax account record that
exists for each condominium which can be related to the parent parcel. The condo points
that have been created must be linked to the master address points for each building. In
addition, unit numbering must be developed for all residential rental and interior
commercial units as well. This will support the call-taking function as well as resident
notifications during emergencies. The complete capture of unit numbering will require
field verification in some cases.

6.1 Review current Condo Points relationship structure

6.2 Implement linked Units table
6.3 Link Condo Points to a Master building address point
6.4 Identify multi-unit buildings
6.5 Develop survey program to obtain unit numbering
6.6 Perform field survey of unit numbers

Page 5
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

6.7 Populate unit numbers for condo and rental units

6.8 Perform QA/QC of unit numbers
6.9 Refine Address Points Per Building

Activity 7 Review all buildings with multiple address points

Many buildings have multiple address points which reflect distinct entrances and
structure addressing at each entrance. In cases where the building has interior firewalls
digitized, creating separate building polygons, the relatioinship will be one-to-one,
however there are many cases where the building is a single structure with multiple
storefronts, entrances, or lobbies. In these cases, the addressing will be reviewed and
address points placed near the entrances. The addresses will be compared to the address
ranges that were developed and any inconsistencies flagged for field verification. The
multiple addresses per building structure will be used to generate an address range label
in those cases where the buildilng area is too small to support individual address labels
legibly. For each building, a primary address point will be selected to serve as the
combined label point.

7.1 Locate address points at entrances

7.2 Compare to building address ranges in DTS Buildings
7.3 Ensure multiple points match ranges
7.4 Select primary address point for labelling purposes

Activity 8 Implement Replicated Servers

In order to support timely updates and immediate access to accurate addresses, the server
environment must be upgraded to support maintenance and production servers,
replication between County and Department of Planning, and versioned data editing.
This will allow shared editing responsibilities, cooperative QA/QC programs, and ensure
that publicly available data is accurate and timely.

8.1 Design Server Architecture

8.2 Create versioning plan
8.3 Establish data maintenance server for MAR
8.4 Establish replicated maintenance server at DTS
8.5 Implement replicated versioned editing
8.6 Create publication servers
8.7 Replicate maintenance database to publication servers

Page 6
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

Activity 9 Implement GIS Portal

Implementation of a GIS Portal will allow data to be published and managed through one
interface ensuring that all users have access to timely and documented data. This will
resolve current problems of multiple data layers existing on mapped shared drives and in
SDE databases with no documentation of source and timeliness of data.

9.1 Design GIS Portal structure and documentation standards

9.2 Identify and create GIS Portal publishers and managers
9.3 Implement the GIS Portal
9.4 Provide training in publishing to the Portal

Activity 10 Centerline Modernization

The centerline file that is being maintained currently is in coverage format which is not
supported by ESRI's current maintenance environment. The content and format of the
centerline file was originally derived from the GBF-DIME file that supported the Census
Bureau mapping requirement. The data structure requirements of the line and polygon
elements are not longer required to support mapping. The current users and requirements
for the centerline and related polygon layers should be reviewed to determine the
appropriate data structure considering the ESRI environment and the integrated MAR
data model. The centerline should be migrated to an SDE database and a toolset
developed to support its efficient maintenance. Training for staff will be needed in the
new environment.

10.1 Review centerline data requirements

10.2 Identify all current uses and related data layers
10.3 Document current centerline maintenance procedures
10.4 Update/revise Centerline data model
10.4.1 labeling vs. annotation
10.4.2 "related polygon layers, left/right attributes"
10.4.3 Mainframe GBF/DIME
10.5 Integrate with MAR
10.6 Design new maintenance procedures
10.7 Design data maintenance tools
10.8 Develop QA/QC Plan and Procedures
10.9 Migrate Centerline to SDE as test
10.10 Implement data maintenance tools
10.11 Train staff in new tools and environment
10.12 Migrate Centerline to SDE as production
10.13 Perform parallel centerline updates

Page 7
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

Activity 11 Update Public Safety Data Provisioning

The current CAD system utilizes a GIS conversion toolset that requires source data to be
in coverage format. A complex data provisioning process has been developed that
involves multiple processing cycles and QA/QC reviews at each step. There is
opportunity to streamline this process in two stages. The first is the generation of the
required coverages from data maintained in the SDE environment. In the future, when the
CAD system is upgraded or the conversion tool upgraded, the CAD data can be provided
in the current GIS data format instead of coverages. For both of these cases, migration of
the data maintenance and provisioning process to the SDE environment will streamline
the QA/QC process. In this activity the current data layers will all be reviewed and all
migrated to the SDE environment with the appropriate tools for maintenance and QA/QC.
The centerline migration will be performed in parallel.

11.1 Review current CAD data requirements

11.2 Review CAD upgrade plans and migration path
11.3 Review PSDP Procedures in detail
11.4 Design new procedures extracting data from SDE
11.5 Design new QA/QC procedures
11.6 Develop test procedures
11.7 Perform parallel PSDP process

Activity 12 Implement Addressing Online Tools

Several online tools have been identified to support the improvement of addressing data
through error reporting and tracking and address validation. This will support submittal
of errors, change requests, updates by a variety of stakeholders, including the public,
County employees, public safety staff, other agencies and communications companies.
All submittals will be reviewed and incorporated as appropriate, and tracked. Address
validation tools for both individual addresses and batch submittals of address data files
will be provided. This will allow agencies that rely on address information to improve
their databases and geo-coding results with minimal intevention by GIS professional
support staff. Field data collection tools will also be implemented to support the address
update and correction process by staff in the field. A structured process that adheres to
the Software Development Life Cycle (SDLC) will be followed for each application area.

12.1 Perform SDLC for Online Error Reporting and Resolution

12.2 Perform SDLC for Address Validation tools
12.3 Perform SDLC for field verification tools

Page 8
 Montgomery County, Maryland—GIS Strategic Plan Update

Phase II—Addressing Data Development Plan

WORKPLAN—SCHEDULE

Page 9