Repository navigation
Measure the incremental value of a direct AllThePlaces extract #397
Description
Activity
Overnight preflight, rechecked against
bf47e937a2457f4a2539bcf43d1bf043ccea7248and the public instance on October 7, 2026:- ATP access itself is available: the official homepage redirects to
https://alltheplaces.xyz/and returns HTTP 200. Upstream licensing still distinguishes CC0 output data from MIT spider software. No extract was downloaded or counted as a measured improvement. - Source normalization already records ATP donor identity, property, record ID, update time, license and release. Current enrichment reads phones/websites and provenance; its current Overture row contract does not expose opening hours. These are promising comparison targets, not quantified incremental benefit.
- Public TileJSON identifies OSM replication time
2026-10-03T20:20:50Z, sequence4927. The public integration registry has 104 entries and no Overture integration entry; it supplies no imported Overture release or matching OSM POI generation. That does not prove no dataset exists elsewhere, or that the TileJSON input is the exact POI/conflation snapshot. The committed provider validates database release state, which is different evidence.
I am leaving the measured pilot open rather than substituting a fresh unrelated Overture release or the inherited conflation corpus for the required already-imported baseline and new human-reviewed labels. Next prerequisites are a pinned regional export of the actual OSM/Overture generations (with checksums and source IDs), a fixed candidate ATP run, and independently reviewed branch/tenant/closure cases with denominators. Then set value/quality thresholds before acquiring/evaluating the extract and use a disposable migrated database. The discovery evaluation tooling in #424 will support reproducibility, but does not supply those missing real-data judgments.
- ATP access itself is available: the official homepage redirects to
Before you start
Objective
Determine whether a current direct AllThePlaces (ATP) run adds correct useful businesses, hours and contacts beyond the exact OSM/Overture releases already imported. Overture already carries ATP-derived provenance; the pilot must measure the remaining delta rather than count ATP records as wholly new.
Scope
One reproducible bounded regional comparison using a pinned published ATP extract, checksums/run timestamps, matching OSM/Overture releases and a labeled sample of difficult businesses. Use current conflation/evaluation rules as a starting point, including distinct chain branches, tenants/floors, closures and contradictory identities. Deliver a go/no-go report and reproducible acquisition/normalization/evaluation instructions. Out of scope: scheduled production ingestion, worldwide rollout or automatic OSM edits. Decide pilot regions and minimum quality/value thresholds before acquisition.
Verified current state
Rechecked against
mainata8e03bc3efc49207d91f7c1855402c6cf149b8fdon October 7, 2026.Completion criteria
Verification approach
Run the existing conflation metrics on controlled/labeled fixtures and validate counts against sample identities. A pilot script must have deterministic positive/negative cases and resource measurements. For any committed tooling:
pnpm lint,pnpm check-types,pnpm test; use a migrated disposable PostGIS database for real data comparison, andpnpm -C docs buildfor the report.Dependencies
#393 provides the visual baseline. Related #301 concerns Overture release scaling, not direct ATP evaluation. A production ATP issue will depend on a positive pilot result; ambient tiles are useful later but are not needed to run this comparison.
This is backlog planning, not authorization to expand the implementation beyond this scope. Resolve named decisions during triage before scheduling work.