Skip to content
All Resources
Location Intelligence 9 min read

Prepared by GSDSI Regulatory Content Team

Last updated

Editorial standardsTrust Center

POI Data Provider Comparison: What to Look For in 2026

A POI (point of interest) data provider is best judged on five tests, not on record counts: coverage of your own categories and countries, polygon quality, how fast closures and openings appear, stable place IDs, and permitted use. Run every finalist through the same trade-area sample before you sign.

How to use this article

Read the checklist here, then use the linked hub and product pages for procurement citations.

Buyers who search for a POI data provider usually get lists of names and record counts. Those lists do not tell you which file will survive your use case. This guide gives you the criteria instead, each tied to a public standard or primary document, so you can build a shortlist and a request for proposal (RFP) that any vendor can answer the same way. GSDSI sells POI data and POI and geofencing as one option among many, and the scorecard below applies to us too.

What a POI data provider sells

A POI data provider sells a database of places, each with a name, an address, a category, a location and usually a status. Some files add brand hierarchy, hours, or a boundary shape around the building. The GeoJSON specification (RFC 7946) shows the common shape of such a record: a Feature object that pairs a geometry with properties such as a name and a category.

Commercial files differ on what sits around that core. Some bundle visit analytics. Some sell only the places and leave measurement to you. Some add identity or mobility data that can be joined to the place. Decide which job you are buying for before you compare anything, because the right file for a navigation app is rarely the right file for a foot traffic study.

POI data provider comparison: the criteria that matter

Seven criteria separate one POI data provider from another in practice. The table lists each one with the question to ask and the evidence to request. Score every finalist on the same rows, using the same sample, and weight the rows by your use case.

POI data provider evaluation criteria, as of November 2026. Source: GSDSI editorial synthesis of World Wide Web Consortium (W3C) and Open Geospatial Consortium (OGC) public documentation
CriterionQuestion to askEvidence to request
CoverageDoes the file cover my countries and categories?Counts for your own industry codes and country list, with the date counted
GeometryIs each place a point or a boundary?Sample boundaries for your densest corridor
FreshnessHow are closures and openings detected?A change file covering a closure you already verified
Place IDsDoes the identifier survive refreshes?A crosswalk between two releases
DeliveryDoes the format match my stack?A sample in the format you will ingest
ComplianceWhat uses are permitted and how is deletion handled?The license text and the deletion workflow
PriceWhat scope does the quote cover?A scope document that names geography, category, geometry tier and refresh

Coverage: countries and categories, not global totals

Coverage claims fail when they are global. A worldwide total hides thin countries and thin categories. Ask every vendor for counts on your own industry list, using the North American Industry Classification System (NAICS) where you work in the United States, and for a country table where you work abroad. GSDSI states POI and mobility location coverage in 150+ countries, and we confirm availability by geography in the sample rather than in a slide.

The U.S. Census Bureau gives you neutral reference points. Its County Business Patterns series reports establishments by industry and geography each year, but it covers only employer establishments and leaves out some industries. Use it as a sanity check on a category you know, and note the gaps before you read a mismatch as a vendor error.

Polygons or points: geometry changes the answer

Geometry decides how a visit gets attributed. A point represents a place as one coordinate. A polygon represents the building or parcel footprint. On a strip mall or a medical plaza, a radius around a point catches neighbors that a footprint would exclude.

Ask what shape each record carries and in which format. The GeoJSON specification (RFC 7946) defines both Point and Polygon geometries with WGS 84 coordinates, so any vendor can deliver a boundary in a form your tools read. The OGC Simple Features standard defines the same geometry classes for databases. Some files carry only a point per place, so a file without boundaries is not a defect, but it is a limit you should price in.

Freshness: how fast closures and openings reach the file

Freshness is the quiet difference between providers. Businesses open, close, move and rebrand all the time, and the Census Bureau's Business Dynamics Statistics program measures establishment openings and closures every year for exactly this reason. A file is a photograph of a moving subject.

Do not accept the word refreshed. Ask what the refresh touches: the whole file, only flagged records, or new locations alone. Ask whether closures are detected or simply aged out. Ask whether you receive full snapshots or changes only. The W3C practice of providing information on the changing nature of spatial things points the same way: a vendor that can show you what changed between two releases gives you something concrete to check in a closure test.

Place IDs and join keys: the hidden integration cost

A stable place identifier is worth testing early. The W3C Spatial Data on the Web best practices advise stable, persistent identifiers for spatial things so that links to them do not break. The same logic applies to a licensed file: if the ID changes when a record is refreshed, your history breaks.

A good identifier registry records when each ID was first issued, when it last changed, and what replaced it when a place closes. Ask any vendor three questions. Does the ID persist across releases? Is there a crosswalk to your own store identifiers? How do franchise locations roll up to a parent brand?

Delivery formats and schema notice

Delivery fit is pass or fail. Confirm that the vendor can ship the format your warehouse reads, whether that is flat files, an application programming interface (API), a cloud share or a columnar format. GeoParquet is an incubating OGC standard that adds point, line and polygon types to Parquet, so a vendor that supports it is delivering geometry in a form that analytics engines read directly.

Also ask for schema change notice and deletion semantics. A feed that renames a column without warning costs more than a feed that costs more per month. Put the notice period in the contract and test it in the pilot, as covered in our guide to refresh cadence and drift monitoring.

Compliance and permitted use

Compliance belongs in the scorecard as a pass or fail gate before any numeric score. A POI-only file carries less risk than a bundled mobility file, but the license still has to say what you may do with derived visit counts and activation exports. For any mobility join, review the sensitive location data compliance checklist first.

Ask whether the vendor is a registered data broker where registration applies. The California Privacy Protection Agency (CPPA) runs a data broker registry and the Delete Request and Opt-out Platform (DROP), which lets Californians send one deletion request to all registered brokers. Your vendor should be able to explain how those requests reach delivered data. For the contract side, see data licensing agreement red flags.

POI data providers for retail site selection

Retail site selection weights the criteria differently from advertising. Site selection teams overweight coverage of competitors and category depth, because the question is who else is on the corridor. They can accept a slower refresh if the geometry is right. Teams in retail that measure visits overweight boundaries and freshness, because a stale closure inflates last year's comparison.

Activation teams weight place IDs and delivery heavily, because the file has to join to audiences and exports every week. Set the weights before any file arrives and publish them to the finalists. Weights chosen after the scores are opinions, not a method. Where several people score, give each row an owner: data science for accuracy, legal for compliance, engineering for delivery and finance for cost.

Run a bake-off before you sign

A bake-off on one trade area beats any spreadsheet of claims. Pick two or three areas that a colleague can walk, and ask every finalist to deliver those areas in full. Then score what you can check without trusting anyone.

  1. Write the job to be done: site selection, visit measurement, competitive benchmarking or activation.
  2. Freeze a chain list and a ground-truth list of venues you have verified by hand.
  3. Score the share of real businesses that appear and the share of records that no longer exist.
  4. Count duplicates that describe one physical location under different names.
  5. Check the open or closed status against what you saw on the street.
  6. Publish the weights and a one-page decision memo that names the disqualifications.

Our vendor bake-off checklist and seed match testing guide give the full procedure, and the RFP scoring matrix turns the results into a score. Open files need the same test. Our recount of OpenStreetMap amenity tags shows why a large count can hide records that are not businesses.

What changes the price of POI data

POI pricing follows scope more than record count. Geography, category, geometry tier, refresh commitment, delivery path and downstream rights each move the quote. Ask every vendor to price the same scope document so the numbers compare. Our guide to POI data pricing explains each driver and the contract terms that raise the effective cost.

Next step: request a chain-level sample

Send us your chain list and one trade area, and we will return a sample you can score with the table above. Request it through contact, and run the same test on every other finalist.

Frequently Asked Questions

How do I compare POI data providers?
Score each provider on the same rows: coverage for your countries and categories, geometry, freshness, place ID stability, delivery format, compliance and scope-based price. Use one shared sample on trade areas you can verify in person, and publish the weights before files arrive.
What is the best POI data provider for site selection?
No single provider wins every job. Site selection favors category depth and competitor coverage on your corridors. The best choice is the file that passes your coverage, polygon and closure tests on your own chain list, not the one quoting the largest total.
Why do POI record counts differ between providers?
Providers count different things. Some count places, some count brand locations, and some include historical or closed records. A count is comparable only when the definition of a record, the categories included and the date counted all match, so ask for those three facts.
Do POI data providers include polygons?
Some do and some do not. Some files store each place as a single point, while others add a boundary around the building. Ask each provider what shape every record carries, in which format, and for which geographies.
How often should POI data be refreshed?
Refresh frequency matters less than what the refresh touches. Ask whether closures are actively detected, how long a real-world change takes to reach your delivery, and whether you receive snapshots or changes only. Test it with a closure you already verified.
Does GSDSI offer POI data outside the United States?
Yes. GSDSI states POI and mobility location coverage in 150+ countries, and we confirm availability for your specific countries and categories in a sample before any license. Request a chain-level sample through our contact page and score it against the criteria above.

✓ Opt-Out Request Honored via Global Privacy Control