nippokisen - GTFS transit data for Japan
ExpiredAbout This Feed
nippokisen is the GTFS feed Public-transport-open-data-center publishes for Japan: 2 routes, 3 stops, 1 transit agencies. One-time and recurring data deliveries require the data request form and manual approval by our team.
Active from April 1, 2021 to December 31, 2021; 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 2 routes and 3 stops: stops near a point, departures, trips, timetables. The requests below use the coordinates of this feed. File deliveries require a separate request and manual approval. Request data →
- Stops around a point Free
Stops within a radius of a coordinate.
GET /v1/stopsInRadius?location=32.657,131.7973&radius=1000 - Next departures Free
Departures at the nearby stops, with real-time delays where the agency publishes them.
GET /v1/nextDepartures?location=32.657,131.7973&radius=500&results=30 - A-to-B trip planning Free
Itineraries between two points on this network.
GET /v1/routes?origin=32.657,131.7973&destination=32.6615,131.804 - Route timetables Pro
Directions, stop order and the schedule of one route.
GET /v1/line?routeId={routeId} - AI agents (MCP) Free
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.
GTFS Data Products
One-time and recurring data deliveries require a data request and manual approval by our team. Submit the form to discuss coverage and delivery terms.
Open the data request form →Enhanced & Validated Recommended
Updated 2026-09-11Cleaned, corrected, and validated against GTFS specifications. View corrections.
Original Source
Obtained 2021-04-23Unmodified GTFS data from official sources. May contain errors or inconsistencies.
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 →