Networks and interchange
Design routes, stops, access links, and interchange structures as explicit parts of the transport system.
Transport modelling simulation & public transport design
Understand the system.
Design the change.
Moving Studio combines public transport design with a computation stack shaped for very large networks, passenger choice, and rapid scenario iteration.
Codex plugin · private preview
Inspect projects and operate verified GIS workflows in natural language.
From evidence to decision
One connected environment
- 01DataAssemble the evidence
- 02ModelBuild transparently
- 03DesignDefine interventions
- 04SimulationsCompare alternatives
- 05ResultsExplain the impact
01 / Approach
Start with the decision,
not with the procedure.
Traditional modelling tools ask experts to reproduce a long sequence of technical operations. Moving Studio starts from the transport decision: the alternatives, constraints, available evidence, and questions that matter.
The product turns that design into an inspectable first model, then supports progressive calibration and refinement. Assumptions, missing inputs, provenance, and validation remain visible throughout the process.
02 / Public transport design
Research core and product direction
Public transport is a system to design.
Not a layer to display.
Moving Studio treats networks, services, timetables, interchanges, demand, and passenger response as one connected design problem. Teams can define an intervention, test how travellers react, and compare its multimodal consequences without disconnecting the service plan from the model that explains it.
Services and schedules
Represent service patterns, frequencies, and timetables together with the network and demand they serve.
Passenger choice
Model waiting, in-vehicle alternatives, transfers, hyperpaths, and probabilistic service selection.
Alternatives and phasing
Compare service and infrastructure designs while retaining assumptions, revisions, evidence, and implementation stages.
Research depth
The research core already includes frequency- and schedule-aware networks, reverse transit hypertrees, wait and in-vehicle hyperarcs, and probabilistic service loading. Product availability will be declared capability by capability.
03 / Computational edge
More than a modern interface.
A transport computation stack.
Anyone can make modelling software look modern. The difference appears when the network becomes large, the alternatives multiply, and every result still has to be explained.
Moving Studio grows from years of transport and numerical research. Its source already spans spatial search, network loading, dynamic flow, estimation, calibration, and high-performance solvers — not a single black-box simulator.
01 / Graphs
Network construction & routing
Road, transit, and time-expanded graphs; bucket-based shortest-path trees; A* and ALT landmark search; alternative-path generation.
02 / Transit
Hyperpaths & service choice
Reverse transit hypertrees, wait and in-vehicle hyperarcs, frequencies, and probabilistic service selection.
03 / Equilibrium
Assignment & route choice
Path- and link-based fixed points, deterministic and logit choice, efficient bushes, and Tarjan-based route-overlap measures.
04 / Dynamics
Flow through time
Godunov schemes, general link-transmission models, shockwave propagation, and vehicle-trajectory formulations.
05 / Inference
Demand & calibration
OD scaling and estimation, generation–attraction constraints, sparse assignment matrices, and calibration against counts and travel times.
06 / Numerics
Convergence at scale
Anderson acceleration, matrix-free linear solvers, implicit and bilevel optimization, batched tensor computation, and CUDA execution.
Large-network thinking
Algorithms and data structures shaped around memory, parallel loading, and computation — not only demonstration datasets.
More scenarios, sooner
Faster computation turns time saved into alternatives tested, sensitivities understood, and decisions improved.
Evidence, not magic
Methods, assumptions, convergence, revisions, and fitness for use remain inspectable from model to result.
The research core includes both established components and active experiments. Product availability will be declared method by method; quantitative claims will use reproducible benchmarks on named networks and hardware.
04 / Model families
The models are
the product.
Moving Studio is being built to connect a broad family of transport models inside one project. The research core already contains the methods below; the desktop product will expose them progressively with explicit availability and fitness-for-use information.
Research core
Static equilibrium
Deterministic and stochastic assignment, with path- and link-based fixed-point formulations, efficient bushes, multiclass demand, and congestion.
- Deterministic
- Logit
- Path based
- Link based
Research core
Dynamic traffic
Time-dependent network flow represented through conservation laws, link transmission, propagating shockwaves, and vehicle trajectories.
- Godunov
- GLTM
- Shockwave
- Trajectory
Research core
Public transport
Frequency- and schedule-aware transit networks with reverse hypertrees, waiting and in-vehicle alternatives, and probabilistic service choice.
- Hyperpaths
- Frequencies
- Diachronic graph
Research core
Demand estimation
Origin–destination matrix estimation and balancing with generation–attraction constraints and sparse network-loading relationships.
- OD estimation
- Matrix scaling
- G–A constraints
Active integration
Calibration & inverse models
Estimate demand, capacities, behavioural parameters, and other model inputs against observed counts and travel times.
- Counts
- Travel times
- Autodiff
Active integration
Network design & optimization
Evaluate and optimize interventions while accounting for the transport equilibrium they produce, including implicit and bilevel formulations.
- Network design
- Bilevel
- Implicit gradients
Product direction
One system across model scales
Move between strategic scope and operational detail without losing the network, demand, scenario, or provenance that connects them.
- 01MacroDemand, assignment, accessibility
- 02MesoDynamic flow and network loading
- 03MicroLanes, movements, junctions, signals
05 / Capabilities
One project. Every layer of the problem.
Networks, demand, public transport, scenarios, computation, and results stay connected instead of becoming a chain of disconnected files and tools.
01
One continuous workspace
Data, models, designs, simulations, results, reports, and revisions remain connected. The project file is the container; the value is continuity from evidence to decision.
02
Design as a first-class phase
Define interventions, alternatives, constraints, and phasing as explicit model objects. Every design remains connected to its evidence and baseline.
03
Scenario comparison
Treat alternatives as first-class project objects. Compare choices without duplicating the entire model or losing the connection to the baseline.
04
Multimodal by construction
Combine road networks, public-transport services, demand, and operational data through declared composition and validation rules.
05
From macro to micro
Coordinate macroscopic, mesoscopic, and microscopic representations inside the same project. Preserve lanes, movements, junctions, signals, and access rules even when the active model uses a coarser resolution.
MacroMesoMicro
06
Transparent computation
Run assignment, simulation, estimation, and optimization without turning the model into a black box. Inputs, methods, revisions, warnings, and fitness for use remain traceable.
07
Moving Studio for Codex
The native Codex plugin turns project intent into outcome-oriented operations: inspect state, prepare a design, focus the map, and manage supported GIS layers without memorising interface procedures.
08
Collaboration for real models
Named revisions, lightweight branches, review, semantic comparison, and conflict resolution designed for transport models that may exceed a gigabyte.
06 / Principles
Private by default
Work locally without an account. Publish a project only when collaboration is useful.
Inspectable by design
No hidden defaults presented as scientific conclusions. Every result carries its evidence.
Built for iteration
Create a credible first model quickly, then improve it without breaking provenance or history.
Open at the edges
Use established transport and geospatial formats while keeping one coherent internal model.
Data sources
Bring the network you have.
Preserve the detail you need.
The evolving import catalogue covers OpenStreetMap, Visum, GTFS, GMNS, GeoPackage, GeoJSON, Shapefile, SUMO, MATSim, NeTEx, and OpenDRIVE. Each adapter declares exactly what it can import, what it cannot, and what must still be supplied.
OpenStreetMapVisumGTFSGMNSGeoPackageGeoJSONShapefileSUMOMATSimNeTExOpenDRIVE
07 / Product status
Built in visible, verifiable steps.
This page separates implemented foundations from active development and longer-term product direction.
Available foundation
Working today
- Windows desktop application
- Project-first home and workspace entry
- Live project and layer inspection
- Safe additive GeoJSON layer operations
- Validated Codex plugin package in private preview
- Verified numerical and graph components
In development
Being connected
- Complete local project lifecycle
- Guided source import and composition
- Transactional automatic model building
- Simulation and result workflows
- Large-project synchronization
- Domain-aware revision and merge
Product direction
Designed to grow
- Coordinated macro, meso, and micro models
- Broader multimodal simulation
- Demand estimation and calibration
- Optimization and accessibility analysis
- Team review and graphical conflict resolution
- Cross-platform product evolution
Moving Projects
Serious models.
Better decisions.
Moving Studio is being built by transport modellers for the people who design, test, and defend transport projects.
Return to the beginningWindows desktop preview
Download. Install. Start with a free licence.
No account or credit card is needed to download or work locally. Collaboration preview: keep a local project copy and exchange small encrypted changes. Recovery copies are transferred by your project administrator.
Windows 10 or later, 64-bit. Microsoft WebView2 Runtime is required; the .NET runtime is included. This is a development preview, without a trusted Windows publisher signature. Windows may show an unrecognized-publisher warning.