ids-jmk - GTFS transit data for Czech Republic

Active
IDS-JMK Czech Republic 7. srpna 2026 — 13. prosince 2026

About This Feed

ids-jmk is the GTFS feed IDS-JMK publishes for Czech Republic: 346 routes, 6,312 stops, 1 transit agencies. BusMaps checks and corrects it every week and serves the result through the API and as GTFS files.

Valid from 7. srpna 2026 to 13. prosince 2026.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 346 routes and 6,312 stops: stops near a point, departures, trips, timetables, live vehicle positions and the GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

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

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

    GET /v1/routes?origin=49.1445,16.6268&destination=49.2734,16.881
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • GTFS-RT positions inside the bounding box of the feed.

    GET /v1/rawVehiclePositions?boundingBox=48.659,15.533,49.66,17.644
  • GTFS files Free

    The corrected feed, the source feed, GeoJSON and the validation reports.

    GET /v1/getGtfsFeedsDownloads?feedName=ids-jmk
  • 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.

Per-feed pages: 346 routes, 6,312 stops, 1 agencies

Public pages merge every feed. Sign in to browse this feed on its own, which helps when you integrate or debug it.

Sign in →

GTFS files of this feed

Two builds: the copy BusMaps corrected and validated, and the original from IDS-JMK. The API returns either one for ?feedName=ids-jmk. Documentation →

Enhanced & Validated Recommended

Updated 2026-08-21

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

ZIP GTFS Feed - Corrected & Enriched
5.69 MB
Available through API only This work is licensed under Busmaps_licence_v1. Content Hash: b39f1693d7fed788
ZIP Validation Report
0.01 MB
Available through API only
1Errors
48Warnings
59Info
Top Issues
block trips with overlapping stop times1
expired calendar42
mixed case recommended field6
GeoJSON GeoJSON Data
0.33 MB
Available through API only

Original Source

Obtained 2026-08-07

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

ZIP GTFS Source Data
9.14 MB
Available through API only License: CC_BY Content Hash: 9c7a582c8a3120ff
ZIP Validation Report
0.02 MB
Available through API only
1Errors
191Warnings
1,095Info
Top Issues
block trips with overlapping stop times1
missing bike allowance104
expired calendar47

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
jizdnirady 617 (9.87%) 282 (81.5%)
jdfa 40 (0.64%) 24 (6.94%)
zsr 2 (0.58%)

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?

The source feed is what the agency published. The enhanced feed is the same data after BusMaps fixed the errors and inconsistencies and checked it against the GTFS specification. Use the enhanced feed in production.

Can I use this data in my application?

That depends on the licence the publisher set; you find it next to the files above. Most GTFS feeds allow free use with attribution. Check the licence before you integrate.

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, contact us and we will fix it.