Comment by danserfaty
1 day ago
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.
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.
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.
“genuine bug in the parser” -> red flag for slop for those keeping track at home
Also "fixed and deployed; your trip should now go Cabrillo → 23rd → Geary". The snappy sentence at the start and the unicode arrows are both pretty big flags for AI writing.
Obviously it's fine to use AI for projects like these, but copy-pasting the response from a coding agent doesn't quite sit right with me.
No, as someone who writes a cycle routing engine by hand, this stuff is endemic when dealing with the trifecta of complex traffic regulations, inconsistent mapping data, and user preferences.
1 reply →
No need to be a jerk.