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.
Looking at the repository [1], there are very strong signs for this being LLM generated. The README.md just smells of LLM tells, and Claude Code is being listed as "contributor".
I agree that the tone the parent commenter used wasn't the nicest but unfortunately, factually he is correct.
[1] https://github.com/almostimplemented/flattensf
No need to be a jerk.