The web app was made by my wife while attending Hackbright Academy in SF. I'm really proud of how much she's progressed in such little time, so wanted to share what she made with everyone.
It also works in Melbourne (just tested my daily ride) for when you get back.
NB: you can change the endpoints graphically. Though it's gotten caught up on an unnecessary roundabout, as if it were a way-point (even retracing the route to include it...).
It's on the FAQ and, without saying the exact price, is discussed on the application. It's an education program, so I don't think a "Pricing" tab would fit as well (it'd feel a bit cheap, like Phoenix College).
I should not have to dig around the FAQ to find out it costs $12k, that's a large sum of money to consider spending before jumping into the class. It should, at the very very least be on the application, if not on the front page.
The price (at least for me) was not a _frequently asked_ question, but rather the _very first_ question I thought of asking.
That's awesome. In theory it should work anywhere where Google has elevation data available. She just made it to scratch her own itch, getting around SF.
Haha, we could really use this sort of custom routing in NJ for finding the route using the fewest roads. If I use Google Maps to go to the local mall, Costco, etc. it ends up using about 16 small side roads, alternating left and right turns every block. Takes forever. Meanwhile, if you know what you are doing you can make it there in 3 roads, one a major highway, which is much faster than any of the side roads Google Maps loves so much. Just getting rid of all the turns helps immensely.
Thanks for this! Cycling is my preferred way to commute, so I expect this to come in handy. I just confirmed that my usual work->home route is in fact the flattest.
The dots used for showing the difficulty can be dragged when altering the route. Other than minor finicky things like that, it seems to be a neat idea. Cool work!
I've been using Marble ( http://marble.kde.org/ ) to show me elevation profiles of routes I bicycle. This site is pretty cool too! (This site works everywhere there's map data, not just SF.)
So cool! I've been waiting for a bunch of bike-apps-in-progress to come to fruition (415bike, I'm looking at you: https://github.com/415bike) but now the wait is made much easier with this!
Yeah I'm the same, I look for the steepest rides, I look at my commute home as part work out. Still, no matter which way I take, I still have to climb ~500ft
The length of the route is affecting the slope of each segment.
For example, Bolinas, CA to Vacaville, CA has steeper segments than the Bolinas, CA to Dixon, CA even though they take the exact same route out of Marin and Sonoma.
The extreme example, Bolinas, CA to Boston, MA never gets above a four percent slope.
That's due to limits of the Google Elevation API, it only allows a certain number of samples to be fetched at a time. The app's only meant for use over short distances, like around a city.
My wife (the creator of this app) happened to showed it to someone from Google Maps today. It was demo day at the school she's attending and they were there.
Awesome! Boy, this graph highlights why my evening commute (SoMa to Noe) is killer in comparison to the morning commute.
PS My wife is in Hackbright as well, it is an exciting time in the program (for other HNers, it's the last week of the current cohort). I heard about FlattestRoute a few weeks back, it looks really great!
If I plot a route from Hyde and Bay to 6th and Mission, it routes me over Nob Hill. If I change it two streets to 4th and Mission, it routes me around the Embarcadero, which is much flatter. Is there a reason it takes the more direct (less flat) route in the first instance?
Having played around, the route given seems to vary slightly as I move an endpoint slightly at either end and then massively recalculate - perhaps it caches certain segments and favours those?
One route indicated the lane cove tunnel in Sydney, a place where I can't run or cycle, I could get squished.
Would be interesting to use long/lat co-ordinates, could be really great for bushwalkers and their specific location.
Combine this with something like zombie-run, have the zombies attack at the bottom of a hill/vice versa, you could have a hit with the hard core running community.
Would be nice to see the alternative routes, not just the flattest, but maybe challenging ones, best rated.
But what you've done in a few weeks is still awesome. Well done.
Pretty interesting, looks like Google Elevation API misses some tunnels though (looking at a route that should go through Broadway tunnel right now). Tunnels are key for getting the Flattest Route™.
I'd been thinking about making something like this for a while (I'm in Seattle). Glad that someone with more time and skills than me got it put together.
What's the basic idea behind the optimization algorithm?
76 comments
[ 2.8 ms ] story [ 135 ms ] threadhttp://www.hackbrightacademy.com/
NB: you can change the endpoints graphically. Though it's gotten caught up on an unnecessary roundabout, as if it were a way-point (even retracing the route to include it...).
I personally think it's fine.
The price (at least for me) was not a _frequently asked_ question, but rather the _very first_ question I thought of asking.
EDIT: Disregard. Found the elevation data:
http://blog.programmableweb.com/2010/03/25/google-launches-m...
http://googlegeodevelopers.blogspot.com/2010/03/aint-no-moun...
For example, Bolinas, CA to Vacaville, CA has steeper segments than the Bolinas, CA to Dixon, CA even though they take the exact same route out of Marin and Sonoma.
The extreme example, Bolinas, CA to Boston, MA never gets above a four percent slope.
http://bdon.org/bicycle.html
PS My wife is in Hackbright as well, it is an exciting time in the program (for other HNers, it's the last week of the current cohort). I heard about FlattestRoute a few weeks back, it looks really great!
Having played around, the route given seems to vary slightly as I move an endpoint slightly at either end and then massively recalculate - perhaps it caches certain segments and favours those?
Just curious really, it's a cool idea!
Love the elevation charts, really well done.
One route indicated the lane cove tunnel in Sydney, a place where I can't run or cycle, I could get squished.
Would be interesting to use long/lat co-ordinates, could be really great for bushwalkers and their specific location.
Combine this with something like zombie-run, have the zombies attack at the bottom of a hill/vice versa, you could have a hit with the hard core running community.
Would be nice to see the alternative routes, not just the flattest, but maybe challenging ones, best rated.
But what you've done in a few weeks is still awesome. Well done.
What's the basic idea behind the optimization algorithm?
http://www.cyclestreets.net