GTFS CSV: agency, stops, routes, trips, stop_times, calendar; GTFS-RT JSON or protobuf base64; NeTEx and SIRI XML subsets; explicit mappings.
Technical demonstration
Synthetic data · independent implementation · repeatable test scenarios
Transit integration validation
GTFS · GTFS-RT · NeTEx · SIRI
Inconsistent identifiers and stale data can pass through an integration even when HTTP transport succeeds.
Buyer outcome: JSON/CSV report with discrepancies, evidence and PASS/FAIL result against agreed rules.
First scope: sample / export / test environment. Responsibility covers the agreed rules and acceptance report.
Parsers → canonical journey stops → file, relationship and time validation → cross-format comparison.
Stale feeds, unknown trips, invalid sequences, duplicate entities, malformed XML, missing references and mappings.
JSON/CSV report: run identifier, input hash, rule, expected and actual values, evidence and acceptance result.
The valid fixture produces no discrepancies. Each negative scenario detects its assigned rule. Repeating the input produces the same report.
Controlled change: the GTFS-RT feed timestamp is moved back by 4812 seconds. Other data remains reference data.
Verifiable scope
Acceptance package
Data validation and the test for correct error detection are two separate results.
Run validation or scenarios
The dataset is available in the Input tab. The report is created from the rules actually executed.
What you can verify here
Data validation method, error handling, discrepancy report, PASS/FAIL scenarios and acceptance criteria.
Problem → input → result → acceptance
The valid fixture produces no discrepancies. Each negative scenario detects its assigned rule. Repeating the input produces the same report.
The public scenario covers the documented NeTEx/SIRI subset, relationships, mappings and data consistency. The GTFS profile requires calendar.txt, ordered stop_times and explicit ID mappings. Integration with the operator environment and the required compliance profile are configured for each project. Evaluation clock: 2026-09-16 12:00 UTC.
Describe the scope