1. FSUTMS Data Framework Associate Professor
presented to GIS Committee, Florida Model Task Force
presented by Albert Gan
Associate Professor
Lehman Center for Transportation Research
Florida International University
May 14, 2010

2. Problems with FSUTMS Input Data
Input data are stored in individual files of different file formats
DBF, CSV, PEN, DAT, LIN, NET, MAT, etc.
Text files do not have variable names
Variable names are inconsistent among different models
Files are not saved in standard file folders
Consequence: Data are more difficult to maintain and understand
Consequence: Tools cannot be developed without customizing for individual models

3. Project Objective Design a data framework for FSUTMS that
facilitates the maintenance of model input data
allows tools to be developed and applied across all models with minimum or no customization

4. Three Basic Design Approaches
Use of geodatabase
Use of “master” geodatabase
Include all variables used by all FSUTMS models

5. Use of Geodatabase
Store all files as a set of tables in a personal geodatabase file
GIS-TM uses this approach more than 10 years ago
2 GB size limit of Personal Geodatabase is not a problem
Geodatabase for all base-year data for SERPM is only 65 MB, or about 3% of the 2 GB limit

6. Use of Master Database Approach
Traditional Approach
2000
2010
2020
Base
Differences from Base
Differences from Base
Base
Master Database
2010
Base
Base
Differences from Base
Base
Differences from Base
Scenario Extraction
Scenario Merging
2030
2040
Differences from Base
Differences from Base
Base
Differences from Base
Differences from Base
Differences from Base
Differences from Base
Base
Forward or Backward Propagation
Differences from Base
Differences from Base

7. Include all Variables for all FSUTMS Models
Each model has all of its variables included in the data framework
There is NOT a standard set of data variables in the data framework
Local models will not be affected as a result of transitioning to the data framework
However, each model will have to do the following:
modify to standard table (was file) names, variable names, and file folders
modify input scripts to read from a standard geodatabase instead of individual files

8. FSUTMS Models Considered
Florida Statewide Model (FLSWM)
Northeast Regional Planning Model (NERPM)
Tampa Bay Regional Planning Model (TBRPM)
Southeast Regional Planning Model (SERPM)
Treasure Coast Regional Planning Model (TCRPM)
Greater Treasure Coast Regional Planning Model (GTCRPM)
Central Florida Regional Planning Model (CFRPM)
Northwest Florida Regional Planning Model (NWFRPM)
Gainesville Urbanized Area Transportation Model (GUATS)
Polk TPO Model (POLK)

9. Project Tasks
Developing standards for folder names and structure, database names, table names, field names, and field types for all input data as well as setting standards for metadata files.
Designing a master database that is inclusive of all standard input data tables and fields of all modes from all scenarios of all local models.
Developing a master database system that implements the master database approach.
Developing a procedure for converting existing input files into the proposed master database.

10. Inconsistent Variable Names: An Example
FLSWM
NERPM
TBRPM
SERPM
TCRPM
GTCRPM
CFRPM
NWFRPM
GUATS
POLK Z
ZONE
TAZ
HBWP
HBWKP P1
PHBW
HBWA
HBWKA A1
AHBW
HBSHP P2
PHBSH
HBSHA A2
AHBSH
HBSRP P3
PHBSR
HBSRA A3
AHBSR
HBOP
HBOTP P6 P5
PHBO P4
HBOA
HBOTA A6 A5
AHBO A4
NHBP
NHBSP
PNHB
NHBA
NHBSA
ANHB
NHBWP P7
NHBWA A7
NHBOP P8
NHBOA A8
HBUP

11. Variable Naming Conventions
10 characters maximum
Use meaningful names
If a variable name contains multiple words, use underscores only if it helps to avoid confusion
If a variable is used by multiple models: choose one that is most commonly used subject to the above criteria
If a variable is used by only a specific model: use the original name unless they do not meet the general criteria above
Reference document: FSUTMS Powered by Cube/Voyager Data Dictionary, December 2005

12. Applying the Naming Conventions
FLSWM
NERPM
TBRPM
SERPM
TCRPM
GTCRPM
CFRPM
NWFRPM
GUATS
POLK
Standard Z
ZONE
TAZ
HBWP
HBWKP P1
PHBW
HBWA
HBWKA A1
AHBW
HBSHP P2
PHBSH
HBSHA A2
AHBSH
HBSRP P3
PHBSR
HBSRA A3
AHBSR
HBOP
HBOTP P6 P5
PHBO P4
HBOA
HBOTA A6 A5
AHBO A4
NHBP
NHBSP
PNHB
NHBA
NHBSA
ANHB
NHBWP P7
NHBWA A7
NHBOP P8
NHBOA A8
 HBUP
HBUP

13. Table Name Conventions
Maintain most traditional names
SPDCAP, VFACTORS, FF, PANDA, etc.
No need to attach model year and model alternative; they are part of the scenario database file name
Transportation-network related tables
HwyNodes, HwyLinks, PtNodes, PtLinks, PtLines
Non-transportation network related tables
See next slide

14. Non-Transportation Network Related Tables
ZONEDATA
ZONEDATA_LIFESTYLE
SPECGEN
EETRIPS
INT_EXT
PRODRATES
ATTRRATES
DUWEIGHTS
PANDA
SPDCAP
TOLLLINKS
TURN_PENALTIES
VFACTORS FF
TRANSIT_MODES
TRANSFER_FARES
TRANSIT_OPERATORS
WAIT_CURVES
TRANSIT_SPEED

15. Master Geodatabase File
Contains all tables for all models, all networks, all scenarios

16. Scenario Geodatabase
Contains only applicable tables for specific model, specific model year and model alternative

17. Metadata Standards Not metadata files currently used by any models
FGDC Plus Stylesheet (Federal Geographic Data Committee)
Template:
Edit in Word: C:\FSUTMS\D4\SERPM\MASTER\SERPM_MASTER.DOC

18. File Folder Structure and Naming Conventions
Source: FSUTMS New Standards and Enhancements – A User Oriented Approach, January 2006

20. Master Database System

21. Scenario Extraction

22. Scenario Merging: saving as a new scenario

23. Scenario Merging: update original scenario

24. Data Conversion Procedure (from existing files to master geodatabase)
Step 1: Create a geodatabase for the base-year data
Create an empty Cube geodatabase in Cube
Import highway network
Import public transit network
Import TAZ feature class (optional)
Step 2: Create a master geodatabase
Create an empty geodatabase in ArcCatalog
Import feature classes from Cube geodatabase into master geodatabase
Import other non-transportation network related data

25. Data Conversion Procedure (continued)
Step 3: Update master geodatabase in Microsoft Access
Rename variables to standard names
Add master database system tables (BaseYearNumber, ProjectInfo, ImpExpInfo)
Add LineID field to PTLines feature class
Add master geodatabase key fields (MNet_Year, MNet_Status, and MNet_ProjectID) to feature class and data tables
Fill key fields with appropriate values

26. Master Database System Install Package
Download: (beta version, 14 MB)
Include the SERPM master database file as an example (installed to C:\FSUTMS\D4\SEPRM\MASTER\)
Require ArcGIS Engine Runtime or ArcGIS Desktop installed on the computer running this application

27. Project Contributors Vidya Mysore, FDOT Project Manager
Albert Gan, FIU Project Manager
Kaiyu Liu and Tao Wang, Programmers, FIU
Lina Kulikowski, Broward MPO
Sarah McKinley, Capton Siluvairajan, and Robert Schiffer, CSI
Minhua Wang, Citilabs, Inc.
David Schmitt, AECOM USA, Inc.
Kenneth Kaltenbach, Corradino Group, Inc.
FDOT Research Center and Staff Members

28. Questions? Albert Gan Lehman Center for Transportation Research
Florida International University