Via Platform Export Generation

Export filtered MATSim outputs as Via visualization files and agent tracks.

1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/ro9er117911/matsim-example-project --skill via-platform-export-generation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Via Platform Export Generation
Source: https://github.com/ro9er117911/matsim-example-project/tree/main/.claude/skills/matsim-skill/6-via-export
Command: npx skills add https://github.com/ro9er117911/matsim-example-project --skill via-platform-export-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml.

What problem does it solve?

Manually preparing MATSim data for Via visualization is complex and time-consuming. This Skill automates the filtering and export of lightweight, relevant data, ensuring your visualizations are quick to generate and easy to interpret.

Core Features & Use Cases

  • Generate Filtered Events: Reduce large simulation outputs to only essential data, speeding up visualization.
  • Create Agent Trajectories: Build detailed agent movement tracks for dynamic visualization.
  • Vehicle Usage Reports: Summarize vehicle activity for focused analysis on the Via platform.
  • Use Case: After running a large MATSim simulation, use this Skill to quickly generate a filtered output_events.xml and tracks_dt5s.csv for immediate upload and visualization on the Via platform, without manual data manipulation.

Quick Start

Export MATSim simulation results from 'scenarios/equil/output/' for Via visualization, saving the output to 'scenarios/equil/forVia'.

Frequently Asked Questions about Via Platform Export Generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export MATSim simulation data for Via platform visualization?▼

Export MATSim outputs for Via platform by running this Skill on your scenarios/equil/output directory. It filters and converts output_plans.xml.gz, output_events.xml.gz, and output_network.xml.gz into lightweight Via-compatible files including filtered events, agent tracks, and vehicle usage reports, ready for immediate visualization.

What file formats does MATSim export produce, and can I use them directly in Via?▼

MATSim produces compressed XML files (output_events.xml.gz, output_network.xml.gz, output_plans.xml.gz) that require filtering and conversion before Via ingestion. This Skill transforms them into Via-ready formats: output_events.xml, tracks_dt5s.csv, legs_table.csv, and filtered_vehicles.csv for seamless platform upload.

Can I filter large MATSim simulation outputs to reduce visualization load times?▼

Yes. This Skill generates filtered events and lightweight data exports from large MATSim simulations, reducing file sizes and visualization complexity. Use CLI flags like --dt to control temporal filtering, producing only essential data needed for Via visualization without manual processing.

What are the input requirements before using this MATSim export Skill?▼

Your MATSim output directory must contain three required files: output_plans.xml.gz, output_events.xml.gz, and output_network.xml.gz. The Skill validates this structure, then processes them using lxml to extract filtered events, agent trajectories, and vehicle metadata for Via platform export.

How do I generate agent movement tracks and vehicle usage reports from MATSim data?▼

Run this Skill with --events, --vehicles, and --dt flags on your MATSim output directory. It produces tracks_dt5s.csv containing agent trajectories at your specified time interval, vehicle_usage_report.txt summarizing activity, and filtered_vehicles.csv for focused vehicle analysis on Via.

What happens if my MATSim output directory is missing required files?▼

The Skill performs directory validation and verifies presence of output_plans.xml.gz, output_events.xml.gz, and output_network.xml.gz before processing. If files are missing, it halts with validation feedback, preventing incomplete data export and ensuring only valid scenarios proceed to Via visualization.