Skip to content
ojaro edited this page Apr 13, 2013 · 3 revisions

General requirements

  • Deployable in any region (Helsinki first, then Tampere, then e.g. Amsterdam, Manchester)
  • Region-wide routing (maybe inter-region too)
  • Suitable for cyclists and public transport passengers (maybe car navigation too)
  • Accessible from a mobile phone (maybe for vision-impaired people too)
  • Modular architecture
  • @manchester Extandable points of interested system allowing contributions flexible from various stakeholders.
  • @manchester Allow the service providers to create skins for the application in order to service quickly their particular target audience.

Architecture

  • Data sources
  • Routing service
  • HTML5 user interface
  • @manchester POI system and API (possible use the CitySDK)
  • @manchester Application skin creation framework

Information sources

  • Timetables as well as realtime info from the transport authorities
  • OpenStreetMap/OpenCycleMap
  • also address data from cities
  • also POI data from various sources