3 ms·
You don't seem to handle bridges correctly; mapping from "North Vancouver, BC" to "Burnaby, BC" reports a 65% slope the moment you come off the Second Narrows b
by cperciva 14y ago
You don't seem to handle bridges correctly; mapping from "North Vancouver, BC" to "Burnaby, BC" reports a 65% slope the moment you come off the Second Narrows bridge -- because you're jumping from sea level up to almost 200' above sea level. I realize this is a problem with your geolocation data, but there are probably ways you can clean up that data.
Another example is going from "nanaimo and 12th, vancouver, BC" to "nanaimo and 15th, vancouver, BC": There's a bridge in the middle of that which crosses a 30' deep chasm, but you're showing it as being "very difficult" because you're calculating for someone cycling down the side of the chasm -- which would indeed be nearly impossible!
- thecyborganizer 14y agoI noticed this problem as well. I live in Ithaca, and crossing one of our many gorges generates grades of +/- 150% (as an example, try starting at "Arts Quad, Ithaca, NY" and ending at "Bess Brown Center, Ithaca, NY"). Seems like it would be a little bit tricky to try to systematically identify steep ravines like this in Google's elevation data, but it's certainly an interesting problem.