The usable point
Roadscape puts the city's own 49.4% southbound AM-peak delay-reduction claim in the right category: cited city evidence. It then separates that from what is still missing: actual ADT, turning counts, queue observations, bike/ped counts, emergency-route status, and before/after corridor safety proof.
Estimated lane count, posted speed, operating speed, ADT, curb-to-curb width, and truck/bus share stay labeled as assumptions until field measurement or agency data confirms them.
That separation matters. A public argument gets stronger when it does not pretend an estimate is a measured fact.
How this packet labels claims
Real / cited
Location, protected-intersection history, right-turn lane removal/restoration, the city's stated delay reason, crash-history context, bikeway project context, and growth signals when tied to public records.
Estimated
Representative lane count, posted speed, operating speed, ADT, curb-to-curb width, and truck/bus share until measured or confirmed by agency data.
Needs field measurement
Turning movements, pedestrian and bike counts, blocked-turn events, queue observations, emergency-route status, and current before/after safety performance.
Roadscape can screen and organize evidence. Official redesign, pavement, or safety decisions require local standards, agency records, and licensed Professional Engineer review.
Snippet used in the Fremont study
Roadscape screening note: Fremont's documented Mowry fix is real city evidence of a delay problem, but the corridor still needs measured ADT, turn counts, bike/ped counts, queue observations, and before/after crash proof before any official conclusion.
- Public product context: Roadscape street intelligence
- Resident data brief: Re-Evaluate Fremont's Bike Lanes