Skip to content

πŸ“Š 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

Long-term location choice modeling results

Daily travel behavior and trip generation

Common definitions and data standards

βœ… 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:

  1. Define exact output format - Field names, data types, constraints
  2. Specify allowed values - Valid codes, categories, ranges
  3. Provide data dictionaries - Meaning of categorical codes
  4. Enable survey mapping - Transform survey data to CTRAMP format
  5. 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 identifiers
  • TAZ: Traffic Analysis Zone identifier
  • parking_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:

  1. Establish crosswalks between survey categories and CTRAMP codes
  2. Validate geographic references ensure MGRAs/TAZs are in model network
  3. Handle missing data following model conventions (typically -1 or 0)
  4. Apply expansion factors to match model population targets
  5. Verify consistency across related tables (tours ↔ trips, person ↔ household)

Getting Started ΒΆ

  1. Review the Data Dictionaries for categorical value definitions
  2. Examine your specific output file documentation:
  3. Household Output Format
  4. Person Output Format
  5. Workplace & School Location Results
  6. Individual Tour Output Formats
  7. Joint Tour Output Formats
  8. Individual Trip Output Formats
  9. Joint Trip Output Formats
  10. Use Survey Mapping Templates for data transformation
  11. 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