An archive of overall progress notes of WPs for OSSTIP project at different stages in time.
2013-07-25 (Initial)[edit | edit source]
(as written up after first effort to define these with BZE)
Main OSSTIP tasks[edit | edit source]
- Assessment and development of capacity in the necessary tools and data:
- OSSTIP/WP1 Initial data gathering and familiarisation: Gathering, and familiarisation, with key data requirements and possibilities;
- Evaluation and review of the tools' effectiveness given the project's goals.
- OSSTIP/WP2 - Transit Informatics tools review: Assessment of key existing tools such as OpenTripPlanner given the needs of the project, see Open Source Transport Informatics tools;
- OSSTIP/WP3 - Setup and design of Spatial Data Infrastructure to support project]];
- Testing of tools to display current public transport in Melbourne:
- OSSTIP/WP4 - Display of current Melbourne PT network in chosen tool (In practice, this will be quite closely integrated with previous WPs, especially WP2.
- Then, work out process so that a new network can be visualised:
- OSSTIP/WP5 - Workflow for conversion of GIS data into PT network schedule
BZE WPs[edit | edit source]
Then with each organisation, once we've developed some modifications to Melbourne's PT network (likely in an open source Desktop GIS such as Quantum GIS, will do several custom further WPs based on this common base. So far for BZE these are:
- OSSTIP/WPBZE1 - Phase 1 Display of new BZE Network in OSSTIP
- and to be refined decide, possibly using either the OSSTIP platform as a base for Travel zone based O-D analysis, such as in the Open Source Accessibility Toolkit project - or else supporting integrating results back in from other 3rd party tools being explored by BZE.
- Develop a web-based server to publically communicate the benefits of BZE's new network, based on the OSSTIP platform.
2013-10-23[edit | edit source]
Main OSSTIP tasks[edit | edit source]
| WP | Description | Status |
|---|---|---|
| OSSTIP/WP1 | Initial data gathering and familiarisation: Gathering, and familiarisation, with key data requirements and possibilities | Completed (c.f extensions) |
| OSSTIP/WP2 | Transport Informatics tools review: Assessment of key existing tools such as OpenTripPlanner given the needs of the project, see Open Source Transport Informatics tools | Completed (Bar better archiving of results in a VM etc) |
| OSSTIP/WP3 | Setup and design of Spatial Data Infrastructure to support project | In Progress |
| OSSTIP/WP4 | Display of current Melbourne PT network in chosen tool (In practice, this will be quite closely integrated with previous WPs, especially WP2) | In Progress - Mostly Complete |
| OSSTIP/WP5 | Workflow for conversion of GIS data into PT network schedule (Necessary as part of process so that a new network can be visualised) | In Progress - Early Stages |
Particular WPs with project participants
BZE WPs[edit | edit source]
| WP | Description | Status |
|---|---|---|
| OSSTIP/WPBZE1 | Phase 1 Display of new BZE Network in chosen transport informatics platform. | Early planning done only |
| OSSTIP/WPBZE2 | Evaluation of OSSTIP Tools Batch Trip Routing Capabilities for OD Datasets and to be refined decide, possibly using either the OSSTIP platform as a base for Travel zone based O-D analysis, such as in the Open Source Accessibility Toolkit project - or else supporting integrating results back in from other 3rd party tools being explored by BZE. | *In Progress* |
| OSSTIP/WPBZE3 | Develop a web-based server to publicly communicate the benefits of BZE's new network, based on the OSSTIP platform. | Early planning done only |
2014-02-07[edit | edit source]
Main OSSTIP tasks[edit | edit source]
| WP | Description | Status |
|---|---|---|
| OSSTIP/WP1 | Initial data gathering and familiarisation: Gathering, and familiarisation, with key data requirements and possibilities | Completed (c.f extensions) |
| OSSTIP/WP2 | Transport Informatics tools review: Assessment of key existing tools such as OpenTripPlanner given the needs of the project, see Open Source Transport Informatics tools | Completed (Bar better archiving of results in a VM etc) |
| OSSTIP/WP3 | Setup and design of Spatial Data Infrastructure to support project | Largely complete - need to add step of documenting VMs of system state |
| OSSTIP/WP4 | Display of current Melbourne PT network in chosen tool (In practice, this will be quite closely integrated with previous WPs, especially WP2) | Complete |
| OSSTIP/WP5 | Workflow for conversion of GIS data into PT network schedule (Necessary as part of process so that a new network can be visualised) | Significant progress (working, but need to document and better automate) |
BZE WPs[edit | edit source]
| WP | Description | Status |
|---|---|---|
| OSSTIP/WPBZE1 | Phase 1 Display of new BZE Network in chosen transport informatics platform. | Largely complete |
| OSSTIP/WPBZE2 | Evaluation of OSSTIP Tools Batch Trip Routing Capabilities for OD Datasets and to be refined decide, possibly using either the OSSTIP platform as a base for Travel zone based O-D analysis, such as in the Open Source Accessibility Toolkit project - or else supporting integrating results back in from other 3rd party tools being explored by BZE. | Complete |
| OSSTIP/WPBZE3 | Develop a web-based server to publicly communicate the benefits of BZE's new network, based on the OSSTIP platform. | In progress |
2014-08-20[edit | edit source]
Common Work Packages[edit | edit source]
| WP | Description | Status |
|---|---|---|
| OSSTIP/WP1 | Initial data gathering and familiarisation: Gathering, and familiarisation, with key data requirements and possibilities | Completed (c.f extensions) |
| OSSTIP/WP2 | Transport Informatics tools review: Assessment of key existing tools such as OpenTripPlanner given the needs of the project, see Open Source Transport Informatics tools | Completed (Bar better archiving of results in a VM etc) |
| OSSTIP/WP3 | Setup and design of Spatial Data Infrastructure to support project | Complete (need to add step of documenting VMs of system state) |
| OSSTIP/WP4 | Display of current Melbourne PT network in chosen tool (In practice, this will be quite closely integrated with previous WPs, especially WP2) | Complete |
| OSSTIP/WP5 | Workflow for conversion of GIS data into PT network schedule (Necessary as part of process so that a new network can be visualised) | Complete (do wish to better document and automate) |
| OSSTIP/WP6 | Setting up the capacity to modify and extend existing route lines from GTFS to create a new timetable | In Progress |
BZE Work Packages[edit | edit source]
So far for BZE these are:
| WP | Description | Status |
|---|---|---|
| OSSTIP/WPBZE1 | Phase 1 Display of new BZE Network in chosen transport informatics platform. | Complete |
| OSSTIP/WPBZE2 | Evaluation of OSSTIP Tools Batch Trip Routing Capabilities for OD Datasets and to be refined decide, possibly using either the OSSTIP platform as a base for Travel zone based O-D analysis, such as in the Open Source Accessibility Toolkit project - or else supporting integrating results back in from other 3rd party tools being explored by BZE. | Complete |
| OSSTIP/WPBZE3 | Develop a web-based server to publicly communicate the benefits of BZE's new network, based on the OSSTIP platform. | Complete |
| OSSTIP/WPBZE4 | Convert a refined 2nd version of BZE's network into a GTFS timetable, and display in OSSTIP platform. | Complete |
Possible extensions discussed with BZE:
- Supporting a 'demand-driven local service'. Simplest way to simulate this would be to allow modification of walking speeds to much higher than normal.
