Show list of directions

[slinlee]

Show the directions in a list somewhere.

[andrewdanks]

This is a great idea. Maybe this should be in some inspector-like semi-transparent popover window, that can be opened by a button/icon somewhere, so we don't display so much information at once in the UI

[epan]

Have the button "List" under the map open a new window to show directions of the current route.

See wireframe: http://cl.ly/image/3L3p3E0u021L

[dhchow]

Testing images

[dhchow]

Done! No elevation just yet though. That summary data doesn't seem to be readily available.

[epan]

I think Andrew did some code for elevation but I'm not 100% sure it works or where it is.

On Thu, Oct 25, 2012 at 1:08 AM, Diana C notifications@github.com wrote:

Done! No elevation just yet though. That summary data doesn't seem to be readily available.

— Reply to this email directly or view it on GitHubhttps://github.com/andrewdanks/reroute/issues/14#issuecomment-9769168.

[andrewdanks]

It works.

I just added the "ft climb" metric to the route info. However, this won't be shown right away because calculating the total climb requires a service call; so it'll show 0 initially, and show the correct value a few seconds later.

Also, I'm not sure if we want to show min(0, total climb) or allow negatives. For now, I allowed negatives.

[epan]

Does this return the climb - descent or does it sum up all the climbs? Negative is fine.

On Thu, Oct 25, 2012 at 2:05 AM, Andrew Danks notifications@github.comwrote:

It works.

I just added the "ft climb" metric to the route info. However, this won't be shown right away because calculating the total climb requires a service call; so it'll show 0 initially, and show the correct value a few seconds later.

Also, I'm not sure if we want to show min(0, total climb) or allow negatives. For now, I allowed negatives.

— Reply to this email directly or view it on GitHubhttps://github.com/andrewdanks/reroute/issues/14#issuecomment-9770622.

Eric

[andrewdanks]

The service call returns a list of numbers representing the change in elevations for each segment in the route, since we were going to integrate this with the timeline somehow, so I just summed up the deltas, which is the overall change in elevation, right?

Although, if we're just taking the difference in elevation between the start and end points, it'll be more efficient just to calculate just those two.

But, I think it'll be interesting to somehow incorporate the list of elevations in the future, since a rider can choose routes that have a more gradual change in elevation than others.

[dhchow]

Yeah summing up the deltas gives overall change in elevation. Though I wonder what's more useful for this situation, overall change or max change/delta? A steep hill in the middle of the route that brings me back to my original elevation is still a tough ride.

Definitely would be helpful to mark at least the greatest delta point of the route, on the timeline, or on the map (if not all of the data points). I'll look into this later when I'm back home.

On Thu, Oct 25, 2012 at 6:57 PM, Andrew Danks notifications@github.comwrote:

The service call returns a list of numbers representing the change in elevations for each segment in the route, since we were going to integrate this with the timeline somehow, so I just summed up the deltas, which is the overall change in elevation, right?

Although, if we're just taking the difference in elevation between the start and end points, it'll be more efficient just to calculate just those two.

But, I think it'll be interesting to somehow incorporate the list of elevations in the future, since a rider can choose routes that have a more gradual change in elevation than others.

— Reply to this email directly or view it on GitHubhttps://github.com/andrewdanks/reroute/issues/14#issuecomment-9800816.

[slinlee]

grade % is more descriptive than elevation gain, and creating our own scale/rating is even better. I still don't know if 200ft gain is strenuous or not.

On Oct 26, 2012, at 11:45 AM, Diana C notifications@github.com wrote:

Yeah summing up the deltas gives overall change in elevation. Though I wonder what's more useful for this situation, overall change or max change/delta? A steep hill in the middle of the route that brings me back to my original elevation is still a tough ride.

Definitely would be helpful to mark at least the greatest delta point of the route, on the timeline, or on the map (if not all of the data points). I'll look into this later when I'm back home.

On Thu, Oct 25, 2012 at 6:57 PM, Andrew Danks notifications@github.comwrote:

The service call returns a list of numbers representing the change in elevations for each segment in the route, since we were going to integrate this with the timeline somehow, so I just summed up the deltas, which is the overall change in elevation, right?

Although, if we're just taking the difference in elevation between the start and end points, it'll be more efficient just to calculate just those two.

But, I think it'll be interesting to somehow incorporate the list of elevations in the future, since a rider can choose routes that have a more gradual change in elevation than others.

— Reply to this email directly or view it on GitHubhttps://github.com/andrewdanks/reroute/issues/14#issuecomment-9800816.

— Reply to this email directly or view it on GitHub.

[dhchow]

Yeah, having our own scale/rating is a good idea. I (as a non-biker) have no idea what #'s of ft gain really mean.

Created a new issue for this (for later, outside of milestone): https://github.com/andrewdanks/reroute/issues/35

On Fri, Oct 26, 2012 at 11:46 AM, slinlee notifications@github.com wrote:

grade % is more descriptive than elevation gain, and creating our own scale/rating is even better. I still don't know if 200ft gain is strenuous or not.

On Oct 26, 2012, at 11:45 AM, Diana C notifications@github.com wrote:

Yeah summing up the deltas gives overall change in elevation. Though I wonder what's more useful for this situation, overall change or max change/delta? A steep hill in the middle of the route that brings me back to my original elevation is still a tough ride.

Definitely would be helpful to mark at least the greatest delta point of the route, on the timeline, or on the map (if not all of the data points). I'll look into this later when I'm back home.

On Thu, Oct 25, 2012 at 6:57 PM, Andrew Danks notifications@github.comwrote:

The service call returns a list of numbers representing the change in elevations for each segment in the route, since we were going to integrate this with the timeline somehow, so I just summed up the deltas, which is the overall change in elevation, right?

Although, if we're just taking the difference in elevation between the start and end points, it'll be more efficient just to calculate just those two.

But, I think it'll be interesting to somehow incorporate the list of elevations in the future, since a rider can choose routes that have a more gradual change in elevation than others.

— Reply to this email directly or view it on GitHub< https://github.com/andrewdanks/reroute/issues/14#issuecomment-9800816>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/andrewdanks/reroute/issues/14#issuecomment-9823025.

[andrewdanks]

Hmm, this is a really good point. Numbers don't always mean much.

I wonder if the grade should be based on a average of the ∆elevation/∆distance over all the segments in the route?

But then we also have the issue of determining what's "high" and what's "low"

[slinlee]

I'll find a rating scale. I remember reading how each % increase made a pretty big difference in how many people were willing to ride

[andrewdanks]

Wow, if you could find it, that'd be awesome!