DC Parking Enforcement Atlas

Size: selected citation count (fixed scale). Color: most-cited category at each approximate location within active filters. A hollow diamond indicates an exact tie; it is not another category.

Missing and invalid issue times are not allocated to midnight.

Neighborhood Clusters are DC planning-analysis areas, not official neighborhood boundaries. Exact published coordinates are joined locally to DC’s polygons in EPSG:4326. Points on boundaries, overlaps, and unmatched locations remain unassigned; unmappable citations are excluded only when a geographic filter is active. Boundary source and definition.

The counts describe records in a downloaded, identity-checked monthly parking-violation source snapshot, including any fee and unspecified-code records supplied by DC. They are not a count of adjudicated violations. They do not measure all parking violations, enforcement coverage, occupancy, compliance, revenue collection, or a driver's likelihood of receiving a ticket.

DC GIS describes the supplied positions as street-segment centroids. A coordinate group may include labels from different street sides. The source coordinates may be coarse. A geographic bounding-box check is not proof that a point was assigned to the correct segment. Missing or invalid coordinates remain in overall totals and are excluded only from the map unless a geographic filter is active.

Issue dates are converted from the service's UTC-millisecond values into Eastern local dates, under its declared time-zone metadata. The separate issue-time strings are parsed independently. No missing time is silently assigned to midnight, and no vehicle duration is inferred. Zero bars mean no matching citations within a validated source month. They do not prove no enforcement occurred.

The versioned Studio Davis analytical classification is not an official DC categorization. Original codes remain available in the detailed violation selector and list. Category buttons filter the same selected citations used by the cards, pie and temporal charts; pie shares use those selected citations as their denominator. Unseen or ambiguous meanings remain counted under Vehicle status & other with a needs-review flag. “Unspecified violation” identifies a missing source description. High recorded activity is not, by itself, evidence that more enforcement is needed. Fines and amounts paid are not presented as municipal revenue. No license plate, owner identifier, ticket number, or ticket-level browser download is included.

This independent public beta shows accepted monthly snapshots, not real-time enforcement. The observation month and source-retrieval timestamp are distinct. Available snapshots are listed above; no claim is made that the newest accepted snapshot is the newest available DC data. Updates require a successful source refresh and deployment. The site checks for a newer deployed manifest and offers it without silently changing your selection. The GIS map requests the ArcGIS JavaScript SDK from Esri and reference tiles from DC GIS; web typography may load from Google Fonts. These services and the web host may receive routine request information. No analytics tracker, vehicle identifier, or ticket-level browser download is included. The map requires an internet connection. DC reference mapping is contextual and is not a reconstruction of July 2026 curb conditions.