Add a feedback tool to SMK.

Questions:

• Where should feedback be sent to?
• What information should be gathered from user?
  • Real name?
  • email address?
  • IP address?

The printable directions needs to include reports/alerts specific to segments on the route. Itinerary text should be blue for directions on a truck route, and red, for segments not on a truck route.

Drag and drop of point on the map?

Rationale: can help with large sites that have multiple access points (user can adjust it as needed).

Example: Krause Berry Farms delivery access point versus visitor access point

@qqnluaq Effort to implement?

Ferry crossings should be dotted red line.

After entering an address or clicking a to establish waypoints and a route can a user drag a route (similar to Google Maps)?

Note: Drag the waypoint is higher priority than drag the route.

@mraross suggested that instead of resolving clicks on the map to addresses, we should resolve then to coordinates because when users drop a point on the map it'sbecause they want to reach that specific point, not the nearest address. See an example of this in https://office.refractions.net/~chodgson/gc/ols-demo/?rt=rri though this app has 2 clicks probably not necessary for truckers but good for QA purposes in the LSIA app.

Related ticket: #40

TL legal suggestion - the Province should probably be added as a named entity in the disclaimer.

2020-01-09 CVRP Disclaimer Text.docx

submitted by @al-tabb

It may be helpful to have the legend and route planner 'widget' be independent from the other (Basemaps, feedback) functions of the app. I think they are the primary tools that the user will be interacting with so they should be open by default and should not be minimized/hidden while interacting with the other tools. Perhaps the legend could be on the other side of the screen and the Route Planner widget could be above the Basemaps/Feedback tools?

Correction

Please display the MV Regional Boundary by default

<<>>

Please add the regional boundary for Metro Vancouver.

CVRP BETA Screenshot:

In the TransLink app, the truck route multiplier is set at such a level that causes unnecessarily long routes. Al at TransLink suggests that it be changed to a value just greater than 13 so try 15.

Option: Don't provide a default location
-->Good for dispatch and truckers

Option: Give users a choice to use their location; see maps.google.ca on a phone for an example (small crosshairs bull's eye icon on the map)
-->Good for truckers

Please update the text for the various message types. EXCEL file includes the original TL BETA text and proposed revisions.
2020-01-21 RestrictionAdvisoryApplicationMessages.xlsx

If you generate a route, then access the base maps to toggle, the route is erased. Not a huge issue since routing is so fast, but might annoy some

https://cvrp.translink.ca/contacts

Yes this is needed as a general link and as part of the "you need a permit" process.

Depending on the level of effort, it would be helpful if the app could generate and display at least one alternate route (ideally two). This would apply to a "Proposed Route" (blue) and "Unverified Route" (dotted red line).

The rationale for this feature is to clearly communicate to the user that the app is generating proposed or unverified routes (as applicable) with the explicit expectation that the carrier and/or driver will choose a preferred route (at their sole discretion), and that they are responsible for verifying all clearances and restrictions on the route of their choice.

Example - Google Maps (and other Apps) provide up to 3 options:

Note: The TL BETA does not generate multiple route options.

TRP requires an About page, same as the CVRP Beta on AGO.

Data provision is anticipated on January 24th.

@al-tabb to send us screen shots of desired symbolization (desired colour/symbol); as well it would be good to confirm the display name, where it should be placed in the layer list, draw order concerns.

Minor detail - it may not be self-evident based on the symbol alone that "route options" also gives the user the ability to edit vehicle attributes.

Consider following text on mouse-over: "Route & Vehicle Options"

The CVRP Beta Application (ArcGIS Online) allowed for 2 location inputs.

The route planner web service can handle more than 2 easily, and that is the current implementation in TRP, but if we do leave it as more than 2 then we may have some user interface issues to attend to: the graphics for anything between start and finish points need work and on mobile there is not a lot of real estate to accommodate a long list of locations.

Please add the definitions copied below, as follows.

1. Please include a legend entry with a name for each route type (“Potential Route” and “Unverified Route” – as currently provided in the TL BETA, noting the change to “Potential Route” instead of “Proposed Route”).

2. When a route is generated, please Include the two definitions in the report/notice and the printed route itinerary (either at the top or bottom of the printout).

3. It should also be relatively straight forward to create a static glossary page where we can include term definitions like these.

Generated Route Type Definitions, as reviewed and revised by TL Legal:

Change “Proposed Route” to “Potential Route”

Potential Route (Blue Line) – A route that based on factors such as the origin and destination, intermediate waypoints, and the default or user-entered vehicle parameters, may comply with municipal truck route bylaws. This route is put forward for the driver and/or carrier’s consideration for pre-trip planning purposes without warranty of any kind, whether express or implied. The driver and/or carrier is responsible for ensuring the default vehicle parameters or user-entered vehicle parameters are an accurate representation of the actual vehicle, for verifying all clearances and restrictions on the route, and for ensuring the vehicle is operated in compliance with all applicable municipal bylaws and provincial and federal regulations.

Unverified Route (Dotted Red Line) – A route, or a portion of a route, that may not comply with municipal truck route bylaws and may not be suitable for a vehicle with the default or user-entered vehicle parameters. The driver and/or carrier is responsible for ensuring the default vehicle parameters or user-entered vehicle parameters are an accurate representation of the actual vehicle, for verifying all clearances and restrictions on the route, and for ensuring the vehicle is operated in compliance with all applicable municipal bylaws and provincial and federal regulations.

Related tickets: #15, #21

What would be the level of effort to allow a user to edit way points, including the starting point? Preference would be to give the user the ability to edit way points by dragging and dropping or by address search.

Create a list of all reference layers in the TransLink pre-route planning app, determine their source, linage, update frequency and any missing layers (e.g. dangerous groups) to help inform a plan to look for gaps or tasks relating to their availability in the app and if they meet performance expectations. Hosting location for the final app will also need to be considered.

Data provision is anticipated on January 24th.

@al-tabb to send us screen shots of desired symbolization (desired colour/symbol); as well it would be good to confirm the display name, where it should be placed in the layer list, draw order concerns.

iPhone 8 (iOS 13.3) printable route document has paging issue. Page 1 content spills into page 2, page 3 into page 4, page 5, into page 6, etc. A 5 page document on desktop becomes 11 pages on iPhone.

Please consider changing the label for the "Route" button to "Get Route Details", “Get Directions”, or something similar. It is not immediately obvious that the user should click on "Route" to review/print turn-by-turn directions.

Assuming this is where reports/notices will reside, "Get Route Details" rather than "Get Directions" would be more appropriate.

Beta ver: 0.0.2 built: 2019-12-20

The Disclaimer text is not totally readable in Firefox or Chrome on Windows 10. No ability to scroll down to see it all.

Add a feedback form to the CVRP Beta

Version: 0.8.1
Last commit: 2019-12-18 14:33:42 -0800

When viewed in Safari on iOS 13.3 (iPhone 8) and iOS 9.3.5 (ipad mini), there appears to be a disabled text box beneath the "I accept" button.

Also, if you tap the "I accept..." button, the disclaimer panel does not disappear as when viewed in desktop mode. Rather it takes user to the top of the Disclaimer form.

submitted by @al-tabb

Is it possible to use the classic popup style box above the clicked on feature when identifying features? This would probably only work well in a desktop environment.

submitted by @al-tabb

"Designated Municipal Truck Route with Restrictions" (light green) is currently labelled as "Designated Truck Route". This item should also be included in the "Truck Routes" legend item above it. This would eliminate the need to have a "Truck Routes" grouping.

Remove the "Truck Advisories and Restrictions" grouping and have "Restrictions & Warnings" and "Temporary Road Closures" outside of any grouping. Rename "Restrictions & Warnings" heading to "Truck Advisories and Restrictions".

In the routing Options interface there are form elements that allow a user to press arrows in order to generate a number (Height OAH, Width OAW, Length OAL and Weight GVW).

The form inputs allow for negative numbers to be input; consensus is that users should not be able to enter negative numbers.

Data provision is anticipated on January 24th.

@al-tabb to send us screen shots of desired symbolization (desired colour/symbol); as well it would be good to confirm the display name, where it should be placed in the layer list, draw order concerns.

integrate changes to directions service into SMK

The original beta app built by Translink had a list of vehicle types. We need to expand the truck types and reflect the provided graphics as appropriate.

Text on the Disclaimer accept button is truncated vertically

Inventory the AGO Beta for the metadata links (Item description pages) as applicable. The details in there will form the basis of the new metadata record stubs in the BCDC.

The directions tool should be able to generate a document with the current route, suitable for printing.

This document should include:

• the waypoints
• a list of the directions for the route through the waypoints
• a map showing the route

Ideally on one page.

Put together an inventory of the data consumed in the map and check the data sources

Would it be possible to limit the disclaimer width when a user maximizes the size of the window on a desktop (wide screen)?

Current:

Proposed - set max width so that the following text does not break across multiple lines:
"This website is intended to be used as a pre-trip planner. Do not operate a vehicle while using this website."

The directions tool should be able to generate a document with the current route, suitable for printing.

This document should include:

• the waypoints
• a list of the directions for the route through the waypoints
• a map showing the route

Ideally on one page.

It would be great if the legend contained an entry for the generated route which indicates the difference between the proposed portion of the route and the unverified portion of the route.

CVRP BETA Screenshot:

I noticed that in some cases the generated route (i.e., part of the route) is not colour coded correctly. Not sure if this has already been flagged elsewhere. Noting it just in case.

See example.

Please change the App's name from Commercial Vehicle Route Planner (CVRP) to Truck Route Planner (TRP).

Aligns with MoTI preferences, and should reduce confusion for end users by clearly identifying the TL App as separate/distinct from the DriveBC Height Clearance Tool, which was at one point called the CVRP.

Thank you in advance.