Transport Accessibility Analysis with ENIF and Railplan

Transport Accessibility Analysis with ENIF and Railplan Matt Carlson, Arup • Steve Miller, Transport for London

Introduction • Transport for London • The Railplan Model • The Capital Model • Accessibility Analysis with ENIF

Transport for London • Transport for London (TfL) is the integrated body responsible for London's transport system. • Its role is: • to implement the Mayor's Transport Strategy for London • manage the transport services across the capital for which the Mayor has responsibility. • TfL manages: • London's buses, • The Underground, • Docklands Light Railway (DLR) • London Trams.

The Railplan Model • Runs on EMME/2 under UNIX • AM Peak Crowded Transit Assignment model of London (Based on Congtras.mac) • Underground • Rail • Tram • Bus • Docklands Light Rail (DLR) • Uses Size 16 licence • 1500-3000+ Zones • 50000+ Links • Distribution-Mode Split model outside Railplan

PT access 1 (Bus Stop) 3 mins 10 mins 20 mins ED Origin(s) Centroid PT access 2 (LUL Station) ED Destination(s) Centroid 7 mins 6 mins 10 mins PT access 3 (TOC Rail Station) 10 mins 4 mins 5 mins Walk Access Time via OSCAR network (GIS) PT Travel Time via Railplan network (emme/2) Walk Egress Time via OSCAR network (GIS) The Capital Model • CAPITAL = Calculator (for) Public Transport Accessibility in London • Integrates Railplan with GIS • Uses finer level of detail for trip access and egress zones and walk network • Provides detailed calculations of travel time by public transport from a set of origins to a specific destination, such as: • Town centres • Development sites • Hospitals • Supermarkets • Considers all aspects of the journey time including • Access and Egress time • Wait time • In Vehicle time • Uses census output areas to combine socio-economic data such as population to further quantify the level of accessibility – • jobs within 45 minutes journey time of a town centre. • Diagrams taken from “Combining EMME/2 and ArcView GIS: The CAPITAL Model Case Study”, by Richard Hopkins, Transport for London, Nigel Robbins, David James, Brown & Root, London, U.K., 10th European EMME/2 User Group, Thessaloniki, 2001

Can produce very detailed outputs Can link to socio-economic data Runs under Windows only, while master version of Railplan runs under UNIX Long Run Times: 24 hours+ Capital: Strengths and Weaknesses Solution? • Simpler approach: EMME/2 and ENIF only – no linkage to GIS • ENIF will work on any EMME/2 platform

Accessibility Analysis with EMME/2 & ENIF • EMME/2 – Assemble Data • Use “Disaggregate Assignment” (p4-371, EMME/2 Manual) • Analysis of individual trips between origins and destinations using Module 5.35 • ENIF - Display Data • Isochrones in pseudo-grids • Using outputs of Module 5.35 • Inspired by node/link grids (Winnipeg emissions example)

EMME/2 Considerations • Module 5.35 is only partially integrated with other modules • Cannot use @attributes in place of trip file • Cannot store DISA results directly in scenario • Lack of control over DISA outputs • Therefore a workaround is needed…

How it works (1) – EMME/2 Macro • User calls an EMME/2 macro • Whether origin or destination • Which origin or destination • The macro will do the following • Mark Nodes for output to a file • Output Nodes to file • Create Trip File for Module 5.35 • Run Module 5.35 • Import Module 5.35 Results • Main points of macros will be shown in turn

Macro Details (1) - Mark Nodes for Output • Relevant Nodes • Station Entrances (XXYY01-XXYY09) • Selected Bus Nodes (XX9801-XX9999) • Standard 2.42/2.41 Operation: • 2.41 • ~+|1|y|@sta |n|(i.mod.100).lt.10 ||10000,999999||1|2 • ~+|1|y|@bssel|n|(i.mod.10000).ge.9800 ||10000,999999||1|2 • ~+|1|y|@selnd|n|(@sta+@bssel).gt.0 ||10000,999999||1|2 • q

Macro Details (2) – Output Nodes to file • Uses a standard report file • 2.14 • ~+|1|n|@selnd=1||2 • q

Macro Details (3) - Create Trip File for 5.35 • The report file is read • ~@ is used to skip the first few lines of the output file, then read each selected node sequentially • The single origin and all destinations are written to a trip file • A file of the following format is produced: t trips a acnod=309903 egnod= 10101 a acnod=309903 egnod= 10201 a acnod=309903 egnod= 10202 a acnod=309903 egnod= 10203 a acnod=309903 egnod= 10301 Etc…

Macro Details (4) – Run Module 5.35 • Report and Punch • Condensed Report • Does not show itineraries • Allows easier parsing of data • Following data extracted: • inveh • wait • board • auxtr

Macro Details (5) – Store Results in Network • Import to Network from Output file • 2.41 • ~+|3|@inveh|n|@selnd=1||%x%,4|y|2|y • ~+|3|@wait |n|@selnd=1||%x%,5|y|2|y • ~+|3|@board|n|@selnd=1||%x%,6|y|2|y • ~+|3|@auxtr|n|@selnd=1||%x%,7|y|2|y • q • Once node attributes are stored in the network scenario, they can be viewed in ENIF

ENIF Considerations • ENIF Grids can only sum node or link values • They cannot compute min/max/avg • Another workaround - generic elements and generic symbols are used • Node values are aggregated within a generic element grid • Node values are displayed using generic symbols • The size of the symbols are scaled to the zoom level, to give the appearance of a geographical grid

How it works (2) - ENIF Configurable Attributes

Example: Zone 2205 as an Origin

Conclusions • Each set of isochrones takes around 2 minutes to produce • Self-contained process within EMME/2 and ENIF • Useful as a ‘first sieve’ of options before running full Capital runs

Further Developments • More options added: • Modify Weights • Change Default Walk Speeds • Run entirely from ENIF: • Integration of EMME/2 and ENIF hinted at by INRO • Click on a node, automatically run Module 5.35 and display outputs

Steve Miller • Transport for London • 19th Floor, Portland House • Bressenden Place • London • SW1E 5RS • UK • +44 20 8433 6970 • SteveMiller@TfL.gov.uk • http://www.TfL.gov.uk Contact Details Matt Carlson Arup 13 Fitzroy Street London W1T 4BQ UK +44 20 7755 4114 Matt.Carlson@arup.com http://www.arup.com

Transport Accessibility Analysis with ENIF and Railplan