This feed has expired Service dates: 2020-01-29 - 2023-01-29

express - GTFS transit data for Japan

Expired
Jorudan-Cloud-contents-Service Japan January 29, 2020 — January 29, 2023

About This Feed

express is the GTFS feed Jorudan-Cloud-contents-Service publishes for Japan: 31 routes, 126 stops, 1 transit agencies. BusMaps provides the original source through the API. Corrected and validated builds are not available in the API and require the data request form.

Active from January 29, 2020 to January 29, 2023; the schedule has ended. The files stay available for analysis.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 31 routes and 126 stops: stops near a point, departures, trips, timetables and source GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

    GET /v1/stopsInRadius?location=36.3301,138.9739&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

    GET /v1/nextDepartures?location=36.3301,138.9739&radius=500&results=30
  • Itineraries between two points on this network.

    GET /v1/routes?origin=36.3301,138.9739&destination=36.4689,139.1834
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=express
  • Claude, ChatGPT or any MCP client asks this network questions in plain language.

    https://mcp.busmaps.com/mcp

Base URL https://capi.busmaps.com:8443. Send the key in the capi-key header. Route ids come from the responses above.

31
Routes
126
Stops
1
Agencies

GTFS Data Products

Request enhanced data access

The API provides source files only. Submit the data request form to discuss enhanced or custom data, coverage, and delivery terms.

Open the data request form →

Enhanced & Validated Recommended

Updated 2026-09-11

Cleaned, corrected, and validated against GTFS specifications. View corrections.

ZIP GTFS Feed - Corrected & Enriched
0.05 MB
Access: Submit the data request form This work is licensed under Busmaps_licence_v1. Content Hash: 2fc8e01423a61aeb
ZIP Validation Report
0.02 MB
0 Errors
274 Warnings
6 Info
Top Issues
mixed case recommended field 212
missing recommended field 30
duplicate route name 16
GeoJSON GeoJSON Data
0.01 MB

Original Source

Obtained 2020-02-14

Unmodified GTFS data from official sources. May contain errors or inconsistencies.

ZIP GTFS Source Data
0.05 MB
Available through API License: CC_BY_4.0 Content Hash: e04d7f73800a492d
ZIP Validation Report
0.03 MB
Available through API
3 Errors
2,753 Warnings
56 Info
Top Issues
missing required column 3
missing timepoint value 2,101
mixed case recommended field 345

Frequently Asked Questions

What is GTFS data?

GTFS, the General Transit Feed Specification, is the open format transit agencies use to publish schedules, stops and route shapes. Trip planners, routing engines and analytics tools read it directly.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. API plans include source data only. Enhanced data requires a separate request through the data request form. Request access through the form →

Can I use this data in my application?

Source-data use depends on the licence set by the publisher; check it before integration. Enhanced and custom data is supplied under terms agreed for your coverage, delivery, and intended use.

How do I validate a GTFS feed?

Every feed here ships with a validation report of errors and warnings. For an independent check, run the MobilityData GTFS Validator. The enhanced feed has the critical issues resolved.

All data comes from public sources. If a file was posted in error, carries a wrong licence or lacks attribution, we will fix it.

Contact us →