Follow this request
There is 1 person following this request
Act on what you've learnt
Similar requests
Mystery Operational Standards document
To Transport for London by Ian Jackson 30 March 2011
TrackCode locations
To Transport for London by Craig Poxon 25 February 2011
FOI request summary
To Transport for London by Felicity Groombridge 17 May 2011
Ticketless travel estimates
To Transport for London by Felicity Groombridge 31 August 2011
Journey demand and service supply breakdown
To Transport for London by Jeremy Christopher 27 March 2011
Data for Blackfriars Junction person counts
To Transport for London by Tommi Komulainen 7 September 2011
Closure between Gospel Oak to Stratford
To Transport for London by Tony Dodd 5 January 2010
Oyster Extension Permits
To Transport for London by Mike Hudgell 14 November 2009
Penalty Fares issued by TfL
To Transport for London by I Madder 6 December 2009
Audio Recordings for iBus and London Underground
To Transport for London by Richard Jarvis 5 March 2012
More similar requests
Event history details
Are you the owner of any commercial copyright on this page?
List of TrackerNet DestCode values
Chris Applegate made this Freedom of Information request to Transport for London
This request has an unknown status. We're waiting for Chris Applegate to read 2 recent responses and update the status.
From: Chris Applegate
14 February 2012
Dear Transport for London,
The TrackerNet API for train locations on the London Underground
contains a wealth of useful information for those wishing to make
third-party applications for Tube information.
However, the documentation does not adequately cover some aspects.
For the PredictionDetailed API call, the data returned includes an
XML Attribute called "DestCode" - a numeric value describing the
destination of the train. But nowhere in the documentation does it
detail the possible values for this code, and which destinations
these values correspond to. From a quick scan of the data it
appears the values go up to at least 750.
Therefore, I request, in a spreadsheet format such as Excel or CSV,
a complete list of all possible DestCode values used by the
TrackerNet system, with the destination (station or otherwise) that
each value corresponds to.
Yours faithfully,
Chris Applegate
Link to this
From: FOI
Transport for London
15 February 2012
Dear Mr Applegate
TfL Ref: FOI-1647-1112
Thank you for your email received by Transport for London (TfL) on 14
February 2012 asking for information about the DestCode values used by the
TrackerNet system.
Your request will be processed in accordance with the requirements of the
Freedom of Information Act and TfL’s information access policy.
A response will be provided to you by 13 March.
In the meantime, if you would like to discuss this matter further, please
do not hesitate to contact me.
Yours sincerely
Lee Hill
FOI Case Officer
FOI Case Management Team
General Counsel
Transport for London
-----Original Message-----
From: Chris Applegate
[[1]mailto:[FOI #105842 email]]
Sent: 14 February 2012 15:00
To: FOI
Subject: Freedom of Information request - List of TrackerNet DestCode
values
Dear Transport for London,
The TrackerNet API for train locations on the London Underground
contains a wealth of useful information for those wishing to make
third-party applications for Tube information.
However, the documentation does not adequately cover some aspects.
For the PredictionDetailed API call, the data returned includes an
XML Attribute called "DestCode" - a numeric value describing the
destination of the train. But nowhere in the documentation does it
detail the possible values for this code, and which destinations
these values correspond to. From a quick scan of the data it
appears the values go up to at least 750.
Therefore, I request, in a spreadsheet format such as Excel or CSV,
a complete list of all possible DestCode values used by the
TrackerNet system, with the destination (station or otherwise) that
each value corresponds to.
Yours faithfully,
Chris Applegate
-------------------------------------------------------------------
Please use this email address for all replies to this request:
[FOI #105842 email]
Is [TfL request email] the wrong address for Freedom of Information
requests to Transport for London? If so, please contact us using
this form:
[2]www.whatdotheyknow.com/help/contact
Disclaimer: This message and any reply that you make will be
published on the internet. Our privacy and copyright policies:
[3]www.whatdotheyknow.com/help/offic...
If you find this service useful as an FOI officer, please ask your
web manager to link to us from your organisation's FOI page.
-------------------------------------------------------------------
References
Visible links
1. mailto:[FOI #105842 email]
2. www.whatdotheyknow.com/help/contact
3. www.whatdotheyknow.com/help/offic...
hide quoted sections
Link to this
From: FOI
Transport for London
13 March 2012
London Underground Services Guide.doc
511K
Download
View as HTML
Your right to appeal copyright.pdf
16K
Download
View as HTML
Dear Mr Applegate
TfL Ref: FOI-1647-1112
Thank you for your email received by Transport for London (TfL) on 14
February asking for a list of TrackerNet DestCode values.
Your request has been considered in accordance with the requirements of
the Freedom of Information (FOI) Act and TfL’s information access policy.
You asked:
The TrackerNet API for train locations on the London Underground contains
a wealth of useful information for those wishing to make third-party
applications for Tube information.
However, the documentation does not adequately cover some aspects. For the
PredictionDetailed API call, the data returned includes an XML Attribute
called "DestCode" - a numeric value describing the destination of the
train. But nowhere in the documentation does it detail the possible values
for this code, and which destinations these values correspond to. From a
quick scan of the data it appears the values go up to at least 750.
Therefore, I request, in a spreadsheet format such as Excel or CSV, a
complete list of all possible DestCode values used by the TrackerNet
system, with the destination (station or otherwise) that each value
corresponds to.
Unfortunately TfL does not hold the information you have requested. The
specification does not include a table of values for the "DestCode” (see
attached) as this is not required. However, “Destination” is also
presented in the XML which is a text descriptor of a train’s destination
and this is what our applications use.
It is possible to get the text description of the destination from
“Destination” instead of "DestCode” in the XML.
Please see the attached information sheet for details of your right to
appeal.
Yours sincerely
Lee Hill
FOI Case Officer
FOI Case Management Team
General Counsel
Transport for London
-----Original Message-----
From: Chris Applegate
[[1]mailto:[FOI #105842 email]]
Sent: 14 February 2012 15:00
To: FOI
Subject: Freedom of Information request - List of TrackerNet DestCode
values
Dear Transport for London,
The TrackerNet API for train locations on the London Underground
contains a wealth of useful information for those wishing to make
third-party applications for Tube information.
However, the documentation does not adequately cover some aspects.
For the PredictionDetailed API call, the data returned includes an
XML Attribute called "DestCode" - a numeric value describing the
destination of the train. But nowhere in the documentation does it
detail the possible values for this code, and which destinations
these values correspond to. From a quick scan of the data it
appears the values go up to at least 750.
Therefore, I request, in a spreadsheet format such as Excel or CSV,
a complete list of all possible DestCode values used by the
TrackerNet system, with the destination (station or otherwise) that
each value corresponds to.
Yours faithfully,
Chris Applegate
-------------------------------------------------------------------
Please use this email address for all replies to this request:
[FOI #105842 email]
Is [TfL request email] the wrong address for Freedom of Information
requests to Transport for London? If so, please contact us using
this form:
[2]www.whatdotheyknow.com/help/contact
Disclaimer: This message and any reply that you make will be
published on the internet. Our privacy and copyright policies:
[3]www.whatdotheyknow.com/help/offic...
If you find this service useful as an FOI officer, please ask your
web manager to link to us from your organisation's FOI page.
-------------------------------------------------------------------
References
Visible links
1. mailto:[FOI #105842 email]
2. www.whatdotheyknow.com/help/contact
3. www.whatdotheyknow.com/help/offic...
hide quoted sections
Link to this
Things to do with this request
- Add an annotation (to help the requester or others)
- Download a zip file of all correspondence
- Write a reply
- Update the status of this request
- Request an internal review
- Respond to request