Knowledge

GTFS Realtime

Source 📝

606: 293: 168: 66: 25: 501:
proposed 2 additional feed entity types: Stop and Trip Modifications. These allow agencies to broadcast new detour paths of routes and new temporary stops. The change has been released to users in the Transit app across several agencies. On March 11, 2024, the proposal was merged and released by GTFS
617:
Alerts typically don't update as often as Vehicle Positions or Trip Updates. Each Alert stores the cause (such as labour strike or a mechanical fault) of an incident, along with its effect (reduced service, detour, stop cancellation, etc.). Alerts also contain detailed headers, descriptions, urls,
596:
also contains the current latitude and longitude of the vehicle, and can also include bearing, odometer, and speed in m/s. Finally, it can also contain information on how crowded the bus is, known as occupancy status, and status of road congestion experienced by the vehicle.
493:
Integrated Travel Project began validating GTFS Schedule and Realtime feeds published by municipality and county public transport agencies within California. Monthly reports are published on the errors in agency data, along with analysis of typical street speeds and traffic.
477:
A proposal that was created on July 28, 2015 and merged on Aug 15, 2015 allowed the combination of several feed entity types into a single feed. While the majority of agencies separate feed entity types (Vehicle Positions, Trips, and Alerts), some feeds are still joined.
549:, typically every few seconds to minutes. Agencies typically refresh data in frequencies ranging between 1 second to 1 minute. There is no standard for streaming GTFS Realtime data, also support is built in to allow for deletion of items from previous iterations. 541:
Agencies supporting GTFS-Realtime typically provide separate urls for the three separate feed types, and may choose to only provide some of the feeds. Unlike GTFS Static, many agencies may require developers to request an API key via email or a web form.
567:
This feed contains an array of Trip Updates. Each trip update enumerates a description of a trip (trip id, route id, start time and date, direction), last updated time, may include an associated vehicle number and route number, and contains an array of
775: 510:
The GTFS Realtime specification is defined by a .proto file hosted by Google. Data is serialized into raw bytes by the server and then deserialized by a client. Officially supported GTFS-rt binding libraries have been built in
481:
On August 30, 2021, an experimental feed entity types, Shapes, was released. Shapes has the ability to update route shapes in real time to reflect detour, as route updates are either reflected by referencing an existing
618:
images, and a list of routes or stops affected (known as the Informed Entity). Alerts specify their beginning and expiration times using "active periods". Alerts can be localised into several languages.
561:, a trip refers to an operator driving a fixed-route vehicle from the start of the route to the end. A new trip is started for when the vehicle turns around at the end of its route. 451:
The standard is used by public transport agencies globally, including the United States, Canada, most countries in the European Union, United Kingdom, Australia, New Zealand, and in
538:
There are currently three official feed types defined in the standard, TripUpdates, VehiclePositions, and Alerts. Shapes, Trip Modifications, and Stops are currently experimental.
920: 613:
Alerts can be shown to mapping application users to alert them of detours, cancellations, or other service changes. This feed contains an array of
490: 592:
can also contain a basic description of the trip, such as its trip id, start and stop times, route number, and relationship to the schedule. The
576:
can define past, current, and future stop times, delays, and cancellations. The stop id references the GTFS Schedule feed the agency provides.
564:
The Trip Update feed allows maps to show the departure or arrival times of vehicles, and allows routing algorithms to update their directions.
584:
Vehicle Positions are sometimes shown on mapping applications to aid users in tracking the location of buses. This feed contains an array of
925: 448:(AVL) systems. Trip arrival times are computed using machine learning models that analyse historical positional data and timetables. 272: 254: 149: 52: 930: 935: 192: 87: 80: 38: 235: 130: 524: 207: 102: 940: 824: 727: 437:
agencies share real-time vehicle locations, arrival time predictions, and alerts such as detours and cancellations via
660: 532: 516: 333: 214: 109: 702: 445: 528: 866: 396: 221: 116: 678: 890: 76: 471: 375: 203: 98: 752:"Allow multiple feed entity types in a single feed by egorich239 · Pull Request #7 · google/transit" 605: 842: 303: 44: 380: 292: 463:
On 22 August 2011, a first version of GTFS-rt was released by Google. This data was shown to
438: 434: 388: 368: 177: 228: 123: 914: 498: 464: 182: 167: 65: 545:
Developers then write programs to periodically fetch an agency's web API over
520: 800: 776:"Cal-ITP unveils new open data standard to improve transit agency operations" 843:"Provide realtime trip information with TripUpdates - Transit Partners Help" 825:"transit/gtfs-realtime/proto/gtfs-realtime.proto at master · google/transit" 751: 452: 801:"GTFS Trip-Modifications by gcamp · Pull Request #403 · google/transit" 635: 703:"Know when your bus is late with live transit updates in Google Maps" 531:. Unofficial libraries have been written in other languages, such as 604: 444:
Realtime location data is created continuously by an agency from
558: 546: 512: 486:
or by defining in real time a new shape as an encoded polyline.
430: 161: 59: 18: 407: 728:"Google Maps Now Features Alerts On Subway Service Changes" 297:
Example of GTFS Realtime Visualisation of Los Angeles Metro
188: 609:
MTA Subway GTFS-rt Alerts being posted on Transit App
402: 386: 374: 364: 356: 332: 314: 302: 195:. Unsourced material may be challenged and removed. 636:"Reference - General Transit Feed Specification" 175:An editor has performed a search and found that 8: 285: 16:Standard for real-time public transport data 53:Learn how and when to remove these messages 273:Learn how and when to remove this message 255:Learn how and when to remove this message 150:Learn how and when to remove this message 627: 497:In September 2023, Swiftly and the app 867:"Vehicle Positions | Realtime Transit" 284: 86:Please improve this article by adding 679:"Revision history | Realtime Transit" 7: 921:Public transport information systems 193:adding citations to reliable sources 891:"Service Alerts | Realtime Transit" 474:began showing alerts from GTFS-rt. 14: 659:Parkford, Stan (30 August 2021). 34:This article has multiple issues. 726:Del Signore, John (2012-07-31). 291: 166: 64: 23: 42:or discuss these issues on the 1: 88:secondary or tertiary sources 360:Transit realtime data format 926:Scheduling (transportation) 181:to establish the subject's 957: 661:"How do predictions work?" 588:. Like Trip Updates, each 446:automatic vehicle location 290: 178:sufficient sources exist 931:Web syndication formats 610: 343:; 6 months ago 320:; 13 years ago 318:27 September 2011 75:relies excessively on 936:Computer file formats 895:Google for Developers 871:Google for Developers 683:Google for Developers 608: 429:) is an extension to 707:Official Google Blog 189:improve this article 941:Real-time computing 665:Swiftly Help Center 287: 847:support.google.com 611: 559:GTFS Specification 365:Extended from 341:11 March 2024 304:Filename extension 580:Vehicle positions 420: 419: 381:De facto standard 283: 282: 275: 265: 264: 257: 239: 160: 159: 152: 134: 57: 948: 905: 904: 902: 901: 887: 881: 880: 878: 877: 863: 857: 856: 854: 853: 839: 833: 832: 821: 815: 814: 812: 811: 797: 791: 790: 788: 787: 772: 766: 765: 763: 762: 748: 742: 741: 739: 738: 723: 717: 716: 714: 713: 699: 693: 692: 690: 689: 675: 669: 668: 656: 650: 649: 647: 646: 632: 586:VehiclePositions 485: 439:Protocol Buffers 435:public transport 416: 413: 411: 409: 392: 369:Protocol Buffers 351: 349: 344: 328: 326: 321: 295: 288: 278: 271: 260: 253: 249: 246: 240: 238: 197: 170: 162: 155: 148: 144: 141: 135: 133: 92: 68: 60: 49: 27: 26: 19: 956: 955: 951: 950: 949: 947: 946: 945: 911: 910: 909: 908: 899: 897: 889: 888: 884: 875: 873: 865: 864: 860: 851: 849: 841: 840: 836: 823: 822: 818: 809: 807: 799: 798: 794: 785: 783: 774: 773: 769: 760: 758: 750: 749: 745: 736: 734: 725: 724: 720: 711: 709: 701: 700: 696: 687: 685: 677: 676: 672: 658: 657: 653: 644: 642: 634: 633: 629: 624: 603: 594:VehiclePosition 590:VehiclePosition 582: 555: 508: 483: 461: 453:Yokohama, Japan 425:(also known as 406: 387: 352: 347: 345: 342: 340: 324: 322: 319: 315:Initial release 310: 298: 279: 268: 267: 266: 261: 250: 244: 241: 204:"GTFS Realtime" 198: 196: 186: 171: 156: 145: 139: 136: 99:"GTFS Realtime" 93: 91: 85: 81:primary sources 69: 28: 24: 17: 12: 11: 5: 954: 952: 944: 943: 938: 933: 928: 923: 913: 912: 907: 906: 882: 858: 834: 816: 792: 767: 743: 718: 694: 670: 651: 626: 625: 623: 620: 602: 599: 581: 578: 574:StopTimeUpdate 570:StopTimeUpdate 554: 551: 507: 504: 470:In July 2012, 460: 457: 418: 417: 404: 400: 399: 393: 384: 383: 378: 372: 371: 366: 362: 361: 358: 357:Type of format 354: 353: 338: 336: 334:Latest release 330: 329: 316: 312: 311: 308: 306: 300: 299: 296: 281: 280: 263: 262: 174: 172: 165: 158: 157: 72: 70: 63: 58: 32: 31: 29: 22: 15: 13: 10: 9: 6: 4: 3: 2: 953: 942: 939: 937: 934: 932: 929: 927: 924: 922: 919: 918: 916: 896: 892: 886: 883: 872: 868: 862: 859: 848: 844: 838: 835: 830: 826: 820: 817: 806: 802: 796: 793: 781: 777: 771: 768: 757: 753: 747: 744: 733: 729: 722: 719: 708: 704: 698: 695: 684: 680: 674: 671: 666: 662: 655: 652: 641: 637: 631: 628: 621: 619: 616: 607: 600: 598: 595: 591: 587: 579: 577: 575: 571: 565: 562: 560: 552: 550: 548: 543: 539: 536: 534: 530: 526: 522: 518: 514: 505: 503: 502:maintainers. 500: 495: 492: 487: 479: 475: 473: 468: 466: 458: 456: 454: 449: 447: 442: 440: 436: 432: 428: 424: 423:GTFS Realtime 415: 405: 401: 398: 394: 390: 385: 382: 379: 377: 373: 370: 367: 363: 359: 355: 337: 335: 331: 317: 313: 307: 305: 301: 294: 289: 286:GTFS Realtime 277: 274: 259: 256: 248: 245:February 2024 237: 234: 230: 227: 223: 220: 216: 213: 209: 206: –  205: 201: 200:Find sources: 194: 190: 184: 180: 179: 173: 169: 164: 163: 154: 151: 143: 140:February 2024 132: 129: 125: 122: 118: 115: 111: 108: 104: 101: –  100: 96: 95:Find sources: 89: 83: 82: 78: 73:This article 71: 67: 62: 61: 56: 54: 47: 46: 41: 40: 35: 30: 21: 20: 898:. Retrieved 894: 885: 874:. Retrieved 870: 861: 850:. Retrieved 846: 837: 828: 819: 808:. Retrieved 804: 795: 784:. Retrieved 782:. 2022-06-07 780:Mass Transit 779: 770: 759:. Retrieved 755: 746: 735:. Retrieved 731: 721: 710:. Retrieved 706: 697: 686:. Retrieved 682: 673: 664: 654: 643:. Retrieved 639: 630: 614: 612: 593: 589: 585: 583: 573: 569: 566: 563: 556: 553:Trip updates 544: 540: 537: 509: 496: 488: 480: 476: 469: 462: 450: 443: 441:web server. 426: 422: 421: 269: 251: 242: 232: 225: 218: 211: 199: 187:Please help 176: 146: 137: 127: 120: 113: 106: 94: 74: 50: 43: 37: 36:Please help 33: 472:Google Maps 465:Google Maps 433:, in which 389:Open format 915:Categories 900:2023-08-07 876:2023-08-07 852:2023-08-07 810:2023-12-07 786:2024-02-02 761:2023-12-07 737:2023-08-07 712:2024-02-02 688:2023-07-31 645:2023-07-31 622:References 521:Javascript 348:2024-03-11 325:2011-09-27 215:newspapers 183:notability 110:newspapers 77:references 39:improve it 732:Gothamist 491:CalTrans' 489:In 2022, 412:/realtime 397:CC BY 3.0 45:talk page 640:gtfs.org 506:Standard 484:shape_id 376:Standard 615:Alerts. 557:In the 499:Transit 467:users. 459:History 427:GTFS-rt 403:Website 346: ( 323: ( 229:scholar 124:scholar 829:GitHub 805:GitHub 756:GitHub 601:Alerts 572:. The 527:, and 525:Python 231:  224:  217:  210:  202:  126:  119:  112:  105:  97:  395:Yes, 236:JSTOR 222:books 131:JSTOR 117:books 547:HTTP 533:Rust 517:Java 513:.NET 431:GTFS 410:.org 408:gtfs 208:news 103:news 339:2.0 309:.pb 191:by 79:to 917:: 893:. 869:. 845:. 827:. 803:. 778:. 754:. 730:. 705:. 681:. 663:. 638:. 535:. 529:Go 523:, 519:, 515:, 455:. 90:. 48:. 903:. 879:. 855:. 831:. 813:. 789:. 764:. 740:. 715:. 691:. 667:. 648:. 414:/ 391:? 350:) 327:) 276:) 270:( 258:) 252:( 247:) 243:( 233:· 226:· 219:· 212:· 185:. 153:) 147:( 142:) 138:( 128:· 121:· 114:· 107:· 84:. 55:) 51:(

Index

improve it
talk page
Learn how and when to remove these messages

references
primary sources
secondary or tertiary sources
"GTFS Realtime"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message

sufficient sources exist
notability
improve this article
adding citations to reliable sources
"GTFS Realtime"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message
Learn how and when to remove this message

Filename extension
Latest release

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.