Every calendar refresh used to leave me with geographic cleanup.
Ticketing-market boundaries are not publication boundaries. A provider’s Southern California market can include Bakersfield, Ventura, Santa Barbara, San Luis Obispo, Imperial County, and occasional edge cases beyond California. A broad coordinate rectangle has similar spillover.
The fetchers accepted those records, wrote them into several outputs, and left a later audit to identify venues that did not belong.
The workflow was catching errors after they had already become data.
Move The Boundary Before The Writers
SoCalNomad’s editorial area is five counties: Los Angeles, Orange, San Bernardino, Riverside, and San Diego.
I moved that decision into both primary event fetchers. They now resolve a venue against the same county model before any database, archive, or frontend writer receives the event. Records outside the five counties are dropped unless the venue belongs to a small explicit exception list.
The SeatGeek importer also writes the resolved county when creating a venue. Previously, new records often began with a null county and depended on a post-run repair.
The First Run Proved The Placement
During the first full production refresh with both gates active, the Ticketmaster path rejected 108 out-of-area events before publication. The SeatGeek candidate-venue set also contracted to the intended geography.
More importantly, the null-county audit came back clean. The single new venue was created with its county already assigned.
I did not merely get fewer bad rows. A recurring repair procedure became a verification step.
One Definition, Several Sources
The important architectural change was not the bounding-box arithmetic. It was applying one editorial geography consistently across providers.
Without that shared rule, each integration invents its own meaning of Southern California. Data from different sources can then look compatible while describing different regions.
The explicit exception list keeps deviations visible. If the project deliberately covers a venue outside the normal boundary, that decision appears as policy rather than as an accidental coordinate leak.
Filters Cannot Correct False Source Data
A geographic gate still trusts provider coordinates. An out-of-area venue carrying incorrect local coordinates can pass. No bounding rule can infer that the source location itself is wrong.
That residual risk belongs in the audit, along with unusual new venues and exception-list growth.
The gate did not eliminate review. It moved routine rejection to the earliest safe boundary and reserved human attention for genuinely ambiguous cases.