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.
replyEdited: 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.
replyCabrillo 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
replyAlso "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.
replyObviously 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.
replyLooking 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".
replyI agree that the tone the parent commenter used wasn't the nicest but unfortunately, factually he is correct.
No need to be a jerk.
reply