Regions & corridors

The county argument selects the region. Geofence works for every region; route and depot require interstate route artifacts, currently built for Travis and the cross-state interstate corridors.

Always check the live list

The table below is the full mode matrix from the catalog. The set of regions actually loaded by a given server is reported by hb.regions(), so check against it before sending.

for r in hb.regions().regions:
    print(r.county, r.modes)

Mode availability by region

Region	Geofence	Route	Depot
travis	✅	✅	✅
houston	✅	-	-
sanantonio	✅	-	-
dallas	✅	-	-
sf	✅	-	-
la	✅	-	-
phoenix	✅	-	-
vegas	✅	-	-
sandiego	✅	-	-
sacramento	✅	-	-
ca_az_interstates	-	✅	✅

City geofences

The geofence regions are metropolitan counties across TX, CA, AZ, and NV, for example travis (Austin), houston, dallas, sanantonio, sf, la, sandiego, sacramento, phoenix, and vegas. Each carries its own crash and calibrated-VMT layers.

Interstate corridors

ca_interstates and sw_interstates are not cities; they are multi-county interstate networks that support route and depot modes:

• ca_interstates: California interstates (e.g. I-5, I-80, I-580, I-205).
• sw_interstates: CA + AZ cross-state corridors (I-10 / I-15 / I-40).

For route mode you pass (route, milepost) segments; multi-corridor trips are stitched together via a junction graph. For depot mode you pass two lat/lon pins and the engine routes between them.

California-only denominator toggle

The denominator_vmt filter (CPRD vs HPMS) is meaningful only for the California geofence regions. Texas/Arizona/Nevada counties use a single state-DOT calibrated denominator and reject denominator_vmt=hpms with a 400.