There's a weird thing going on at 22nd and San Jose in the Mission, where it doesn't seem to understand that you can simply continue down 22nd, but instead takes a hook down San Jose before backtracking. I see some other weird discontinuities like this as I click around.
I have to say that the Claude UI has made many inexplicable decisions here, including (but not limited to) the mysterious color coding, the confusing continuous slider over a discrete set, and the weird positioning of the height labels in the altitude graph.
Checkout https://bikehopper.org for solid elevation, bike infrastructure and transit-aware routing around the Bay Area. Some friends and I built this about 5 years ago and continue to maintain it. We use 1m DTM elevation data for SF and 50m for rural areas. DTM is a must for elevation based routing in SF as there are so many sizable buildings, large trees the other models fail hard.
It's not accurate. I mapped it from my house on Cabrillo St in the outer Richmond to 4th avenue and it says I need to climb 25th avenue then walk Geary instead of correctly telling me to use 23rd avenue that is completely flat.
ah, I think this is related to SF's "Slow Streets" program and a genuine bug in the parser.
Cabrillo is a Slow Street, and the parser read its "destination-only" tag as closed to pedestrians, so the tool couldn't see the street at all (and started you a block over?). fixed and deployed; your trip should now go Cabrillo → 23rd → Geary.
This reminds me of a funny story for my first trip to SF. I left the office at 9 and had time to burn until my flight at 1pm.
I decided to walk to the japanese district and check out some shopping there, it was 15 minutes in google maps. I walk every day at home, 2 miles is like 30 minutes ish for me. For some reason it took me 50 minutes (!), and a WHOLE lotta climbing.
And I had to dodge a bunch of drug addicts yelling at people.
By the time I got to japantown I was drenched in sweat lmao so I had to cool off in the shade but man that SUCKED. Never again.
I have to say that the Claude UI has made many inexplicable decisions here, including (but not limited to) the mysterious color coding, the confusing continuous slider over a discrete set, and the weird positioning of the height labels in the altitude graph.
Edited: which apparently is hosted for free on AWS S3.
Cabrillo is a Slow Street, and the parser read its "destination-only" tag as closed to pedestrians, so the tool couldn't see the street at all (and started you a block over?). fixed and deployed; your trip should now go Cabrillo → 23rd → Geary.
(in honor of my old commute, which I miss)
https://flattensf.com/#t~-122.40850~37.77493~-122.50940~37.7...
Another mechanism might be a kind of user-defined cost-curve, where a gradual climb to 10 might be preferred over a steep climb to 8, etc.
https://github.com/opentripplanner/OpenTripPlanner
https://github.com/opentripplanner/OpenTripPlanner/blob/dev-...
Most of us would take a hill with a protected bike lane over a flat 45mph.
The flattest route is only 0.2 miles longer than the shortest, but goes from 200ft of climbing to 500ft of climbing, 12% max grade to 22% max grade.
Apple maps picks the shortest every fucking time.
I decided to walk to the japanese district and check out some shopping there, it was 15 minutes in google maps. I walk every day at home, 2 miles is like 30 minutes ish for me. For some reason it took me 50 minutes (!), and a WHOLE lotta climbing.
And I had to dodge a bunch of drug addicts yelling at people.
By the time I got to japantown I was drenched in sweat lmao so I had to cool off in the shade but man that SUCKED. Never again.