Metacity
  • Welcome
  • Metacity
    • Installation
    • [dev] CGAL Dependency
    • Data Import
    • Models and Attributes
    • Layers
    • Grids
    • Quad-trees
    • Dockerized Processor
    • Development notes
  • Archives
    • DataAPI
      • Development
    • MetacityGL
      • Installation
      • Creating a MetacityGL App
      • Writing Custom Layers
      • Loading Metacity Data
      • Development notes
    • BananaGL
      • Development
    • AMOS
      • Synthetic Population
        • Case Studies
        • Data Specification
        • Activity Chains
        • Spatial Distribution
        • MATSim population input and comparison
        • Households
      • MATSim
        • Basic Info
        • Running Scenario
          • Config File
          • Current state
        • Input information
          • OSM
          • Filtering GTFS
          • Coordinates
        • Output
          • Processing
      • OICT
        • MapResolver
      • Resources
        • Trafic Simulation
        • MATSim
        • Vis and Meta Software
        • Synthetic Population
        • Public Relations
        • Inspiration
    • Metacity Block Edition
      • Epic Games Mega Grant
      • 🧠Internal notes
  • Links
    • Homepage
    • GitHub
  • Code of Conduct
Powered by GitBook
On this page
  • Extracting Activity Chains from Travel Survey
  • Matching census data and travel survey
Edit on GitHub
  1. Archives
  2. AMOS
  3. Synthetic Population

Activity Chains

To pair each synthetic agent with activities we first extract the daily activity chains from the travel survey.

Activity Chain

A series of activities that each agent performs during one day. Our tracked activities so far are:

  • Primary:

    • home

    • work

    • education

  • Secondary (TBA):

    • leisure

    • shop

    • other

Activity chain consists of activities and trips between each two activities:

Activity: * type * start time * end time * activity order * location ID [optional]

Trip: * traveling mode * trip order

For simulation purposes first activity type must be the same as the last activity type. For example, if synthetic agents starts the day performing a "home" activity, they must also end the day performing a "home" activity, such that the activity chain is looped and can, in theory, run indefinitely.

Extracting Activity Chains from Travel Survey

We extract looped activity chain for each traveler in our travel survey data. Travelers with invalid activity chains are discarded.

Matching census data and travel survey

To assign each synthetic agent an activity chain, we use statistical matching to map traveler onto our census data.

Attributes used for Hot Deck matching algorithm:

  • age: grouped into categories {0-17,18-29,30-44,45-64,65-74,75+}

  • employment status: grouped into categories {employed, unemployed, student}

  • sex: two groups {male, female}

  • district [optional]

Roughly 1000 samples from our census data remained unmatched with a counterpart from the travel survey. The unmatched agents were mostly 30+ aged students. We dropped those samples from our dataset.

PreviousData SpecificationNextSpatial Distribution

Last updated 2 years ago