This repository has been archived by the owner on Aug 27, 2024. It is now read-only.
forked from MobilityData/gtfs.org
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add About page This changes adds content for the About page, including licencing, how to contribute and a summary of GTFS history. * Update docs/About/index.md Co-authored-by: isabelle-dr <[email protected]> * Add important milestones Adding creation of Realtime and MobilityData to GTFS history. --------- Co-authored-by: isabelle-dr <[email protected]>
- Loading branch information
1 parent
513803c
commit e6e1d8d
Showing
3 changed files
with
26 additions
and
8 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# About | ||
|
||
GTFS.org is the central documentation platform for the General Transit Feed Specification. This site and its contents are maintained by [MobilityData](https://mobilitydata.org/). | ||
|
||
Thank you to [Andrew Byrd](https://www.linkedin.com/in/byrdandrew) for purchasing and lending use of the GTFS.org domain name and providing leadership for the community. | ||
|
||
## Contributing to GTFS.org | ||
|
||
To propose edits to the content of this website, contact MobilityData at [[email protected]](mailto:[email protected]) or visit the [GTFS.org GitHub Repository](https://github.com/mobilitydata/gtfs.org) to submit your edits as pull requests. | ||
|
||
## GTFS evolution | ||
|
||
GTFS started with a collaboration between TriMet in Portland, Oregon, and Google. TriMet worked with Google to format their transit data into an easily maintainable and consumable format that could be imported into Google Maps. This transit data format was originally known as the Google Transit Feed Specification (GTFS). | ||
|
||
As a result of developer innovation, GTFS data is now being used by a variety of third-party software applications for many different purposes, including trip planning, timetable creation, mobile data, data visualization, accessibility, and analysis tools for planning. | ||
|
||
In 2010, the GTFS format name was changed to the General Transit Feed Specification to accurately represent its use in many different applications outside of Google products. Real-time information capabilities were added to the specification with the creation of GTFS Realtime in 2011, and in 2019, the non-profit [MobilityData](https://mobilitydata.org/) was established to further maintain GTFS with the help of the community. | ||
|
||
Among public transportation data formats, GTFS stands out because it was conceived to meet specific, practical needs in communicating service information to passengers, not as an exhaustive vocabulary for managing operational details. It is designed to be relatively simple to create and read for both people and machines. | ||
|
||
For further background on the origins of GTFS, see [Pioneering Open Data Standards: The GTFS Story](https://beyondtransparency.org/chapters/part-2/pioneering-open-data-standards-the-gtfs-story/) and [How Google and Portland’s TriMet Set the Standard for Open Transit Data in Streetsblog SF](https://sf.streetsblog.org/2010/01/05/how-google-and-portlands-trimet-set-the-standard-for-open-transit-data). | ||
|
||
## License | ||
|
||
Except as otherwise noted, the content of this site is licensed under the [Creative Commons Attribution 3.0 License](https://creativecommons.org/licenses/by/3.0/), and code samples are licensed under the [Apache 2.0 License](https://www.apache.org/licenses/LICENSE-2.0). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters