This section defines the behavior of the “Map To” button while logged into a Demand/Response workpiece.
Map To Button Enable/Disable
Once the user is logged into a Demand/Response workpiece, a manifest of trips will be sent down through the data connection. The user will select the trip they want to work on by touching the relevant trip. If the trip can be navigated to (i.e. Dispatch has entered a valid GPS location), the “Map To” button will be enabled.
If the trip cannot be mapped (i.e. Dispatch has not entered a valid GPS location), then the “Map To” button will be disabled.
Map To Functionality
Once the Map To button is pressed, the Navigation application will be brought to the foreground. Either navigation will start automatically, or the end location will be marked on the map for the user. This functionality is configured.
Automatic Navigation To Destination
If the system is configured for automatic navigation, then the application will already be in navigation mode. The user can drive the vehicle to the destination, and it will function as a navigation assistance. The result will look something like this.
Mark Destination For User
If the system is not configured for automatic navigation, then the application will simply show the location as a marker whenever the “Map To” button is pressed. The user will then have to manually start navigation to the destination. The result of the “Map To” button will be something like this.
Navigation Application Functionality
The navigation functionality should be familiar to anyone who has used navigation software before, so this section will give you just a general overview of all the functionality.
Here is the screen that the user will see when the navigation is open.
It shows the vehicle on the road, the speed limit information (if available), the road the vehicle is on, the speed, and allow the operator to act. All the actions the user can take are defined in the table below.
|Deactivates the navigation application and returns the user to the MDT screen. After arriving to the destination, press Hide to return to the MDT screen and then press ‘Arrive’ to indicate that you have arrived.
|Bottom Menu Bar
|Deactivates the navigation application and returns the user to the MDT screen.
|Open search screen to allow the user to search for a destination.
|Opens the history of destinations that were found.
|Opens the possible parking that is nearby the vehicle.
|Opens the menu screen. Currently, this only contains the search option.
The search menu will allow the user to simply search for a location that they would like to go to. This works like a typical search with no real advanced functionality. Once the user selects an item from the search, the screen will go to Pre-Navigation.
Once a location is selected, pre-navigation is open.
This will allow the user to navigate to the location. Avail recommends to allows the use of the navigate feature and not the “Set as start point” as the latter can be confusing.
Once navigation is selected, the route preview will be shown.
Finally, the user can click choose the route they want and click the “Navigate” button to start Navigation.
Once navigation begins, the application will show the route the vehicle needs to take, update as the vehicle moves, and provide audible turn-by-turn instructions while the vehicle drives. This will continue until the vehicle reaches its destination. At this point, the navigation will automatically stop.
|Read the next instruction aloud
|Allows the user to change or delete waypoints on the route
|Stops current navigation
|Allows the user to add a waypoint to their current route.
The navigation application will automatically switch between day/night based on the time of day. This is not configurable by Avail and there may be some lag time between the Avail night mode and the navigation night mode. However, as they use the parameters to determine the transition, it will be almost identical.