List of TrackerNet DestCode values

The request was partially successful.

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

FOI, Transport for London

 
 
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]http://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]http://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. http://www.whatdotheyknow.com/help/contact
3. http://www.whatdotheyknow.com/help/offic...

hide quoted sections

FOI, Transport for London

2 Attachments

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]http://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]http://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. http://www.whatdotheyknow.com/help/contact
3. http://www.whatdotheyknow.com/help/offic...

hide quoted sections

Looking for an EU Authority?

You can request documents directly from EU Institutions at our sister site AskTheEU.org . Find out more .

AskTheEU.org