GIS Features in Cube 4.2, 5.0, and Beyond FDOT Model Task Force GIS Subcommittee November 28, 2007 1 Overview Introducing Cube 4.2 The Cube Geodatabase Cube 5.0 Beta Results Status and Future of Cube 5.0 2 Introducing Cube 4.2 Released 10/2007 at Futura User Conference Significant new visualization features: – – – – Avenue packet log animation Export packet log to Google Earth (KML) Auto _LOS attribute for junction model output display Synchronized transit/highway link splits Major advances in Voyager capability: – – – – – Improved point-to-point tolling via TOLLMATI Vastly improved Avenue functionality New DBI (database input) record processor ESRI geodatabase read/write functionality CubeGIS roadway network feature class Now available for download on website (4.2.1) 3 Introducing the Geodatabase Cube 4.2 supports data storage in the ESRI ArcGIS 9.2 personal geodatabase (.mdb) format A geodatabase: – – – – Is like a file folder Provides a place to store and organize data sets Can be used to relate tables and feature classes to one another, both spatially and using common attributes Does not contain any maps or models—just the data for them Industry-standard format compatible with major GIS and database management software 4 The Cube Geodatabase Users can import/export: – – – Shapefiles (point, line, polygon data) Database tables (dBASE) Voyager/TP+ transportation networks CubeGIS transportation networks: – – – – – Maintain the node-link connectivity relationships required for transportation planning applications Allow the user to edit and store link shape vertices for true shape display and distance updating using shape length Store node and link attribute tables in two stand-alone feature classes that can be accessed separately or as a unit Can be read and written directly by Voyager models Can be edited in the Cube GIS Window 5 Benefits of Geodatabase Use Industry-standard format in used widely by GIS professionals and organizations Provides a common repository for sharing data used by modeling, forecasting, and GIS staff Allows you to leverage existing geographic data and offer model data as a resource for others Develop models incorporating relational database logic into processing with DBI Adopt and refine ready-made schemas and standard data models for transportation 6 Working Across Organizational Hierarchies and Divisions Planning Finance Modeling GIS Research 7 A Common Transportation Information Resource Planning Modeling Operations Research GDB 8 Relational Database Logic Tables and feature classes in a geodatabase can be related by common attribute fields via DBI joins – e.g. FILEI DBI[1]=MyGDB.mdb\Streets, SORT=ID FILEI DBI[2]=MyGDB.mdb\StreetTypes, SORT=Type_ID, JoinToDBI=1, JoinToFields=Type_ID FILEI DBI[3]=MyGDB.mdb\CapClass, SORT=Cap_ID, JointoDBI=2, JoinToFields=Cap_ID ID 1 2 3 4 5 6 7 … Streets Name Type_ID Wood 4 Davidson 7 Mercer 2 Green 3 Oak 1 Main 1 Barrett 1 StreetTypes Type_ID Lanes Cap_ID 1 1 2 2 1 4 3 2 1 … CapClass Cap_ID Capacity 1 850 2 1100 3 1250 4 1400 5 1800 9 Geo-Processing Functions The ArcGIS Engine also provides tools for querying and relating features by location: Union Intersect Buffer Clip 10 CubeGIS Data Models Existing relationships between data elements in Voyager travel demand models translate into relationships between objects in the Cube 5 geodatabase. Users can rely upon this system of core tables & geographic features and extend it with data models designed for their own applications. Note: for discussion only. Not an actual software object model. 11 Cube GIS Components Display & Editing Management & Manipulation Network Window GIS Window Catalog Geodatabase 12 What’s New at Cube 5.0 Beta? Geodatabase Manager – – – – Create, edit, and manage geodatabase files Compatible with MS Access 2003, ArcGIS 9.2, and CubeGIS View, set, and edit extent and spatial reference Create new feature classes, including CubeGIS networks Geodatabase Browser – Allows you to link model applications and Voyager scripts to geodatabase feature classes GIS Mapping Window – – – Display and edit GIS layers within Cube, including point, line, and polygon feature classes, as well as CubeGIS networks Support for shapefile, raster, and CAD format data included Create ArcView-ready map document files with annotation and map surrounds using the WYSIWYG Layout View 13 Results of Cube 5.0 Beta testing Diverse reactions to compromises made in graphical user interface: – – Cube-centric users: “where are the usual buttons?” Arc-centric users: “why can’t I rearrange the toolbar?” Some issues regarding compatibility with existing user data sets (existing geo-databases) Transit line display and editing features (originally planned for 5.1) are critical Desire for a “richer” data model in the GDB (e.g. turn penalties, junctions, screenlines) Conclusion: continue as an open public beta and distribute with 4.2 to interested customers 14 Road map: 5.0 and beyond Since October: – – – Fixed installation issues in 4.2.0 Tested and resolved many bugs and crashes Draft GIS documentation, getting started guide End-of-year 2007: – – – – Beta release of GIS-based PT display and editing Beta release of timetabling and schedule import Cleanup and improvement in GUI experience and user guide Better handling of existing real-world user data sets March 2008: – – Final release with all Cube 4.1 functionality in GIS window Final documentation and user guides Beyond: extensions & usability improvements 15