About Mapumental

Who built this, and how does it work?

Who we are

Mapumental is a project from the social enterprise mySociety.

mySociety builds simple but effective online tools that empower people in the civic and democratic parts of their lives. You may know us best for our sites such as FixMyStreet, WhatDoTheyKnow and TheyWorkForYou - if you would like to know more, see the mySociety website.

Mapumental’s development was funded through an investment loan from Channel 4 and Screen West Midlands. All revenues from Mapumental go to support our charitable projects in the UK and beyond.

How Mapumental works

Mapumental combines Ordnance Survey postcode data with public transport timetables, and displays the results using Leaflet on OpenStreetMap.

The timetable dataset is compiled with information from many sources, including local public transport information from each of the Traveline regions (known as the Traveline National Data Set, or TNDS), coach services from the national coach services database (NCSD) and rail information from the Association of Train Operating Companies (ATOC).

The transport timetables used in Mapumental are updated on a regular basis. Currently the data is from October 2011, but with the upcoming release of our API we will be using data from January 2014 and then updating every three months.

Mapumental journey times assume you can walk at approximately three miles per hour as the crow flies. It allows for ten minutes’ walking between stations and to/from your final destination. 30 minutes’ walking is allowed at the other end of the journey. It assumes that one minute is enough time for changing buses at the same stop, and that five minutes is enough time for changing train, coach, underground and ferry at the same station.

As Mapumental uses timetabled journeys, it is possible that a given journey time might seem longer than you may think, but this is due to it taking timetables into account.

If you are interested in the technicalities behind Mapumental, you should read these blog posts and case studies: