π CTRAMP Output File Specifications ΒΆ
About This Documentation
Comprehensive field-level documentation for CTRAMP (Coordinated Travel-Regional Activity Modeling Platform) output files. All specifications are verified against real model data for maximum accuracy.
π Model Run Verification ΒΆ
Data Source Verified
All documentation is based on analysis of the 2015-tm22-dev-sprint-04 model run:
C:\Box\Modeling and Surveys\Development\Travel Model Two Conversion\Model Outputs\2015-tm22-dev-sprint-04\ctramp_output\
π Output File Categories ΒΆ
Core population and household characteristics
- πͺ Household Data - Demographics and socioeconomic attributes
- π€ Person Data - Individual characteristics and travel patterns
Long-term location choice modeling results
- π’ Workplace & School Locations - Employment and education destinations (wsLocResults)
Daily travel behavior and trip generation
- π― Individual Tours - Person-level tour patterns (indivTourData) - 57 fields
- β‘οΈ Individual Trips - Trip segments within tours (indivTripData) - 19 fields
- π¨βπ©βπ§βπ¦ Joint Tours - Household coordination (jointTourData) - 51 fields
- π Joint Trips - Joint household trip segments (jointTripData) - 18 fields
Common definitions and data standards
- π Data Dictionaries - Modes, purposes, and field definitions
β Quality Assurance ΒΆ
Verification Standards
All field counts and data structures verified against actual CSV files
Purpose classifications and mode choices reflect real model outputs
Standardized 17-mode transportation dictionary across all files
Documentation Purpose ΒΆ
This documentation serves to:
- Define exact output format - Field names, data types, constraints
- Specify allowed values - Valid codes, categories, ranges
- Provide data dictionaries - Meaning of categorical codes
- Enable survey mapping - Transform survey data to CTRAMP format
- Support validation - Ensure data integrity and consistency
Key Design Principles ΒΆ
Geographic Hierarchy ΒΆ
- MGRA (Micro-Analysis Zone): Finest geographic resolution (MAZ in model code)
- TAZ (Traffic Analysis Zone): Aggregated zones for trip matrices
- County/District: Administrative boundaries
Temporal Structure ΒΆ
- Time Periods: Model uses discrete time periods (typically 1-48 half-hour periods)
- Tour Organization: Tours contain trips (outbound and inbound legs)
- Activity Patterns: Daily activity coordination across household members
Choice Model Results ΒΆ
- Utilities/Probabilities: Optional detailed model outputs
- Logsum Values: Accessibility measures from nested models
- Random Numbers: For reproducibility and debugging
Common Field Types ΒΆ
Identifiers ΒΆ
hh_id: Unique household identifier (integer)person_id: Unique person identifier across model (integer)person_num: Person number within household (1-based, integer)tour_id: Unique tour identifier (integer)stop_id: Stop number within tour half (0-based, integer)
Geographic References ΒΆ
home_mgra,orig_mgra,dest_mgra: MGRA identifiersTAZ: Traffic Analysis Zone identifierparking_mgra: Parking location MGRA
Categorical Codes ΒΆ
person_type: Worker/student/age categories (1-8)tour_purpose: Trip purpose codes (work, school, shopping, etc.)tour_mode/trip_mode: Transportation mode (1-N, varies by model)income: Household income category (1-4 or 1-5)
Model Results ΒΆ
sampleRate: Expansion factor for sampling (float)avAvailable: Autonomous vehicle availability (0/1)dcLogsum: Destination choice logsum value (float)
File Relationships ΒΆ
Household (1) ββββ (N) Person
β β
β βββ (N) Individual Tours ββββ (N) Individual Trips
β β
βββ (N) Joint Tours ββββ (N) Joint Trips
Survey Data Integration ΒΆ
When mapping survey data to CTRAMP format:
- Establish crosswalks between survey categories and CTRAMP codes
- Validate geographic references ensure MGRAs/TAZs are in model network
- Handle missing data following model conventions (typically -1 or 0)
- Apply expansion factors to match model population targets
- Verify consistency across related tables (tours β trips, person β household)
Getting Started ΒΆ
- Review the Data Dictionaries for categorical value definitions
- Examine your specific output file documentation:
- Household Output Format
- Person Output Format
- Workplace & School Location Results
- Individual Tour Output Formats
- Joint Tour Output Formats
- Individual Trip Output Formats
- Joint Trip Output Formats
- Use Survey Mapping Templates for data transformation
- Validate output using Quality Checks
Source References ΒΆ
This documentation is derived from:
- travel-model-two CTRAMP implementation (Java source code)
- tm2py model orchestration and validation logic
- SANDAG ABM model structure and conventions
- MTC Travel Model 2.0 specifications
Last Updated: November 2025 - Documentation verified against actual 2015-tm22-dev-sprint-04 model output files