Chain Location Network Monitor (Overture Places)
Pricing
from $5.00 / 1,000 chain network changes
Compare chain/brand locations in a small area between two Overture Places releases or a saved baseline: newly observed, no-longer-observed, changed and uncertain records as source observations.
Brand names to track. Matching uses brand.names.primary and the record name (see matchMode). Add spelling variants per brand as separate alias entries — e.g. "Albert Heijn" plus "AH to go". Keep the list small; each brand adds matching work.
[ "Albert Heijn", "AH to go"]Area to observe, in WGS84 degrees: { "west": 4.88, "south": 52.36, "east": 4.91, "north": 52.38 }. Keep it small (a city district): extraction cost grows quickly with area and the source has no country partition. Returns records whose coordinates fall inside (west..east, south..north).
{ "west": 4.88, "south": 52.36, "east": 4.91, "north": 52.38}Overture Maps release ID of the observation to analyze, e.g. "2026-08-19.0". Only about two monthly releases are kept upstream; pin the release explicitly so repeated runs compare the same data. Must be newer than releasePrevious.
Optional second Overture release ID (e.g. "2026-07-22.0") to compare against the current one. Leave empty to record a baseline run: locations are stored as first observation, no change events are produced, and the next run can compare against this baseline. Must be older than releaseCurrent and, like it, still hosted by Overture (about two releases are retained).
How a record is attributed to a brand. "brandField" uses only the Overture brand field (strict, misses records where brand is empty). "brandOrName" also matches the location name — more sensitive, but a name containing the brand text is not always a location of that chain, so check matchEvidence in the output.
Exclude records whose Overture confidence is below this value (0–1). The source mixes low-confidence records from many providers; the default filters obvious noise but is not a guarantee.
Exclude records whose primary Overture category is in this list — used to drop obvious non-store matches (e.g. "casino", "transportation"). Applied to the primary category only.
[ "casino", "transportation"]If true and no releasePrevious is given, compare against the baseline saved by an earlier run (named key-value store, per brand-area configuration). A scheduled run with this option keeps the network history alive. With releasePrevious set, that explicit pair of releases is compared and the baseline store is only refreshed, never used for events. With no baseline yet, this run records one (all records reported as first observation, no change events).
Hard cap on total HTTP bytes fetched per release, including metadata. The probe for a small city-district area needed ~33 MB; a larger area needs more row groups. The run aborts (without writing a baseline or disappearance events) when the cap is exceeded.