1 Introducing Scenario Network Data Editing and Enterprise GIS January 27, 2010 Minhua Wang, Ph.D. Citilabs, Inc.

 Introduction  Scenario Network Data Editing  Multi-user Network Editing in Enterprise GIS Agenda

 Scenario Network Data Editing Requirements in Demand Forecast Modeling  Be able to create scenario network data  Be able to display scenario network data Display scenario relationships Display scenario network on map  Be able to edit scenario network data  Be able to cascading network changes to related scenario networks  Be able to query scenario network data  What is Enterprise GIS?  Centralized geodatabase to store scenario based network data  Allow multi-user access, edit geodatabase concurrently  Allow geodatabase versioning and edit versioned geodatabase  Allow geodatabase replication and synchronize distributed editing  Why enterprise GIS for Master network editing  Single source of network  Multiple user access and editing  Protect network from unauthorized user  Support distributed editing Introduction

 Scenario Data Creation  Network Scenario Creation Define network scenario  Junction Scenario Creation Define junction scenario  Scenario Data Display  Scenario Data Display in Data Manager Display parent-child relationship  Scenario Data Display on map Query layer of scenario data  Scenario Network Editing  Edit scenario network from scenario network layer (define scenario first)  Save network edits to scenario network - save to new scenario (define) or save to existing scenario Scenario Network Data Editing

Highway Network Scenario Creation Transit Network Scenario Creation Junction Scenario Creation

 Separation of Master Network storage and editing from Cube environment  Issues? Keep sync from network changes in Cube to Master network? How to maintain network topology if network is edited outside of Cube?  How to edit master network within Cube or Sugar? How do you edit scenario network with Master Network now? Store and Edit Master Network Outside Cube Export to Scenario Network to Shape file Load network shape file to model Run model If network changed in Cube, how to sync back?

Scenario based Network Editing Workflow Define Scenario (Data Manager) Add Scenario Network to Map (Data Manager) Edit Network on Map Window (Network Editor) Add Source Network to Map (Data Manager) Save edits as Scenario (Network Editor) Save to New Scenario ? Select a Scenario (Data Manager) Define Scenario (Data Manager) Cascade Changes Save edits as Scenario (Network Editor) No Yes

 Scenario Network Editing  Define Scenario Define scenario Define scenario-source relationship Scenario time frame: start, end  Add Network to Map Add scenario network: add newly defined scenario to map (create a query layer) Add source network: add specific network to map (any network, base network or a scenario network)  Edit Network with Network Editor Edit geometry Edit attributes  Save Edits to Scenario Save edits to new scenario o Save to current scenario or to define a new scenario Save Edits to existing scenario o Select an existing scenario o Save to the selected scenario Scenario Network Data Editing in Future Cube and Sugar

 Scenario Network Editing  Store scenario changes as new records in geodatabase Store new network data entity o New links, new nodes Store changed network data entity o Store geometry changes: reshape o Store attribute changes o Retire old network data entity  Set status to retired  Set DATE_OUTSERVICE Store split link o Store split links as new links o Store Source_AB in new links for the parent link o Retire parent link Store deleted network data entity o Set status to retired for the deleted link o Set DATE_OUTSERVICE Scenario Network Data Editing in Future Cube and Sugar

 Cascading Network Changes  Cascading base network changes Cascading changes for transit network Cascading changes for junction: e.g., deleted node o Cascading changes for scenario junctions Cascading changes for all scenario networks  Cascading source scenario network changes Cascading changes for all child scenario networks  Cascading Network Changes Workflow  Update Cascading_Status field  Highlight network changes in related networks  Allow options for automated cascading updates or manual updates Scenario Network Data Editing (Cont’d)

 Enterprise GIS Database  SQL Server  Oracle  DB2  Enterprise GIS Database Versioning  Geodatabase Versioning Default version: root version Child versions  Version types Protected version Public version Private version  Editing versioned geodatabase  Register dataset as versioned dataset  Edit default version  Edit child versions  Compare changes in versions  Post versioned changes  Reconcile conflicts  Post changes back to default version Multi-User Editing in Enterprise GIS

Versioning Concept Create Version Edit Versioned Dataset Workflow

Compare version changes

 Multi-user Network Editing  Create versions for GIS group and Modeling group Create private version Only owner can edit Administrator will do reconcile conflicts and post changes  Administrator or user creates SDE connection to a versioned network  Can create group of users to access versioned network  For a specific version, more than one user can access and edit the versioned network  Cube or Sugar can load versioned geodatabase to data manager and the map Multi-User Editing in Enterprise GIS

Thank you!