OSSTIP/WP4: Difference between revisions

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)

@@ Line 11: / Line 11: @@
 == Requirements Summary ==
-There are two key challenges with utilising software tools that visualise a public transport timetable:
+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]].
-# The decision-making involved in generating the actual timetable itself;
-# The capacity to save the timetable in [[GTFS]] format.
-The goal in this work package is produce software scripts and/or tools to support this process to be as efficient as possible. This may involve either writing new scripts, or leveraging existing open source applications, such as [http://code.google.com/p/transitdatafeeder TransitDataFeeder].
+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.
-The envisaged starting point is a set of transport routes saved in a common GIS format, such as ESRI Shapefiles, as developed in [[OSSTIP/WP1]]. These would be accompanied by a “desired frequency” and “average speed” of each route – probably to be recorded as part of the GIS database.
-From this expected starting point, the scripts tools in this WP are envisaged to (a) create a set of “first cut” GTFS timetable files based on the above inputs; and (b) provide some kind of support/process for identifying where the generated timetable most needs to be further edited manually. This process should also be documented, so it can be reproduced as efficiently as possible throughout later stages of the project.
 == Results ==
 (TODO)