Read Between the Lanes

Traffic & air quality: how to read the traffic report and spot the assumptions that drive conclusions

Traffic reports don’t arrive as lies or truths. They arrive as stories—stories told in numbers, charts, and carefully defined “conditions.” And like any story, the ending depends on what the author decides to treat as normal, likely, reasonable, “conservative,” or not worth counting.

That matters here, because the River Walk Specific Plan isn’t a minor tweak at the edge of town. The project description in the public notice frames a mixed-use development of roughly 2,432–2,682 residential units plus 375,000–875,000 square feet of mixed-use commercial/office/service/retail, tied to a larger Sphere of Influence expansion of about 1,522 acres.

And the Draft EIR notice is unusually direct about one key point: Transportation and Circulation are identified as significant and unavoidable, and Cumulative Air Quality is also flagged as significant and unavoidable.

So the question isn’t, “Is traffic studied?” It is. The question is: when you read a traffic report, how do you tell whether its conclusions are sturdy—or built on assumptions that quietly steer you toward a predetermined shrug?

Let’s treat the traffic report the way you’d treat a witness statement: respectfully, carefully, and with a sharp eye for what’s assumed.

---

1) Start with the simplest question: “What problem is this report actually solving?”

Traveled (VMT) under SB 743, while still evaluating safety (often via queueing on state highways) and multi-modal impacts (pedestrians, bicycles, transit).

That’s important because it means the report may say, in effect:

• “Congestion is not a CEQA impact,” but
• “VMT and safety are.”

If you don’t catch that early, you can end up arguing a point the document is structured to ignore—or missing the point it’s structured to defend.

---

2) Check the baseline: “What counts as ‘existing conditions’?”

This is where many reports quietly become time capsules.

River Walk’s traffic operations analysis uses traffic volumes collected in early 2020, specifically noting they were collected before COVID-19 affected traffic volumes.

That single sentence should trigger follow-up questions in your mind:

• Do early-2020 counts reflect today’s lived reality on Patterson, McHenry, Coffee, Claribel, Oakdale, and the Crossroads area?
• If conditions have changed (new retail, new housing, new commuting patterns), how does the report bridge the gap between then and now?

A baseline is not just “data.” It’s the foundation for every “increase,” every “mitigation,” every “less-than-significant.” If the foundation is dated or unrepresentative, the entire structure leans.

---

3) Find the first big hinge: trip generation (how many trips the project “creates”)

Here’s the citizen-reader move: don’t only read the final “net” number. Read the discounts.

The pass-by assumption (the “they were driving by anyway” discount)

Retail “pass-by” means: some customers would already be on the road, so the project isn’t adding their full trip to the network.

That can be legitimate when applied carefully. But it can also be used like perfume: it makes the math smell nicer while the underlying burden remains.

In River Walk’s report, the pass-by percentages vary by retail area—28%, 33%, 15%, even 50% for one component.

Here’s what to ask:

• Are those pass-by rates realistic for this location and this mix of uses?
• Even if a trip is “pass-by,” does it still add turning movements, queueing, and delay at the same intersections neighbors already struggle with?
• Is pass-by being used to reduce impacts where the project is most vulnerable?

Pass-by trips are not free trips. They are still emissions, noise, and intersection friction where it matters most: at access points and chokepoints.

---

4) Spot the “we don’t know, so we assumed…” sections

These are the quiet drivers of the conclusion.

NEVs (Neighborhood Electric Vehicles): the “could reduce car trips” promise that isn’t counted

The report notes that the Specific Plan includes a Neighborhood Electric Vehicle (NEV) system and describes the River Walk Trail network as potentially including paved paths, NEV lanes, and natural trails.

But then it drops a key caveat: ITE trip-generation data doesn’t address NEVs, so NEV travel is “unknown,” and the analysis assumes all trips are made by automobile to be “conservative.”

That assumption cuts both ways:

• It can inflate traffic impacts (if NEVs truly replace car trips).
• But it can also sanitize the project narrative by letting the plan market a “multi-modal lifestyle” without requiring the analysis to prove it will actually reduce driving at a meaningful scale.

So the question becomes: Is the NEV/trail system a real transportation strategy—or an aesthetic feature treated like mitigation in public-facing language but not enforceable in the math?

---

5) Watch how the report decides where trips go (distribution and assignment)

Then it provides a distribution table that assigns substantial shares south and west, with only about 10% of new residential trips staying on-site.

Two things to notice:

1. Internal capture is small.
   If only ~10% stays internal, most daily life still spills outward onto the same corridors everyone already uses.
2. The report admits a limitation that should make you pause:
   Its method “does not reflect customer choices based on the quality of alternative retail destinations.”

Translation: the model distributes trips based on gravity/model structure—not on human preferences like, “People will still drive to the bigger/better cluster,” or “They’ll keep shopping where they already have routines.”

That’s not a gotcha. It’s just reality: distribution is an assumption wearing a spreadsheet costume. Your job is to notice where it might be fragile.

---

6) Make friends with VMT (because that’s where CEQA now sharpens the knife)

VMT is not “traffic congestion.” VMT is driving burden—how many miles vehicles travel because the project exists.

In the River Walk traffic report, the VMT analysis compares conditions with and without the project and shows a regional VMT increase (Table 16).
It then states something that is both blunt and consequential:

• Because Riverbank and Stanislaus County haven’t adopted VMT significance criteria, the analysis applies OPR guidance and concludes it must presume the residential VMT impact is significant, and it finds the non-residential uses also cause a significant VMT increase.

This is where readers often miss the deeper point: a “significant” conclusion doesn’t automatically stop a project. Under CEQA, a lead agency can certify an EIR with significant impacts if it adopts feasible mitigation (where possible) and makes findings/overriding considerations.

So your next question is not just “Is it significant?” but:

• What mitigation is proposed?
• Is it enforceable, funded, and timed to occur before the impact?
• Does it reduce the impact meaningfully—or simply rename the burden?

---

7) Now connect traffic to air quality: emissions are where miles and idling become lungs

Two practical tools to keep in mind:

• Air quality today: You can track local conditions using the AQI scale (Good to Hazardous) through AirNow and regional forecasts.
• Project-level modeling: California uses models like EMFAC (CARB’s on-road emissions model) for project-level estimates and planning.

And if you’re reading an EIR’s air quality chapter, you’re looking for answers to questions like:

• Which pollutants are analyzed (NOx, PM2.5, diesel particulate matter, etc.)?
• What thresholds are used (district guidance)?
• Are impacts “less than significant,” “significant but mitigable,” or “significant and unavoidable” (including cumulative)?

For the San Joaquin Valley, the regional air district provides detailed CEQA guidance (including analysis tiers and mitigation expectations).

---

8) The air-quality assumptions that most often steer conclusions

When you read an air quality section, you’re not just reading chemistry. You’re reading policy choices disguised as inputs. Here are the big ones:

A) The “cleaner future fleet” assumption

EMFAC incorporates regulations and expected fleet turnover.
That’s useful—and also dangerous in rhetoric.

Because it can lead to:

“Yes, there’s more driving, but future vehicles will be cleaner, so impacts are minimal.”

You should ask:

• What model year was used?
• Does it assume optimistic adoption curves?
• How does it treat heavy-duty diesel trucks (often the bigger PM driver)?

B) Speed and congestion assumptions

Emissions can rise in stop-and-go conditions due to idling and acceleration cycles. But widening roads to “fix” congestion can also induce more driving over time.

SB 743 was partly designed to keep CEQA focused on the environmental outcomes of driving (like pollution) rather than treating congestion relief as inherently “good.”

So if an EIR leans heavily on operational fixes, ask:

• Does the analysis consider induced travel/VMT rebound?
• Are improvements assumed to exist even if they’re not funded?

C) Hotspots and near-roadway exposure (the part averages can hide)

Even if regional emissions look “manageable,” people living near major corridors can experience higher exposures—especially to traffic-related pollutants.

Near-roadway impacts are serious enough that public health and research communities study interventions and exposure pathways specifically for them.

So ask:

• Does the air quality analysis address sensitive receptors near busy roads?
• Does it discuss diesel particulate matter and localized exposure—not just regional totals?

---

9) A quick “assumption audit” you can use on any traffic + air quality chapter

When you’re reading, keep a notepad and answer these ten questions:

If you can answer those ten questions, you’re no longer “reading a report.” You’re reading the logic beneath the report—which is where public decisions should actually live.

---