yesterday at 11:58 PM
Sorry if this is a stupid question, but isn’t the climb independent of the route?
yesterday at 11:59 PM
Not if there are hills in between. But the delta between A and B is the best you can do, yes.
yesterday at 11:36 PM
It would be neat if it there were an option which added distance and elevation gain, but minimized the grade.
For example, a route from SOMA to Nob Hill can be made flatter by approaching from either the east or west. Technically the "flattest" as measured by elevation gain between the two is straight up Taylor from Market, but it's much nicer to bike to the top of Nob Hill by going out of the way (e.g. Polk → California, Embarcadero → Broadway, etc.)
today at 12:08 AM
I suspect that this would result in absurdly long routes. Imagine trying to go up a mountain while minimizing grade... you'd end up zig-zagging back and forth endlessly.
yesterday at 11:15 PM
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.
yesterday at 11:44 PM
Can you please consider expanding it to include Seattle? Or better yet Puget Sound area? 1m DTM elevation data is available here. We have many amazing bike trails, but also plenty of hills that must be avoided.
yesterday at 11:56 PM
We’d like too! It’s an open source project that was never designed to scale beyond one regions (bay area, puget sound, NYC, etc…) our hope has always been been that folks in different regions would spin up their own copy. By keeping it regional the data and hardware requirements for running it are minimal. That said, we are working on a new routing engine that we hope can scale to support continent wide routing. Then we can manage running it for many metro’s. If you’re interested in self hosting for Seattle we are happy to help get it set up.
today at 12:02 AM
What are the system requirements for hosting it? I'm not sure I have the discretionary funds to host it for the general public - but it all depends on how heavy this is :)
today at 12:11 AM
We run it on a single coolify box from someone’s house. 6 core, 32GB ddr4 memory box. The actual routing query are compute intensive but only momentarily. More cores and memory means higher concurrency but we’ve never had an issue with load in the Bay Area with a few hundred users a week. We used to run it on a k8s cluster but we cut it down to save on power and infrastructure management overhead.
yesterday at 11:15 PM
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.
yesterday at 11:54 PM
You should consider adding drive as well, some of us have manual transmissions still, although the Bike mode returns pretty reasonable results.
yesterday at 10:19 PM
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.
yesterday at 10:49 PM
I think this comes down to the DEM they are using. I think it would have come out better if they had used USGS 3DEP DTM at 25cm.
Edited: which apparently is hosted for free on AWS S3.
yesterday at 10:56 PM
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.
yesterday at 11:45 PM
“genuine bug in the parser” -> red flag for slop for those keeping track at home
yesterday at 11:53 PM
No need to be a jerk.
yesterday at 10:10 PM
The wiggle!
(in honor of my old commute, which I miss)
https://flattensf.com/#t~-122.40850~37.77493~-122.50940~37.7...
yesterday at 11:34 PM
This is great. Since SF is mostly a grid, I used to use the heuristic of only choosing paths that wouldn't take me further from my destination, avoiding going downhill but choosing the shallower uphill climb if a choice is given.
Other than knowing the direction of my destination, it only used local information
yesterday at 11:13 PM
someone should make flattendallas.com as a joke
yesterday at 10:13 PM
Absolutely love the live profile updating when you swipe from flatter to shorter.
yesterday at 10:15 PM
> The slider runs along the whole trade-off between distance and climbing [...] Climbing is cumulative gain
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.
yesterday at 10:31 PM
You want OpenTripPlanner. Their triangle lets the user trade distance, climbing, and safe facilities.
https://github.com/opentripplanner/OpenTripPlanner
https://github.com/opentripplanner/OpenTripPlanner/blob/dev-...
yesterday at 10:28 PM
Doesn't Google Maps in bicycle mode already do this?
yesterday at 10:57 PM
There are many constraints to satisfy, and avoiding hills is but one of them.
Most of us would take a hill with a protected bike lane over a flat 45mph.
yesterday at 10:10 PM
Cool! Any way to toggle on street names on the map?
yesterday at 10:50 PM
Try downtown to somewhere in Bernal, say Progressive Grounds coffee house.
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.
yesterday at 11:17 PM