Maryland SHA Federated Street Centerline Synchronization Pilot Project

1
Maryland SHA Federated Street Centerline
Synchronization Pilot Project
A Report on the History, Lessons Learned, and
Future Directions of the Project

• NSGIC 2009 Midyear Conference
• 23 February 2009

2
Project History

• The Shared Centerline Program started in 2001
  with the Maryland State Highway Administration
  (SHA) testing vertical integration of
  transportation data using the Howard County
  attributed centerline
• SHA developed a methodology that would allow
  sharing the common centerline from local
  governments
• SHA attaches a unique-ID onto each road segment
  allowing simplification of future data exchange
  as well as making the data model flexible

3
Project History

• This is why a cooperative centerline was needed
• Original SHA Route System

4
Project History

• New SHA Routes with County Centerline data

5
Project History
6
Project History

• Maryland State Highway Administration (MD-SHA)
  and the Maryland Association of Counties (MACO)
  received a 2005 Special Achievement in GIS award
  for its outstanding use of geographic information
  system (GIS) technology from ESRI
• Later in 2005, ESRI President Jack Dangermond met
  with SHA, sharing with the team that data
  interchange may be enhanced with the new
  capabilities being introduced into the ArcGIS
  data server environment at the 9.2 release

7
Street Centerline Update Process

• There were 2 processes that SHA followed to
  update the Street centerline data
• The State and Local Team would process the
  inventory data
• The GIS Team would make the spatial adjustments
  to the GIS Centerline
• These processes have been more closely allied, as
  the GIS Team no longer maintains the Street
  Centerline
• The State and Local Team, who is responsible for
  the Inventory Process, and the HPMS submission
  ,now maintain all aspects of the project, from
  initiation to GIS update.

8
Inventory Process

• 23 Counties and 145 Municipalities report Road
  Improvements to SHA
• Road Improvements Package is sent to Counties
  and Municipalities in September
• Municipalities return Improvements Package to
  SHA by December 1st
• SHA verifies improvements and consolidates into
  Improvement Log to be inventoried compiled from
  November to January

9
Inventory Process (Cont.)?

• Improvements are field verified by SHA Inventory
  Crews from November until April
• SHA Technicians process improvements from field
  checks and prepare for HPMS submission to
  Federal Highway Administration by June 15th
• Concurrently, the team also make all necessary
  geometry updates to the GIS route and centerline
  data

10
Maryland SHA Federated Street Centerline
Synchronization Project

• Pilot project March August 2006
• Participants
• Maryland State Highway Administration
• Anne Arundel County
• Towson University Center for GIS
• Leveraged existing cooperative relationships
• Tested new technology and software functionality

11
Pilot Conceptual Architecture
12
Implementation StrategyCreated March, 2006

• CGIS hosted the parent replica
• Allowed access for
• County Connected Environment
• SHA Disconnected Environment
• Parent replica was configured to accept all
  changes in favor of child during Phase 1
  (additions deletions)?
• Parent replica was configured to accept all
  changes manually during Phase 2 (conflict
  resolution)?
• SHA replicated using the webdev site or email
• Anne Arundel County replicated outside of
  existing firewall

13
Choosing a Pilot Area

• Included a fair number of existing county
  centerline edits
• Demonstrate Municipal County State
  relationship
• Portion of Annapolis, MDselected

14
Creation of Replicas

• CGIS imported pilot area into SDE database
  connection
• Version add Global IDs
• Created child replicas
• AA county replica was put directly on server
• SHA received a delta XML document via webdev
• SHA imported XML document

15
Replication Scenarios

• Scenario 1 Anne Arundel County edits replicated
  to SHA
• Scenario 2 SHA edits replicated to Anne Arundel
  County
• Scenario 3 Reconciliation and Conflict
  Resolution

16
Replication Scenarios

• Phase 1 (Additions/Deletions Scenarios 1 2)?
• Phase 2 (Data Conflict Scenario 3)?
• SHA and AA County edited same arcs before
  synchronizing

17
Process Issues Lessons Learned

• Initially, Towson had Beta 9.2.1 in a staging
  area
• Replica Creation was taking gt2 hrs.
• Caused us to initially believe the process needed
  to run over night Not the case
• Moved to main network
• Testing of scenarios
• Towson would have liked to set up 2 instances of
  SDE internally
• Testing of scenarios locally
• Learning the replication process (smoother
  transition)?

18
Process Issues Lessons Learned

• Understand versioning and replication processes
• Ex 1st Data Conflict/Resolution Meeting
• Which tool to use for each process?
• Replication language
• Communication was important!
• Disconnected environment especially
• Data Sender/Data Receiver roles

19
Project History

• The Cooperative Centerline Program had evolved
  into the Federated, or Synchronized Street
  Centerline Project, via the previous Pilot
  between SHA, Towson University and Anne Arundel.
• The additional counties of Frederick, Baltimore,
  Howard and Harford were selected for phase 2.
• Meeting between SHA and the counties were
  conducted to resolve any issued, and establish
  the details

20
Next Steps

• Phase 2
• Implementation
• Five NEW
• counties to
• participate

21
Conceptual Phase 2 Architecture
22
What Happened

• As we began the next phase of the Federated
  Centerline Pilot, it became apparent that the
  counties were also resolving their internal
  workflow processes
• Several counties had multiple centerline
  datasets, each maintained by a different
  department. Each had a different need for the
  data, hence each had a different update cycle,
  spatial accuracy, and attribution quality.
• SHA and the counties continued to share
  information, as the counties embarked on
  centerline dataset consolidation and clean-up.

23
What Was Next?

• In response to Governor OMalleys vision for
  StateStat, and the use of geo-spatial data to
  improve governmental efficiency and drive
  decision making, the need arose for a statewide
  addressing centerline, intended to serve multiple
  application needs, such as E911, the public, etc.
• The Center for GIS (CGIS), at Towson University
  was awards a grant from the Maryland Highway
  Safety Office (MHSO) to develop a process to
  develop, and serve an addressable statewide
  street centerline.
• This project was initiated in October 2007.

24
Maryland Statewide Addressing Initiative
Geocoding Service
Towson
Child
Map Service
Map service and associated Geodata service
creation
Geodata Service
Map Service
County 1 sends a one-time copy of their
centerline to Towson
County 1 connects and extracts data, views the
map service, or uses the geocoding service
Geodata Service
County 1
County 1 connects and established the replica
based on existing data, and synchronizes changes
Parent
25
Maryland Statewide Addressing Initiative
Locator Use

• Maryland GreenPrint Application
• http//mdimap.towson.edu/GreenPrint/
• Maryland Incident Location Tool (MILT)?
• Emergency Management Mapping Application (EMMA)
  at MEMA
• Previously using ESRI Streetmap for geocoding
• MDE Land Resource Protection Application (LRP)?
• Did not have geocoding capability in the past
• Other applications to be developed

26
(No Transcript)
27
Maryland Statewide Addressing Initiative
Concerns

• Overlapping address ranges
• Edge-matching issues between counties
• Need surrounding States centerline data for
  Mutual Aid Agreements and other Emergency
  Management (EM) related issues.
• Not all of Marylands counties are fully able to
  participate in a regular update schedule

28
Maryland Statewide Addressing Initiative
Concerns (cont.)?

• Two similar Centerlines - the SHA centerline
  and the Addressing centerline.
• While built upon the SHA Centerline standard,
  County data has ancillary features, such as
  address stubs for Town Houses, Strip shopping
  centers, etc for E911 purposes.
• SHA data model can incorporate such features, as
  well as address range information

29
Future Directions

• SHA and addressing centerline processes need to
  be incorporated into one centerline process
• SHA and Maryland Counties need to discuss how to
  conflate these two very similar datasets into one
  dataset.
• One commonly accepted geometry to build various
  LRS systems for multi-governmental and public
  utility.

30
Future Directions

• Another related need is to develop and approve of
  a definitive political boundary layer for use in
  Maryland.
• While SHA has resolved this internally with there
  centerline data, both SHA and County Governments
  are not the authoritative Agency response with
  enacting these changes statutorily into Maryland
  Law (COMAR)?

31
Thank You

• For additional Information Contact
• Mike Sheffer
• GIS Program Coordinator
• Maryland State Highway Administration (MD SHA)?
• 707 N. Calvert Street,
• Baltimore, MD 21202
• [phone]
• msheffer_at_sha.state.md.us