Treating commute as a filter, not a footnote

"45 minutes to my kid's school" and "45 minutes to downtown" are different constraints, and a good job search should let you apply both. The default commute filter on PiNC accepts two anchors — an origin (usually your home) and a destination (optional; often a partner's workplace or a daycare). Every job is scored by distance to origin with a soft penalty climbing past 30 miles.

Why we compute haversine first, route-aware later

Route-aware commute APIs cost money per request and don't scale to 200,000 jobs. We run haversine distance for the fast pass — good enough to sort and filter the list — and save the route-aware calculation for the detail panel, where you only pay for the one job you're actually looking at. The detail's "28 min drive" number IS route-aware, and it lines up with what Google Maps would tell you within a minute or two on most routes.

The destination field

Nobody else does this, and we think it's the single most useful thing we've added. Set a destination — a school, a partner's office, an elderly relative's house — and every job's commute time is computed from the origin AND from there. If both are reasonable, the job is a candidate. If one is brutal, we tell you up front in the detail panel.