(→Requirements Summary: - upload from doc ...) |
(→Requirements Summary: - fixed after importning from wrong WP) |
||
Line 11: | Line 11: | ||
== Requirements Summary == | == Requirements Summary == | ||
The goal of this WP is to develop and test the ability of the public transport network analysis tool selected in [[OSSTIP/WP2]] with the data collected in [[OSSTIP/WP1]], and infrastructure in [[OSSTIP/WP3]] – to actually display and analyse Melbourne’s current public transport network. The output format should support understanding network performance, e.g. in the form of [[Travel time maps]]. | |||
This will give a good indication of whether the tool will be practicable for the rest of the project, and give a baseline to work from for integrating the outputs into more advanced work or modelling (e.g. [[BZE]]s transport mode-choice model (REF). This should be demo’d and discussed with the team for feedback. | |||
== Results == | == Results == | ||
(TODO) | (TODO) |
Revision as of 08:14, 25 July 2013
WP Essentials
This is a Work Package as part of the OSSTIP project.
Inputs: Existing GTFS timetable (OSSTIP/WP1), GIS display infrastructure (OSSTIP/WP2), various Open Source tools such as Graphserver and/or OpenTripPlanner.
Outputs: Software repository of prototype tool, installed example on a Virtual Machine server, Generated map-based analytical displays, documentation of how it was set up.
Estimated Time: Small-Medium
Requirements Summary
The goal of this WP is to develop and test the ability of the public transport network analysis tool selected in OSSTIP/WP2 with the data collected in OSSTIP/WP1, and infrastructure in OSSTIP/WP3 – to actually display and analyse Melbourne’s current public transport network. The output format should support understanding network performance, e.g. in the form of Travel time maps.
This will give a good indication of whether the tool will be practicable for the rest of the project, and give a baseline to work from for integrating the outputs into more advanced work or modelling (e.g. BZEs transport mode-choice model (REF). This should be demo’d and discussed with the team for feedback.
Results
(TODO)