LONDON'S INFRASTRUCTURES

The infrastructures integrated in the iCity platform by the City of London are mainly related with the environmental data and mobility for public transportation services (TFL)
 
 

Air Quality 

 
Description
 
King’s College London Environmental Research Group of Strand. This infrastructure offers information about environmental air quality sensors placed in the city of London.
 

Policies and rules
 
Service limitation: Number of actions per unit time is restricted to 10 queries/second.
 
Cost: Free
 

Details
 
Air Quiality allows to retrieve the mesuared values of various physical properties such as CO-COncentration, PM10-Concentration... These mesurements are performed, along the time, through a network of measurement stations. After being statiscally processed those data are collected in a central server.
Air Quality includes these kind of sensors:
 
Air quality sensors : air_qualityNO2, air_qualitySO, air_qualityO3, air_qualityPM10, air_qualityPM25
 
You can find detailed information about Air quality in: http://www.londonair.org.uk/LondonAir/Default.aspx
 
 
Technical name

PLTLDN001

Properties
Units
  • urn:air_qualityNO2
  • urn:air_qualitySO2
  • urn:air_qualityPM10
  • urn:air_qualityO3
  • urn:air_qualityPM25
µg/m3
µg/m3
µg/m3
µg/m3
µg/m3
Status: INTEGRATED.
 
 

Journey Planner 

 
Description
 
This infrastructure enables application developers to freely access the same journey solutions that are available to TfL customers on the TfL website and mobile site. Offers information about the best route to arrive to a defined place by introducing some parameters as well as the starting point.
 

Policies and rules
 
Service limitation: Number of actions per unit time is restricted to 10 queries/second.
 
Cost: Free
 

Details
 
This function allows planning from/to stations, stops, places of interest, geo-locations, addresses or postcodes.
TfL provides a range of formats – in this case REST-like API responding with XML and JSON.
To request for information, please use the property urn:infocity:trip , and include parameters in the request call like in the following example:
 
 
Example Journey Request Stop to Stop
(Alexander Road --> Prince of Wales Gate) at 01/08/2011, 0800h
GET http://icity-gw.icityproject.com:8080/developer/api/observations/last?id=1479&property=urn:infocity:trip&n=1&filter= language=en;sessionID=0;place_origin=London;type_origin=stop;name_origin=Alexander%20Road;place_destination=London;type_destination=stop;name_destination=Prince%20Of%20Wales%20Gate;itdDate=20110801;itdTime=0800
Example Journey Request Address to Address
(12 Chatham Street --> 42 Gillingham Street)
GET http://icity-gw.icityproject.com:8080/developer/api/observations/last?id=1479&property=urn:infocity:trip&n=1&filter=language=en;sessionID=0;place_origin=London;type_origin=address;name_origin=12%20Chatham%20Street;place_destination=London;type_destination=address;name_destination=42%20Gillingham%20Street
Example Journey Request Postcode to Postcode
(SW1H 0BD -> AL2 1AE)
GET http://icity-gw.icityproject.com:8080/developer/api/observations/last?id=1479&property=urn:infocity:trip&n=1&filter= language=en;sessionID=0;place_origin=London;type_origin=locator;name_origin=SW1H%200BD;place_destination=London;type_destination=locator;name_destination=AL2%201AE
 
Example Journey Request POI to POI
(O2 --> Madame Tussauds)
GET http://icity-gw.icityproject.com:8080/developer/api/observations/last?id=1479&property=urn:infocity:trip&n=1&filter= language=en;sessionID=0;place_origin=London;type_origin=poi;name_origin=O2;place_destination=London;type_destination=poi;name_destination=Madame%20Tussauds
 
 
Example Journey Request Stop to Coordinate
 
GET http://icity-gw.icityproject.com:8080/developer/api/observations/last?id=1479&property=urn:infocity:trip&n=1&filter= language=en;sessionID=0;place_origin=London;type_origin=stop;name_origin=Alexander%20Road;name_destination=-0.179349:51.608163:WGS84[DD.ddddd]:71%20Fallowcourt%20Avenue,%20N12;type_destination=coord;itdDate=20110801&itdTime=0800
You can find detailed information about Journey Planner in: journeyplanner.tfl.gov.uk
 
 
 
Technical name
 
PLTTFL0011

Properties
      Units
  • urn:infocity:trip
trip
Parameters
      Value Example
  • filter
language=en;
sessionID=0;
place_origin=London;
type_origin=address;
name_origin=12%20Chatham%20Street;
place_destination=London;
type_destination=address;
name_destination=42%20Gillingham%20Street

Status: INTEGRATED.
 
 
 

Alert ME 

 
Description
 
This infrastructure data is a Smart Home platform. In this case, we will have an instance of "AlertMe Smart Energy" (see www.alertme.com) in the home of each triallist based in London.
The primary data is live and historical whole-house electricity use. This could be used in many ways. e.g. to compare homes with each other, or mix it with national grid carbon mix data to deduce the homes' carbon footprint, etc.  
 
 
Policies and rules
 
Service limitation: Number of actions per unit time is restricted to 10 queries/second.
 
Cost: Free
 
 
Details
 
Information about energy, temperature and signal measurements.
 
 
Technical name
 
PLTLDN0006

Properties
Units
  • urn:energy
  • urn:signal
  • urn:temperature
J
%
Cel
Status: INTEGRATED.
 
 

Smart Parking Croydon 

 
Description
 
This infrastructure lets you query for most locations and returns:
  • Lot details
  • Lot operating hours
  • Lot tariffs
  • Lot occupancies
  • Unavailable bays
 
Lots are customer-defined groupings of parking bays within an overall site, and can include bays in multiple and non-contiguous sectors so long as they are all the same type; i.e. disabled, paid, residential etc. Each Lot’s spatial GPS co-ordinates are provided as a single central point and not by each individual bay.  
 
 
Policies and rules
 
Service limitation: None. 
 
Cost: Free
 
Details
 
The APIs are RESTful; they are URLs with parameters submitted via HTTP. How the API responds is dependent on the URL string that is used, and the content of your HTTP request header. The URL query string dictates the specific API operations.
 
To request for information, please use one of the following properties and include the siteCode parameter in the request call like in the following example:
GET http://icity-gw.icityproject.com:8080/developer/api/observations/last?property=urn%3Aparking%3Atariffs&n=1&infrastructureid=40&filter=siteCode%3DUKLCYWC01

 
Status: Coming soon.