To get things up and running, you'll need to:
- Register an app with TfL
- You'll need to create a product subscription under
Products -> <product name>- At the time of writing, the only product available is
500 Requests per min
- At the time of writing, the only product available is
- You'll need to create a product subscription under
- Copy
PyTfL.conf.templateto aPyTfL.conffile, and fill in your app's details- TfL's jargon for describing these keys appears to be inconsistent:
- "Primary key" corresponds to
app_id - "Secondary key" to
app_key
- "Primary key" corresponds to
- TfL's jargon for describing these keys appears to be inconsistent:
- Point the app to where this file is located by either:
- Setting the
PYTFL_CONFIGenvironment variable to yourPyTfL.cong's path - Being in the same directory as your
PyTfL.conffile
- Setting the
TfL's tube network.
- TubeLines class
- Basic TubeLines class
- Integrate TubeStations into TubeLines
- Integrate TubeRoutes into TubeLines
- Tidy up the initialisation of these classes in the DAO, Currently takes too long (~30 seconds without caching on TfL's side, ~12 seconds with).
- TubeNetwork class
- Rationalise what this is supposed to mean. May need to move much of the functionality found here into a DAO.
- Create whole network and measure how long this takes. Optimise if necessary.
- TubeStation class
- Basic TubeStation class
- Make use of additionaProperties key - could organised them by the 'category' key.
- Make use of children key. This can be postponed until other transport types (particularly bus) are incorporated.
- Entrances (NaptanMetroEntrance)
- Platforms (NaptanMetroPlatform)
- Concourses (NaptanMetroAccessArea)
- TubeRoute class
- Basic TubeRoute class
- Other
- Enums for
directionandservice_type
- Enums for
- Government documents on understanding NaPTAN