(Updating intro section with req doc contents.)
Line 1: Line 1:
== Intro ==
This is a Work Package as part of the [[OSSTIP]] project.
 
'''Inputs''': Initial sample [[GTFS]] and other data from [[OSSTIP/WP1]], Open source package codes.
'''Outputs''': Short evaluation report on each tool, stating pros and cons, saved example code and datasets in project repository/dropbox.
 
'''Estimated Time''': Small-medium
 
== Requirements Summary ==
 
The goal of this WP is to download and briefly evaluate all of the key candidate software packages identified for potential use as the core basis for the rest of the project and the OSSTIP tool.
 
At the outset, these are expected to be, as per the Appropedia page [[Open Source Transport Informatics tools]]:
* [[OpenTripPlanner]]
* [[Graphserver]]
* [[Mapnificent]]
* [[Mapumental]] (earlier codebase)
 
Primary criteria for evaluation and selection will be:
* The quality and usefulness of visual display capabilities in assessing and communicating transport network coverage and usefulness;
* Accuracy of the results generated – and whether they include walking and cycling connections;
* Speed of the results generated;
* How easy the tool is to use, including data formats used, and preparation requirements, and documentation availability;
* The dependencies it has on other software that needs to be installed first or utilised;
* How challenging it would be to utilise the tool as part of an interactive web-based display of a proposed transport network & schedule (See WP8);
* How well-designed and interoperable the tool is to integrate into a larger transport analysis and modelling system (See BZE later Work Packages);
* Level of community activity and support for the code (e.g. on mailing lists), future plans, and institutional support.


This is a Work Package as part of the [[OSSTIP]] project.
Each package should be downloaded, briefly assessed on some sample data, and the results saved in a project repository (e.g. either Github or Dropbox).


== Tool links ==
== Tool links ==

Revision as of 04:59, 25 July 2013

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

Inputs: Initial sample GTFS and other data from OSSTIP/WP1, Open source package codes. Outputs: Short evaluation report on each tool, stating pros and cons, saved example code and datasets in project repository/dropbox.

Estimated Time: Small-medium

Requirements Summary

The goal of this WP is to download and briefly evaluate all of the key candidate software packages identified for potential use as the core basis for the rest of the project and the OSSTIP tool.

At the outset, these are expected to be, as per the Appropedia page Open Source Transport Informatics tools:

Primary criteria for evaluation and selection will be:

  • The quality and usefulness of visual display capabilities in assessing and communicating transport network coverage and usefulness;
  • Accuracy of the results generated – and whether they include walking and cycling connections;
  • Speed of the results generated;
  • How easy the tool is to use, including data formats used, and preparation requirements, and documentation availability;
  • The dependencies it has on other software that needs to be installed first or utilised;
  • How challenging it would be to utilise the tool as part of an interactive web-based display of a proposed transport network & schedule (See WP8);
  • How well-designed and interoperable the tool is to integrate into a larger transport analysis and modelling system (See BZE later Work Packages);
  • Level of community activity and support for the code (e.g. on mailing lists), future plans, and institutional support.

Each package should be downloaded, briefly assessed on some sample data, and the results saved in a project repository (e.g. either Github or Dropbox).

Tool links

See Open Source Transport Informatics tools for links to surveyed list of main tools. Only some of them will be covered in the table below.

Main tools intended for at least a quick review:

Review Criteria

  • The quality and usefulness of visual display capabilities in assessing and communicating transport network coverage and usefulness;
  • Accuracy and speed of the results generated – and whether they include walking and cycling connections;
  • How easy the tool is to use, including data formats used, and preparation requirements, and documentation availability;
  • The dependencies it has on other software that needs to be installed first or utilised;
  • How challenging it would be to utilise the tool as part of an interactive web-based display of a proposed transport network & schedule (See OSSTIP/BZE-WP8);
  • How well-designed and interoperable the tool is to integrate into a larger transport analysis and modelling system (See WP7 (p14) and WP9 (p15));
  • Level of community activity and support for the code (e.g. on mailing lists), future plans, and institutional support.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.