mkarpicki/web-navigation-app

Example of web based navigation tool based on HERE API's

web-navigation-app's Issues

Navigation: ask user to confirm if back button pressed and navigation mode on

Wrong routes displayed on results page after coming back from navigation mode

This is due to the fact that stateService was updated while navigation and when going back in history url has different search criteria then state itself.

Possible solution: restore stateService when going back from navigation
or (better approach) when returning state verify if same as url (it has higher priority)

Zoom to proper objects on map each time view changes

Extend form page ('from' wayPoint) to use geoLocation

when geoLocation event delivered position:

• deliver option on UI to use as first wayPoint
  If option selected:
• detect if position changed enough from last one (if exists)
• reverse geocode position to get address
• propose as 'from' wayPoint

Navigation: recalculate route if position on route but going in wrong direction

check traffic incidents when navigation enabled

when traffic events route (time) enough (val set in config) recalculate route and ask user if want to use new one

Navigation: remove visited part of route during navigation

Mark or remove visited way points on map

Move keeping of calculate routes into state service

Currently rourintService does provide keeping results and cleaning them but there is not logic to decide when to use saved instead of searching new ones if search is quite recent.

stateService keeps already stare of app regarding waypoints, areas to avoid etc. It may be good idea to move routes there as well

Zoom to proper objects on map each time view changes

Implement e2e tests for map and objects on map behaviour

[Navigation UI] Implement view for navigation mode

Include info:

• suggestion to follow
• speed
• estimated time to reach destination
• speed limit (?)

[navigation] inform user that destination point reached