HSL Navigator - An open basis for next-generation journey planners

Presentation at Nordic Public Transport 2014 in Oslo, Norway

Transcript

1. HSL Navigator An open basis for next-generation journey planners 2014-06-12 Tuukka Hastrup, Systems Designer, Helsinki Region Transport HSL
2. Why a new journey planner? 1) Mobile first – real-time data, on-the-go use cases • Seamless incorporation of real-time data • Navigation instructions during the journey • Routing based on real-time situation 2) No suitable, complete products on the market • Need to drive new development • Need for a lot of customisation and integration work 3) Openness enables new innovations and products! • Concrete results from research projects • Lower the barrier for the new businesses and technologies
3. Background 1. Current HSL Journey Planner 2. Open Data since 2009
4. Current HSL Journey Planner
5. Current HSL Journey Planner • Customers recommend current HSL Journey Planner • 0.1 million users per day, compared to 1.3 million inhabitants, 1 million boardings per day Current Features • Schedules and maps • Journey planning − Walking, cycling, public transport • Real-time schedules • Favourite journeys and stops
6. Current mobile site • Limited version of the main site • Works also on older (pre-iPhone) phones • Lacks journey tracking • Lacks re-routing
7. Use of HSL data Developer accounts 2009-2012 Sep 09 Sep 10 Feb 11 480 30 670 (789) < 5 apps +30 apps Sep 11 Sep 12
8. Apps from the developer community
9. HSL Navigator 1. Status 2. Experiences on openness 3. Concept
10. Status • 100% open • Developed in one person-year • Mobile HTML5 • Covers on-the-go route planning • Does not cover all use cases • Tested in Tampere, Amsterdam, Berlin, Manchester, New York…
16. What does 100% open mean? • Open Data − Data management is HSL's public responsibility − No need to ask for permission to create new services • Open API (Application Programming Interface) − HSL provides route planning as a service for other's services • Open Source − HSL's service can be freely duplicated and adapted − Anyone can learn of our problems and technical solutions • Open collaboration − Another city can test and deploy the same system − Improvements can be shared between cities
17. Open collaboration • Re-use of OpenTripPlanner from Portland, Oregon • Oulu has deployed OpenTripPlanner and the Navigator as part of their new information system: http://oulunliikenne.fi/oulunliikenne2014 • Vedia Oy and iplaner.pl deploying their own versions • University student group project wrapped HSL Navigator into a native Android app
18. Next HSL Journey Planner 1. Principles 2. Concept
19. Principles for next Journey Planner • Learn from the Navigator experiment − HTML5, Open Source • Open collaboration − Work in the open − Joint project with the Finnish Transport Agency − Everyone invited to follow the Journey Planner project • Parallel work − Other cities can test the Navigator − Anyone can build new features
20. Why HTML5? • A single service for web, tablet, mobile browsers, iPhone, Android, Windows Phone etc. • A single HSL user experience • No need to install an app on the phone • HTML5 can work offline • HTML5 can be wrapped into native apps
21. Concept • This would become HSL’s start page www.hsl.fi Strong time hierarchy: urgent tasks quick, others possible • Browser-based like all HSL information services Cost efficient, few person resources, stable maintenance Platform independence, HTML5, fully mobile responsive • If needed, HTML5 can be wrapped into native applications HTML5 features extended with native features Uniform HSL experience independent of platforms and devices • All HSL services also available as APIs HSL provides the general, device-independent service Platform specific and added-value services by third parties
22. Thank you! dev.hsl.fi