Transit planning analysts

TransitGap Connection Delay Scenario Packs

Source: this release’s synthetic input → 4 output files. Observed 2026-09-08. Coverage: one example within the supported profile.

TransitGap builds transfer scenario packs from a declared six-file GTFS subset. You state the connections, the service date, walking times, and the delays you want to apply, and it computes whether each declared transfer would still be made under those assumptions. It reports scenario arithmetic over scheduled times, giving planning analysts a repeatable way to compare transfer outcomes across explicit what-if delays.

Open the workflow Download example

Reproduce schedule transfer outcomes under explicit delays

Free browser processingNo account requiredDownloadable resultsExplicit supported scope

YOUR WORKSPACE

Turn your input into a checked artifact

Load the synthetic example to explore the format, or choose your own supported JSON file. Processing happens on this device. Your input is not uploaded. The first run downloads the processing engine.

Open JSON file Input template

Your input · JSON, up to 8 MiB

Load an input to begin. Each workflow also has its own smaller domain limits.

Keep your original source. Unsupported inputs return an explanation. These workflows implement the stated mathematical or file-format checks; they do not establish physical performance, language quality or real-world reliability.

HOW TO USE IT

A repeatable input-to-output workflow

Provide the six-file GTFS subset plus your explicit connections, date, walk times, and delays as JSON.

The tool applies the delays to the scheduled times and evaluates each declared transfer as made or missed.

You download the scenario pack summarizing outcomes and the arithmetic behind them.

What you receive

Per-connection made or missed result
Slack and shortfall figures for each transfer
A scenario pack summarizing the applied delays

Supported scope and limits

Declared six-file GTFS subset and explicit inputs only
Produces schedule arithmetic, not actual arrival reliability
No route planner and no GTFS certification
Results depend entirely on the delays and walk times you declare

Read the exact input profile and examples. Start with the supplied template; this release does not guess missing settings.

OPTIONAL OFFLINE BATCH KIT

TransitGap automation kit

$349 one time

Proposed one-time batch automation kit: a versioned ZIP with an offline CLI runner, the TransitGap engine module, input fixtures, a verifier, and acceptance tests for generating connection delay scenarios offline. No recurring updates or support are promised. Checkout is unavailable at publication until a provider connection is established.

Browser processing and result downloads above are free. The proposed kit bundles the same core engine with an offline command-line runner, synthetic fixtures, source, checksums and acceptance tests for repeated jobs.

Checkout is unavailable. You can use the browser workflow now. The kit cannot be purchased on this page yet.

A future purchase delivers the named version as a ZIP. No subscription, future updates, hosted storage or hands-on review is included. Pricing is an introductory offer experiment.

The interest page accepts contact details. Do not send your source files.

Inspect the synthetic example

Input and actual engine output, available before any purchase.

Example provenance: synthetic source fixture, generated and checked on 2026-09-08. The following sizes and hashes are counted from the downloadable result ZIP; they are not customer data or performance claims.

File in example	Bytes	SHA-256 prefix
connections.csv	368	96a2a5b1c7b9
manifest.json	1,645	11b5d331a4e4
report.txt	1,116	f9cd28d26c9c
scenarios.json	945	0b549be34f1c

Before you start

Does this predict real delays?

No. It computes outcomes for the delays you declare; it does not model or predict actual arrival reliability.

Can it plan a route for me?

No. You supply the connections; it evaluates those transfers under your stated assumptions.

Reference material

These sources describe the surrounding formats and established tools. They do not endorse this product or prove demand for it.