Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the project location and pull 98% reliability high/low pavement design temperatures from LTPPBind (or the state DOT's published PG binder map/chart) using nearby weather stations.
Check the governing state DOT specification (referencing AASHTO M320/M332) for the required base PG grade on that route or functional class.
Determine whether traffic level (ESALs) or slow-moving/standing traffic requires bumping the high-temperature grade one or two steps per AASHTO M323 guidance.
Confirm with the DOT's approved binder supplier/terminal list that the selected PG grade is actually produced and stocked in the region.
Document the binder source, grade, and any anti-strip or polymer-modification requirement on the mix design submittal.
Known gotchas
LTPPBind's default 98% reliability output is a starting point, not automatically what the DOT spec requires — some agencies mandate a fixed grade table by county/route regardless of software output.
Grade-bumping rules for traffic speed/volume vary by agency; applying AASHTO's generic table instead of the state spec's own bumping rule can produce a non-conforming grade.
Binder producers don't stock every PG grade at every terminal; specifying a grade the local terminal can't supply causes sourcing delays.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?