For navigation & mapping platforms

A richer POI layer than your basemap gives you on its own

Turn-by-turn navigation and mapping platforms use catalog.xmap.ai to enrich search results and points-of-interest layers with category, hours, ratings, and activity signals alongside their own routing and basemap data.

WHAT YOU GET A downloadable CSV of business locations (name, address, coordinates, category, ratings, hours & more) filtered to exactly what you need.
What is catalog.xmap.ai

catalog.xmap.ai is a self-serve database of 140M+ real business locations across 40+ countries. Every record is an actual, physically-located business (not an estimate) with up to 36 structured fields: name, full address, latitude/longitude, category (three levels deep), brand and chain affiliation, hours of operation, phone and website, star rating and review count, open/closed status, and more.

You filter the catalog by category, brand, or geography in a live web interface, watch the matching record count update as you narrow the search, and export the results as a clean CSV file, ready to open in a spreadsheet, load into GIS software, or join against your own data.

The dataset refreshes every 30 days, so an export reflects recent openings, closures, and changes rather than a static snapshot from years ago.

140M+
Locations
40+
Countries
36
Fields per record
30 days
Refresh cycle
Why navigation platforms reach for it
Basemaps are thin on POI depth
Roads without rich places

Routing engines are strong on roads but often shallow on the 30+ fields users expect from a place result.

Coverage gaps hurt trust
A missing destination is a lost user

If a search misses a real business, users switch apps, coverage breadth matters as much as routing accuracy.

Licensing legacy providers is slow
Procurement shouldn't block a roadmap

Self-serve, pay-per-record access lets a team prototype a feature before signing anything.

Top use cases
POI search enrichment

Add category, hours, ratings, and phone number to a routing engine's place-search results.

Coverage-gap filling

Compare your existing POI layer against the catalog to find and fill missing destinations.

Category & icon mapping

Use the standardized category hierarchy to drive consistent map-pin icons and filters.

Freshness monitoring

Catch permanently closed locations and new openings on a monthly refresh cycle.

Chain & brand grouping

Group locations under a parent brand for chain-level search and filtering features.

Traffic & dwell overlays

Layer activity signals onto a map to show which nearby places are busy right now.

Field coverage vs. a basemap-only POI layer, illustrative

Share of results carrying each field type.

Name & category
Hours
Rating
Activity signals
Built to integrate

Query the API for live lookups, or bulk-export to seed your own POI layer.

GET /v1/search?category=restaurant
 &near=48.858,2.294&radius_m=1000
&fields=name,category,hours,rating,lat,lon

# -> enrich your routing engine's place results
# -> 30+ fields per record, delivered as clean CSV, refreshed every 30 days
In practice
Enriching a routing engine's place search

A navigation platform's place-search results were missing hours and ratings for most restaurants. The team queried the catalog by category and bounding box, joined the results on name and location, and shipped enriched search results without waiting on a legacy data contract.

See it enrich your map

We'll run a live query against your target category and geography.

Request a demo Other app dev categories
Free 15-min call with a data expert. No slides, just answers.
Grab a slot →