Hourly vehicle and pedestrian traffic on linear paths, with historical depth for trend analysis. Every path resolves to its parent face, viewshed, and originating place.
Pathcast is a calibrated traffic model. Basecast trajectories supply the input movement signal. DOT permanent counters supply the ground truth that calibrates Pathcast outputs. The query API returns hourly counts at the segment level, with direction and mode breakouts where the underlying signal supports them.
Every path response carries a provenance block plus a calibration_source field identifying the DOT counter or counters used for the segment.
What you get
Hourly traffic measurements on any Motionworks path segment.
Date-range historical traffic for trend and seasonality work.
Path metadata with linkage back to the face and viewshed it feeds.
When to use this Job
You are sizing pedestrian or vehicular movement for a new market study.
You need historical traffic context for a retail-site or development decision.
You are debugging an exposure model and want to verify traffic upstream of a viewshed.
How it works
1Fetch a single path with GET /pathcast/paths/{path_id} to get its geometry and metadata.
2Pull current hourly traffic with GET /pathcast/paths/{path_id}/traffic.
3For trend analysis, pull a date range with GET /pathcast/paths/{path_id}/history.