← All sources
DailyLive-testedCommunity mirror

Mobility / National rail schedules and geometry

Community-generated Georgian Railway GTFS

Transitous publishes a community-generated Georgian Railway GTFS feed under ODbL-1.0. It contains 85 passenger stops, detailed railway shapes, 38 train-number routes, dated service exceptions, 416 generated trips, 4,089 calling times and stop-name translations in English, Georgian and Russian. Compared with the official Railway JSON backend it is openly licensed and map-ready; it is also derived rather than first-party and is not realtime.

01

Provenance and access

How the data is reached

Unauthenticated GTFS Schedule ZIP over HTTPS, generated by an open-source community pipeline. The ZIP has a duplicated attributions.txt member; robust consumers should tolerate duplicate ZIP member names while preserving the logical attribution row.

Reuse status

Open Database License 1.0 (ODbL-1.0); attributions.txt credits OpenStreetMap contributors

Read license or terms ↗
02

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

agency.txt and feed_info.txt

Agency identity and generated-feed coverage metadata.

9 fields
Field / pathTypeNull?ExampleMeaningFreshness
agency_idstringNogeorgian-railwayAgency identifierreference
agency_namestringNoGeorgian RailwayAgency namereference
agency_urlURLNohttps://gr.com.geOfficial agency sitereference
agency_timezoneIANA timezoneNoAsia/TbilisiSchedule timezonereference
feed_publisher_namestringNoJonah BrüchertDerived-feed publisherNot Georgian Railway itselfreference
feed_publisher_urlURLNohttps://gitlab.spline.de/spline/transitous/georgian-railways-gtfsGenerator and source repositoryreference
feed_langlanguage codeNoenDefault feed languagereference
feed_start_dateYYYYMMDDNo20260721First covered service datereference
feed_end_dateYYYYMMDDNo20261117Last covered service datereference

stops.txt

Passenger railway stations with coordinates.

4 fields
Field / pathTypeNull?ExampleMeaningFreshness
stop_namestringNoAbashaDefault station nameTranslations are availablereference
stop_idstringNo10784968460Stop identifierMany IDs appear to be OpenStreetMap object IDsreference
stop_latdecimal degreesNo42.204258WGS84 latitudereference
stop_londecimal degreesNo42.202137WGS84 longitudereference

shapes.txt

Detailed polyline points for generated national and international rail routes.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
shape_idstringNoshp_102_13Trip geometry identifierreference
shape_pt_latdecimal degreesNo41.65831WGS84 shape-point latitudereference
shape_pt_londecimal degreesNo41.677883WGS84 shape-point longitudereference
shape_pt_sequenceintegerNo1Point order within the shapereference
shape_dist_travelednumberNo123.049Cumulative distance along shapeObserved values behave as metresderived

routes.txt

Train-number routes with standard and extended rail-mode types.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
route_long_namestringYesOptional route descriptionBlank in all 38 recordsreference
route_short_namestringNo802Passenger-facing train numberreference
agency_idstringNogeorgian-railwayAgency foreign keyreference
route_typeintegerNo102GTFS or extended rail typeObserved: 2 standard rail, 102 long-distance rail, 106 regional railreference
route_idstringNo802Route identifierMatches the train number in the samplereference

calendar_dates.txt

Explicit dates on which each generated service runs.

3 fields
Field / pathTypeNull?ExampleMeaningFreshness
service_idstringNogeo-1198501Dated service keyreference
exception_typeinteger enumNo1Service is added on this dateOnly value 1 was observedreference
dateYYYYMMDDNo20260723Operating datereference

trips.txt

Generated dated rides mapped to train-number routes and shapes.

4 fields
Field / pathTypeNull?ExampleMeaningFreshness
route_idstringNo201Train-number route keyreference
service_idstringNogeo-19197563Dated service keyreference
shape_idstringNoshp_2_36Geometry foreign keyreference
trip_idstringNogeo-19197563Trip identifierreference

stop_times.txt

Scheduled passenger calling times ordered along each generated trip.

6 fields
Field / pathTypeNull?ExampleMeaningFreshness
trip_idstringNogeo-19197563Trip foreign keyreference
arrival_timeGTFS timeNo14:55:00Scheduled passenger arrivalreference
departure_timeGTFS timeNo14:55:00Scheduled passenger departurereference
stop_idstringNo6199471015Passenger stop foreign keyreference
stop_sequenceintegerNo0Calling orderStarts at zeroreference
shape_dist_travelednumberNo2643.542Distance along trip shapeObserved values behave as metresderived

attributions.txt

Required source attribution; the ZIP contains this filename twice but one logical row.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
organization_namestringNoOpenStreetMap contributorsContributing organization or communityreference
is_producer0/1 integerNo1Producer attribution flagreference
is_operator0/1 integerNo0Operator attribution flagreference
is_authority0/1 integerNo0Authority attribution flagreference
attribution_urlURLNohttps://www.openstreetmap.org/copyrightRequired attribution linkreference

translations.txt

Localized stop names; 85 stops in each of English, Georgian and Russian.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
table_namestringNostopsTranslated tableOnly stops observedreference
field_namestringNostop_nameTranslated fieldreference
languagelanguage codeNoenTranslation languageObserved en, ka and rureference
translationstringNoKutaisi ILocalized station namereference
record_idstringNo10056291745Stop-record keyreference
03

Representative evidence

Sample records

Feed coverage metadata

Retrieved 2026-07-22 13:45 Asia/Tbilisi

CSV
feed_publisher_name,feed_publisher_url,feed_lang,feed_start_date,feed_end_date
Jonah Brüchert,https://gitlab.spline.de/spline/transitous/georgian-railways-gtfs,en,20260721,20261117

Scheduled calling time

Retrieved 2026-07-22 13:45 Asia/Tbilisi

CSV
trip_id,arrival_time,departure_time,stop_id,stop_sequence,shape_dist_traveled
geo-19197563,14:55:00,14:55:00,6199471015,0,0
04

Boundaries

Reliability, caveats, and privacy

What held up

  • Every table was inspected and row-counted from the live processed ZIP
  • Four-month feed horizon is declared in feed_info
  • Shapes and calling times provide map-ready trip structure
  • Explicit ODbL and OpenStreetMap attribution are present

What can go wrong

  • Community-derived rather than first-party publication
  • Not realtime; no delay, actual arrival, cancellation, platform, seat or live-position fields
  • route_long_name is blank for every route
  • Duplicate attributions.txt ZIP member can confuse simplistic ZIP readers
  • Critical schedules should be compared with the official Railway API/page

Privacy boundary

  • Contains public railway infrastructure and schedules, not bookings or traveler identity