Coverage and expansion map

Start in the DMV, then expand by confirmed portal family

TheTrafficApp keeps live coverage, pilot targets, and research targets separate on purpose. eTIMS-family expansion comes first because the portal structure is reusable across nearby jurisdictions before the team moves into other vendor families.

2 live jurisdictions DMV-first expansion Read-only pilots

Coverage rings

Map the DMV first, then crawl outward

The site should always show the difference between live coverage, near-term pilots, and research-only markets.

LIVE

Washington, DC

Parking violations

Speed camera citations

Current live coverage and the most visible resident lookup entry point.

LIVE

Montgomery County, MD

Parking violations

Traffic camera citations

Current live coverage and the second anchor point for the DMV footprint.

PILOT TARGET

Prince George's + Baltimore County

eTIMS-family jurisdictions

Near-term DMV onboarding candidates

The next ring out from the current live footprint.

RESEARCH

Arlington, Alexandria, Fairfax + beyond DMV

eTIMS-family research lane

Wilmington, Minneapolis, Saint Paul, Austin parking-only

Expansion starts in the DMV and crawls outward by verified portal pattern.

Vendor families under research

Other systems being mapped next

The goal is to scale by portal family, not by city name alone.

eTIMS family

Current core stack

The live product and near-term DMV rollout are built around the eTIMS portal family because the flow, form fields, and parser shape are reusable.

Passport

Cloud enforcement and citation issuance

Passport's official product materials describe an online, cloud-based enforcement flow that is often paired with citation issuance and payment workflows.

Official product page
Tyler

Electronic parking and payment modules

Tyler's official product materials show parking citation and payment modules that are separate from eTIMS and worth mapping as a distinct family.

Official product sheet
Custom portals

City-specific stacks

Some jurisdictions use custom or locally configured portals. Those stay in the research lane until the portal family is verified and a safe parser path exists.

How expansion works

The first move is the DMV, then the registry gets wider

Each new city should be a registry entry and a verified parser path, not a one-off branch.

1

Confirm the portal family

Identify whether the jurisdiction is eTIMS, Passport, Tyler, or a custom portal before promising support.

2

Add the registry entry

Record the city, state, lookup mode, scope, and official portal links in the jurisdiction registry.

3

Test the parser path

Verify the selector flow and the result payload before anything is called a live jurisdiction.

4

Launch a narrow pilot

Keep the rollout read-only, bounded, and easy for city staff to review before expanding farther.

Need the pilot framing too?

Use the municipal pilot and trust pages alongside this map when you are drafting outreach for a city or county.