1 / 26

Cube Enterprise Database Solution

Learn about Cube Enterprise Database Solution for managing geodatabase-based data editing, scenario management, and enterprise data model. Utilize features like seamless integration, distributed computing, and support for multiple data repositories.

lindberg
Download Presentation

Cube Enterprise Database Solution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cube Enterprise Database Solution presented toMTF GIS Committee presented byMinhua Wang Citilabs, Inc. November 20, 2008

  2. Cube Enterprise Database Solution Agenda • What is Cube Enterprise Database Solution • Enterprise Data Management • Data Editing in Enterprise Environment • Scenario Management • Enterprise Data Model

  3. What is Cube Enterprise Database Solution • Database driven • Geodatabase based • Integration with enterprise GIS • Access multiple data repositories • Scenario Management within Database • Support distributed computing environment • Support Service Oriented Architecture (SOA) • Interface with Citilabs software products, Cube Base, ArcGIS Extension, Voyager, etc.

  4. Cube Enterprise Database Solution Architecture Software Products Cube Base Cube ArcGIS Extensions Cube Web Geodatabase Manager Scenario Manager Software Components Application Manager Junction Analyzer Accessibility Analyzer Functional Libraries Cube Data Connector Cube Voyager ArcGIS Services Data Web Services Data Services Cube Enterprise Database Remote Transportation Database Cube File Systems Data Repositories

  5. Cube Enterprise Database Solution Concept of Operation Cube Web: Editing Network Manage Scenario …. Cube Base: Editing Network Build Model Manage Scenario …. Data Management CUBE Enterprise Database Version Control Scenario Management Access Control Cube ArcGIS Extensions: Editing Network Model Junctions Manage Scenario ….

  6. Enterprise Data Management • Server based data management (Relational database servers) • Data definition • Data versioning • Data access control: user roles and user privileges • Concurrent transactional control • Data publishing: publish web services • Data backup/restore and disaster recovery

  7. Enterprise Data Management (cont’) • Seamless Integration with Your Enterprise GIS • Geodatabase based • ArcSDE backend: • Support geodatabase versioning • Support geodatabase replication • Geometry network is based on centerline data model • Same editing environment • ArcGIS desktop • ArcEngine applications

  8. Enterprise Data Management (cont’) • Support Distributed Computing Environment • Access multiple data repositories • Support geodatabase replications • Provide import/export utilities • Provide dblink or dbconnect tools • Link tables located in remote databases • Provide support for consuming web services • Use ArcGIS API to directly access geospatial data in other data formats • E.g., base map data in Google Earth services (KML services)

  9. Data Editing in Enterprise Environment • Data Versioning • Support concurrent editing by multiple users • Data Scenario Management • Control data editing on scenario based data • Data Editing Tools • Network Editor • Edit highway network • PT Editor • Edit PT network and time tabling data • Junction Editor • Edit junction and movement data • Accessibility Editor • Edit accessibility data

  10. Scenario Management • Model Based Scenario Management • Cube Scenario Manager • Data Scenario Management • Year based network • Alternative • Project based

  11. Scenario Management • Model Scenario Management • Support Cube Scenario Manager • Store model parameters in database as metadata • Model Catalog • Model Application parameters • Model Scenario • Scenario key values • Provide configuration tools to support multiple data types: • Database tables • Linked tables • Data files • Web services • Provide model sharing across multiple users

  12. Scenario Data Management • Handle Data Changes in Scenarios • Spatial Data Changes: new roads, closed roads, new intersections, etc. • Attribute Changes: number of lanes changes, speed changes, capacity changes, new traffic controls, etc. • Master Network Concept • Single version, one-stop storage • Support multi-scenario, multi-modal, multi-year networks • Support multiple concurrent editings • Store, track, manage Scenario data in database • Eliminate data redundancy • Maintain Parent-Child relationships • Synchronize changes across scenarios

  13. Scenario Data Management • Scenario Data Management for Master Network (FSUTSM) • Log Scenario Changes for Master Network – Database Level • Extracting scenario • Log changes • Merge changes to master network • Cascading changes – Software Level • Forward propagating • Backward propagating

  14. Scenario Data Management (cont’) • Scenario Data Management for Enterprise Data Management (Cube Enterprise) • Network definition: support multi-modal networks • Define network and associated features: e.g., highway network, PT network, etc. • Data Scenario Definition • Define data scenario with data group type: e.g., 2010 highway network • Scenario based data • Each data entity is referenced by scenario identifier (DataID) and network identifier (NetworkID)

  15. Scenario Data Management - Use Cases Case 1: Data changes in scenarios • Change network spatially or in attributes • Change network in new scenario (new year) or existing scenario , e.g., • Add, edit, delete, split network links • Change speed, number of lanes, intersection control, capacity, etc. • Data changes outside of master network (FSUTMS) • Extract scenario network: new or existing • Make changes with Cube 5 • Merge updates to master network • Propagate changes (forward or backward) to master network

  16. Scenario Management - Use Cases • Manage data changes with Cube Enterprise • Manage scenario in database: • DataID: identifier for data scenario • NetworkID: identify network group, e.g., highway vs. PT, 2010 highway • ParentID: track parent –child relationship • Scenario tree: track scenario along scenario tree • Scenario tree level: tree level in a tree • Data type: identify data group type on scenario, e.g., Highway Network data, Speed capacity, Junction data, etc. • Name: e.g., Base, etc. • Extract scenario data as layer or view • Retrieve or create scenario data as layer, instead of duplicated copy of data • Make changes on scenario data layer • Cube directly edit scenario data layer • Provide software controls on change propagation • Allow user to selection propagation options

  17. Use case: number of lanes, speed changes in scenario • Base scenario: 2 lanes, speed 35 • Scenario 1: change 2 lanes to 4 lanes • Scenario 2: Change speed to 45 1. Scenario Definition in database 2. Scenario data stored in database

  18. Scenario Management - Use Cases Case 2: Data changes propagation

  19. Scenario Data Management - Use Case 2 • Cube Enterprise Solution • Maintain data scenario parent-child relationship in database: parent-child relationship can be tracked based on ParentDataID, DataScenarioTree and DataScenarioTreeLevel • Allow user to select cascading change options • Forward cascading • Backward cascading • Auto-search data elements based on scenario trees • User select cascading • Automatic cascading

  20. Cube Enterprise Data Model • Data repository or container for all transport demand modeling data • Geodatabase based, fully integrated with ArcGIS products • Scalable implementation with or without ArcSDE • RDBMS support: Oracle, SQL Server, DB2, etc. • Lightweight database server: SQL Server Express (4 GB limit) • File based geodatabase • Personal Geodatabase (2 GB limit)

  21. Cube Enterprise Data Model (cont’) • Road Network Data Model • Geometry Network: represents physical transport features with geometry • Logic Network: represents model network features without geometry • PT Network Data Model • PT Services (Routes) • PT Lines • PT line stops • PT links • PT Trips • PT Triptime • Junction Data Model • Junction • Approach • Movement • Stage • Junction Layout • Accessibility Data Model • Origins • Destinations • Accessibility calculations • Accessibility outputs • Scenario Management Data Model • Model Scenario • Data Scenario

  22. Cube Enterprise Data Model (cont’) • How to display logic network in GIS • Create spatial views by joining geometry network with logic network based on ANODE-BNODE pair (Links) or Node number (Nodes) • How to display PT network in GIS • Create spatial views by joining geometry network with PT network (Links or Nodes) based on ANODE-BNODE pair or Node number (Nodes) • How to create year-based network • Data scenario management

More Related