(→‎WP Essentials: - bullet point form.)
(→‎Results: -update on Github repositories.)
Line 30: Line 30:
== Results ==
== Results ==


(TODO)
=== 20/11/2013 - intermediate work on relevant scripts ===
 
This is in progress, but we have designed a workflow from Geometric routes and stops, through to NEM Files (Needed by [[BZE]] for routing using Netview) and also GTFS.
 
Currently work organised via 2 repos on Git:-
* https://github.com/hsenot/nemtools/ (Handles geometric aspects via PostGIS database queries, and NEM files output)
* https://github.com/PatSunter/SimpleGTFSCreator - Creates a GTFS schedule from a set of intermediate route segment files, stops, and specification of timetable frequency.

Revision as of 05:27, 20 November 2013

WP Essentials

This is a Work Package as part of the OSSTIP project.

Inputs:

  • Initial GIS data (OSSTIP/WP1),
  • GIS data infrastructure (OSSTIP/WP3),
  • and an updated GIS network of changed PT service lines and frequencies (could be synthetic, or real data from BZEs project work so far etc).

Outputs:

  • software scripts or packages supporting conversion of data formats,
  • documentation on how to use them.

Estimated Time: Medium

Status:

Requirements Summary

There are two key challenges with utilising software tools that visualise a public transport timetable:

  1. The decision-making involved in generating the actual timetable itself;
  2. 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 TransitDataFeeder.

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

20/11/2013 - intermediate work on relevant scripts

This is in progress, but we have designed a workflow from Geometric routes and stops, through to NEM Files (Needed by BZE for routing using Netview) and also GTFS.

Currently work organised via 2 repos on Git:-

Cookies help us deliver our services. By using our services, you agree to our use of cookies.