Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/public-transport/friendly-public-transport-format

A format for APIs, libraries and datasets containing and working with public transport data.
https://github.com/public-transport/friendly-public-transport-format

fptf gtfs open-data public-transportation spec transport

Last synced: about 1 month ago
JSON representation

A format for APIs, libraries and datasets containing and working with public transport data.

Host: GitHub
URL: https://github.com/public-transport/friendly-public-transport-format
Owner: public-transport
License: cc-by-sa-4.0
Created: 2017-02-12T22:01:46.000Z (over 7 years ago)
Default Branch: master
Last Pushed: 2023-06-16T13:32:13.000Z (over 1 year ago)
Last Synced: 2024-04-14T07:11:20.144Z (5 months ago)
Topics: fptf, gtfs, open-data, public-transportation, spec, transport
Homepage:
Size: 101 KB
Stars: 116
Watchers: 14
Forks: 1
Open Issues: 19
Metadata Files:
- Readme: README.md
- Contributing: contributing.md
- License: license
- Code of conduct: code-of-conduct.md

Awesome Lists containing this project

README

        # Friendly Public Transport Format (FPTF)

This repo outlines **a format for APIs, libraries and datasets containing and working with public transport data.** See **[the spec](spec/readme.md)** and the [list of JS modules](modules.md).

[![npm version](https://img.shields.io/npm/v/friendly-public-transport-format.svg)](https://www.npmjs.com/package/friendly-public-transport-format)

![CC-licensed](https://img.shields.io/github/license/public-transport/friendly-public-transport-format.svg)

[![chat on gitter](https://badges.gitter.im/public-transport/Lobby.svg)](https://gitter.im/public-transport/Lobby)

It tries to keep things simple:

- JSON and [ndjson](http://ndjson.org) only

- a flat, intuitive representation of public transport timetables & infrastructure

- conceptually inspired by the de-facto standard [GTFS](https://developers.google.com/transit/gtfs/)

Specifically, it trades

- efficiency for consumability: GTFS sets feel like database dumps.

- completeness for ease-of-use: Only basic attributes are required, most is optional.

Things still missing:

- concise definitions

- clear naming & recommendations for optional data

There's also a work-in-progress spec for APIs building on top of the FPTF format: the [*Friendly Public Transport Interface* for JavaScript (FPTI-JS)](https://github.com/public-transport/fpti-js).

## Contributing

We are looking forward to discuss & extend this format further! If you have a question or want to propose changes, go to [the issues page](https://github.com/public-transport/friendly-public-transport-format/issues). Keep our [contributing guidelines in mind](contributing.md). Note that, by participating in this project, you commit to the [code of conduct](code-of-conduct.md).