Location intelligence infrastructure
Exchange place data with usable local context.
LocalHub Import is Spott’s approved data exchange layer. Contribute location datasets for normalization, or request access to consume reliable business and locality data in your own product.
Source-aware Claim-safe Region-linked
$ localhub import ./places.json
→ reading 2,480 records→ resolving province + county IDs→ validating coordinates✓ batch ready for review_
Provide data
Send data to LocalHub.
Share licensed business or locality datasets. We map fields, validate coordinates, connect administrative IDs, detect conflicts, and preserve source attribution.
Propose a data sourceAccess data
Use LocalHub data.
Request an approved feed for your app, research, or service. Scope, fields, refresh cadence, licensing, and delivery method are reviewed for each use case.
Request data accessA controlled data path
Import is a lifecycle,
not a one-time upload.
Every stage exists to keep discoverable data useful while leaving verified business owners in control.
Send
Submit structured place records from an approved source.
Normalize
Map names, categories, coordinates, contact fields, and locality IDs.
Validate
Reject incomplete records and flag conflicts for review.
Maintain
Update source-linked records without replacing claimed business data.
Designed for real-world data
Messy inputs.
Predictable records.
Provider payload→LocalHub mapping→Spott place
Administrative accuracy
Province and county values resolve to backend taxonomy IDs—not hand-typed labels.
Conflict visibility
Potential duplicates and incomplete records stay visible for review.
Ownership boundaries
Imported records remain attributable to LocalHub Imports until an approved claim transfers control.
Integration-ready model
Stable external identifiers make future refreshes and source reconciliation possible.
A small, explicit contract
Send what identifies a place. Keep the source attached.
The exact transport and credentials are provided after source review. This preview shows the core record shape used to evaluate an integration.
externalIdnamecategorylatitudelongitudeprovinceIdcountyIdaddressphonewebsite
{
"externalId": "source:place-1842",
"name": "Example Coffee",
"category": "CAFE",
"location": {
"latitude": 38.2498,
"longitude": 48.2933
},
"locality": {
"provinceId": "...",
"countyId": "..."
}
}Before you integrate
Questions developers usually ask.
Not yet. Imports are enabled for approved data sources so mapping quality, licensing, refresh behavior, and ownership boundaries can be reviewed first.
After approval, control moves away from the importer identity. Future source refreshes must not overwrite owner-managed fields.
Integrations should resolve and store backend taxonomy IDs. Display names can change; stable IDs keep relationships reliable.
Share your data source, coverage, update frequency, licensing basis, and a small sanitized sample through the contact form.
Request integration access
Tell us about your data source.
Requests go directly to the Spott admin review queue. Include enough detail for us to assess licensing, coverage, refresh behavior, and mapping quality.
- Work email and organization
- Coverage and approximate size
- Source rights and update workflow
Bring a source. Leave with a system.
Ready to make local data useful?
Tell us what your dataset covers and how often it changes. We’ll evaluate the safest path into LocalHub Import.
Request access