hsldevcom / digitransit Goto Github PK

User has done route search function and gets search result. One try to interprete and select the best route suggestion. To make a decision user needs information about: travel time, transport modes, transfers, waiting times, fare zones, fares
Related #13

As a user, I want the option to see more detailed information (e.g. accessibility information) in the route search results.

As an administrator, I need a tool for loading new data, making changes to settings etc.

User see additional information in route suggestion to make traveling more convenient. e.g. weather forecast, scenic route...
Related #13

User need information about disruption that one can avoid such lines and routes. Disruption information is needed when planning a trip beforehand and during the trip.

When a user start typing address, poi, etc name, auto complete feature helps to avoid errors and find correct addresss if user does not know exact string or knows only fraction of it
Relates to #6 #7

Helsinki area search currently shows street names only once, not per every city where a same name occurs. The nation wide search instead gives a huge list (>1MB json).

It's possible to fix this in client, but server side filtering would lessen data traffic, which is crucial on mobile connections.

Somewhat blocked by VRK address data (if done server side), which has exact coordinates for each street number, instead of interpolating from rough area information.

User want to define viapoint for routing becouse according one's knowledge or opinion, most suitable route goes via sertain point.
Relates #12

API output methods for UI functions. Same API methods will serve 3rd party applications.

• Route, POI, data updating if there is a bug in existing data
• support to data loading to service
• exceptional capacity requirement in special situation (strike, snowstorm etc.)
• logs
• bug reporting

As a user, I want to use the service with any device that I have, and the service should adapt to the limitations and possibilities of the device.

Municipalities will provide data in ETRSGK25 format. Developers like WGS84. Used coordinatesystem need to be selected for internal and external functions.

Production environment definition
Procurement
Publishing process

Have to manage real-time data from HSL and other metropolitan areas. (SIRI)

• data update processes
• service breakdown management
• backups

• Decide how may servers we need
• Order servers
• Get shell access

• capacity management and monitoring
• possible user account management
  ...

Environment where development results can be tested and displayed to stakeholders
TBD:

• Service provider
• Needed setup
• deployment process

• Decide how builds will be orchestrated
• Decide where we keep deployment code
• Decide how software components are packaged
• Create additional issues about packaging and script for correct projects

Language support for multiple languages. (finnish, swedish, english, russian, sami?)

User wants to plan a journey in advance and specifies start and end points in order to get route suggestions. User can input points in several ways: address, POI, service (e. g. Library), stop id number (HSL short, HSL long, national), device's GPS location, point on a map. User can define a time&date when they need to latest arrive to destination or when they can earliest depart from origin.
Relates to epic #6

User has done route search function and gets search result one try to interprete and select the best route suggestion. To make a decision user needs information about: travel time, leg times, lines, transport modes, transfers, waiting times, fare zones, fares, stop names, stop locations, how to navigate to the stop, accessibility.
Linked to epic #6

For example list feeds at https://code.google.com/p/googletransitdatafeed/wiki/PublicFeeds and http://www.gtfs-data-exchange.com/agencies#filter_official

We need 2 different versions:

• one input field
• two input fields

Next departures list from each stop.
When standing on a stop user wants to know when user's regular bus is coming or in an unknown environment user want to know where one can go from this stop. User can pick up that stop in a service (text search/map) and see a list of approacing vehicles(lines) with arrival times and information where they are going.

• Show all lines in real time on a map

https://github.com/conveyal/gtfs-data-manager

Route search from address to address.

• Can use real time data.
• Multimodality

• Slider for walking distance and change marginal
• Prefer some routes
• Prevent some routes
• Transport mode redesign considering kiss and ride, public + walking/bicycling/driving

Set up browser UI test workspace

• Diagrams contain sources for route data
• Diagrams contain some measure for data quality
• We have identified sources for route duplicates
• What enhancements and transformations we need for data?
• What is the policy of notifying 3rd parties about broken data?
  • E.g. negative driving times
• What do we expect of data? Who takes care that it is good enough?
• Are there some other sources of data? E.g. HSL has some datasources?
• What datasources are included into "first summer version"
  • E.g. Do we include long distance busses?
• Should there be a public disclaimer list "Data for these operators is not that good"

As a user, I want to get information that's relevant to my current situation with as few clicks as possible. More distant use cases may be further away in the UI.

Responsive mobile layout and basic user interface for following components:

• Multimodal route search
• Nearest stops
• Disruption info
• Route map

As a user, I want to enter any search query to refine the context: current location, time of departure/arrival, starting/end point, type of service, bus line, combination of bus lines etc.

Once user has selected suitable route from search result. User need information how to find starting stop, what line to use, when it comes, when to get off, how to transfer, where is nex stop, how to find destination address...
#13

Min.level SLA 99,7% System achitecture has to support high level availability.

User gets real time instructions during the trip so that one can be sure about successfull arrival.

• User can follow how journey progress
• Disruption information
• Re-routing if original plan will fail
• Navigation help on the way to a stop and transferring

• User feedback integration to existing feedback channels
• structured feedback format
• transparency, linking to development process
• feedback handling resposibilities

Would be nice if searching for addresses or places would also immediately give transit options from current location. At least Google is opening an API "soon".

Landing page is the first page of the service.

• User can open it with mobile or desktop device and get suitable layout in both cases (responsiveness)
• Landing page builds confidence by showing quick overview of traffic situation (disruption info)
• User can dig into a detailed info in a case when disruption concerns users regular line
• Page features are served to user in a way which is relevant to current user's context (based on: location, intention, level of engagement(registered or not), behavior history..)
  • next departures
  • route search
  • map functions
  • what else?
• User have an access to other features of the site (navigation)

Business requirement: HSL brand, logo, colors and other style requirements https://www.hsl.fi/tyyliopas

Related to epic #26

Methods to transfer data from existing public transport databases (JORE, Matka.fi koontitietokanta)

• Decide hosting provider
• Contract

Validation process for imported data. Automatic alerts...

Let's gather our specs for Geocoding and do some digging for possible solutions for it. At least these should be done

• Go through office post-its and check what is required from Geocoding
• Find out which datasources provide us required information. Decide all used datasources.
  • check "Open addresses"
• Check out options for geocoding. Some interesting links:
  • https://mapzen.com/pelias
  • https://github.com/rekola/okffi-geocoder
  • Nominatim?
  • What else?
• Design Geocoding API. Selected solution might force us to some format
• Create Geocoding project and create new issues there

• Make map "suiro" immediately visible

Regular public transfer user needs a next collections of next departures lists, where one can add most used stops and lines. Collections helps users in their daily routine trips.
Related to #28

tbd
#13

User is not satisfied with the default route search results and wants to adjust search parametres to find a more suitable route: walking distance, less transfers, success factor (of transfers), transfer margin, allowed fare zones, transport mode etc.
User may have a valid ticket to only one PT operator in a certain area and one want to limit search within one ticket zone. There may be overlapping ticket zones in same geographic area.
Relates to epic #6