Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map information updates #265

Open
1 of 7 tasks
sasjkia opened this issue Apr 28, 2017 · 2 comments
Open
1 of 7 tasks

Map information updates #265

sasjkia opened this issue Apr 28, 2017 · 2 comments

Comments

@sasjkia
Copy link
Collaborator

sasjkia commented Apr 28, 2017

  • Adjust size width so it takes up the entire width of the page (i.e., 2 columns). Shift everything else down directly.

Modify the information displayed on the map to include:

  • Different icons for power chair user riders and drivers with power chair adapted vehicles

  • Dates and times available, when you click on any icon

  • Also optimize the size of the information displayed, so it's accessible to cell phone users and people with vision difficulties

Change the conditions under which icons are removed from the map. Currently, drivers are removed after confirming their first match, which skews downward the availability of drivers. Change this so that:

  • Driver icons remain on the map until the drivers have cancelled the entire drive offer
  • Rider icons remain on the map until the riders have been matched or cancel the ride request. If a match is cancelled, the rider should be returned to the map.

Currently, the map also zooms in too much when entering a zip code. This means that riders in an existing zip code are missed when entering location details into the map.

  • Is there a way to update how the map zooms in, to give a broader view of potentially relevant rides? E.g., include a 5-mile buffer for location entered.
@dmilet
Copy link
Contributor

dmilet commented Apr 30, 2017

@langdonms There are two views currently available vw_unmatched_drivers_details and vw_unmatched_riders_details. Do you think you can work with that? @jkbits1 will have to expose them through the node app if not already done

@jkbits1
Copy link
Collaborator

jkbits1 commented Sep 19, 2018

Less immediate need for this now the system focuses more on supporting operators but changes can still be helpful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants