Ero sivun ”Journeys API” versioiden välillä

732 merkkiä lisätty ,  6. lokakuuta 2014 kello 23.37
Rivi 1: Rivi 1:
==Concept==
==Concept==
Journeys API allows developers and clients to access following information via REST API
Journeys API allows developers and clients to access Public Transport information via REST API
* '''Routes''' on which public transport services operate
* '''Routes''' on which public transport services operate
* '''Lines''', or in other words grouping of routes. For example Line 2, which runs from Rauhaniemi to Pyyninkintori in Tampere
* '''Lines''', or in other words grouping of routes. For example Line 2, which runs from Rauhaniemi to Pyyninkintori in Tampere
* '''Journeys''' made by public transport vehicles on certain line and route at certain day and time
* '''Journeys''' made by public transport vehicles on certain line and route at certain day and time
* '''Stops''' where public transport vehicles stop during their journeys
* '''Stops''' where public transport vehicles stop during their journeys
* '''Vehicle Monitoring''' where public transport vehicles stop during their journeys
The API allows accessing these concepts as hierarchy of objects (see later) as well as performing searches.
The API allows accessing these concepts as hierarchy of objects (see later) as well as performing searches.
Journeys API combines together various data sources and offers their contents to developers and clients via JSON requests made over HTTP. Static data (ie. lines, routes, stops and time schedules) comes from GTFS (https://developers.google.com/transit/gtfs/) files. This data is augmented with proprietary MALA format (tariff zones, municipalities). Real-time data (observations on where public transport vehicles are currently operating) are polled from siri.ij2010.tampere.fi SIRI VM endpoint once in a second. This data includes for example real-time coordinate updates for public transport vehicles.
[[File:Journeys_API_Network.png]]


==API Entities==
==API Entities==
0

muokkausta