baltijas - GTFS transit data for Latvia

Active
gsvalbe-id-lv Latvia July 13, 2002 — December 31, 2027

About This Feed

baltijas is the GTFS feed gsvalbe-id-lv publishes for Latvia: 5,342 routes, 50,452 stops, 139 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.

Valid from July 13, 2002 to December 31, 2027.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 5,342 routes and 50,452 stops: stops near a point, departures, trips, timetables, live vehicle positions and source GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

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

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

    GET /v1/routes?origin=56.8225,24.69&destination=57.5326,25.5724
  • 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=52.209,20.949,59.663,28.22
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=baltijas
  • 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: 5,342 routes, 50,452 stops, 139 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 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-08-22

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

ZIP GTFS Feed - Corrected & Enriched
104.92 MB
Access: Submit the data request form The license for this work is not specified Content Hash: 9039eb383f06d960
ZIP Validation Report
0.12 MB
0 Errors
597,107 Warnings
665 Info
Top Issues
non ascii or non printable char 596,234
mixed case recommended field 463
stop too far from shape 227
GeoJSON GeoJSON Data
2.3 MB

Original Source

Obtained 2026-08-21

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

ZIP GTFS Source Data
135.8 MB
Available through API The license for this work is not specified Content Hash: ad5f8ca41bd2e6f1
ZIP Validation Report
0.25 MB
Available through API
0 Errors
787,622 Warnings
95,072 Info
Top Issues
non ascii or non printable char 782,417
missing bike allowance 1,989
mixed case recommended field 1,435

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
lietuvos-transporto 17292 (35.59%) 1747 (32.7%)
gobus-as-est 1149 (2.36%) 195 (3.65%)
latvia 1852 (3.81%) 110 (2.06%)
rigatest 1380 (2.84%) 63 (1.18%)
lsa 137 (0.28%) 58 (1.09%)
ida-viru 907 (1.87%) 52 (0.97%)
saraksti 1632 (3.36%) 48 (0.9%)
satiksme 1250 (2.57%) 39 (0.73%)
rzeknes-satiksme 26 (0.05%) 22 (0.41%)
pilsetas 333 (0.69%) 18 (0.34%)
vivi-atd 133 (0.27%) 12 (0.22%)
ltg-link 4 (0.07%)
flix-bus-eu 2 (0.04%)
kiasiadoriur 33 (0.07%)
prienur 24 (0.05%)

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 →