mullinscr / naptan

Get and map NaPTAN data quickly and easily.

naptan: a python package

Get, view, and map NaPTAN data.

---

The package's functions return the data from the NaPTAN API as a pandas.DataFrame. This allows the data to be easily filtered, queried and manipulated. Once you have the data, you can export the data as a geoJSON, or view it via an interactive map.

"""
Example code to view all the NaPTAN stops within Leicester and
Leicestershire on a map in the browser.
"""
import naptan

# get data as a dataframe
# 260 is Leicestershire and 269 is Leicester
leics_stops = naptan.get_area_stops(['260', '269'])

# View the stops in the browser on an interactive map.
naptan.view_map(leics_stops)

Installation

The latest release can be installed with:

$ pip install naptan

Documentation

All documentation, tutorials, API reference etc can be found at the package's site: https://mullinscr.github.io/naptan/

License

MIT. See LICENSE.txt.

NaPTAN dataset

National public transport access nodes (NaPTAN) is a national dataset of all public transport 'stops' in England, Scotland and Wales. Bus stops form the vast majority of the dataset; but there is data on tram, metro, tube, rail, ferry and air services too.

Included in the dataset, along with the unique identifiers, is common name, locality, stop type, bearing of onward travel, and status (active, inactive or pending).

More information can be found on the UK government's website:

• NaPTAN guide for data managers
• NPTG and NaPTAN schema guide (2.5) (pdf)

naptan's Issues

Spatial export and view

Users should be able to export the returned stops so that they can be easily viewed in a variety of GIS software / packages (.geojson?). It would also be nice for users to be able to view this export easily (in the browser?) to get a sense of the stops' geographic distribution.

GEOjson indent level

To improve (human) readability of the GEOjson files generated, they should be indented.

Lookup table for ATCO areas should be available

Users of the package should be easily able to get the lookup areas for the ATCO areas and their respective code number -e.g. Leicestershire = '260'.

This should at least be available from the README.md, perhaps even within the package itself.