Datadory notebook

How Developers & Data-Product Builders Use Specialized Consumer Services Data

Datadory delivers specialized consumer services data covering the four layers builder products actually stand on: named venues with starting prices and star ratings from a marketplace of 130,000-plus locations, official business-population counts reaching back decades on both sides of the Atlantic, point geometry for every mapped location, and a 6.99-million-review opinion corpus - typed, joined on shared keys and delivered daily, weekly, or hourly.

1,744 datasets. Pick your catch.

What does a developer actually get from this dataset pool?

Builders arrive at Specialized Consumer Services expecting thin coverage - it reads like a niche of salons, spas and funeral homes - and find a proxy-built slice instead. The industry contributes zero primary datasets of its own: no statistical agency surveys the label directly, so the slice pools 15 related records in from adjacent industries. The pooling arithmetic sounds like a weakness and lands as the opposite: one record scores a perfect 10 on Datadory's rubric, six score 9, and none scores below 7.

Every record answers one of four things a builder actually asks: who the businesses are, how many exist, what they charge and what customers say about them. Fresha - Global Salon, Barbershop & Spa Marketplace owns the first and third questions, Yelp's 6.99-million-review corpus grades the fourth, UK Business Register and Employment Survey (BRES) and the U.S. Census Bureau Data API - CBP / Economic Census / Wholesale Trade settle the second, and OpenStreetMap Overpass API pins everything to coordinates.

What goes into the geometry layer?

OpenStreetMap Overpass API returns mapped elements as geometry rather than summary cells: nodes, ways and relations carrying their full tag sets, queryable worldwide by tag, bounding box or area, deliverable as GeoJSON for direct mapping or as typed rows for a warehouse. Granularity is individual elements, coverage is the planet, and historical states can be queried by timestamp - the difference between a map background and a longitudinal supply record.

Tag density is the thing to verify before building on it, because adjacent tags differ by orders of magnitude. For accommodation, taginfo counted 452,341 objects tagged tourism=hotel (255,658 nodes, 190,479 ways and 6,204 relations) against just 329 explicit resort tags - most resorts simply wear the hotel tag, so filtering on resort alone undercounts the market three orders of magnitude. Fill rates stay honest too: names and contact fields run reliable, while the capacity trio of stars, rooms and beds survives on only a minority of properties, so capacity analysis needs a declared fallback rather than a hopeful join.

For repeat whole-country work, Geofabrik OpenStreetMap Data Extracts republishes the map as pre-clipped regional files - eight continents resolving to 555 named regions - with retained change history covering roughly 100 days of backfill and weekly full-history archives allowing exact reconstruction of older vintages. Through Datadory the two shapes collapse into one decision: name the regions and the grain, and the extract lands as documented rows either way.

How do the American count layers fit a builder's stack?

U.S. Census Bureau Data API - CBP / Economic Census / Wholesale Trade carries the structural load. County Business Patterns vintages run annually from 1986 through 2023, each cell holding employer establishments, mid-March employment and annual payroll by six-digit NAICS code, resolved across a geography ladder that runs from the national roll-down through states, counties, metros, congressional districts and ZIP codes. Employment and payroll values travel with companion flags grading disclosure treatment, so thin cells announce their uncertainty instead of hiding it - sum flagged counties with the flags, never after discarding them.

Five-yearly depth comes from the U.S. Economic Census - Wholesale Trade (NAICS 424), the pool's only perfect score: a sector table running 442,035 rows across nearly 21,000 geographic areas, carrying sales, gross margin, operating expenses and inventories beside the headcounts. Annual CBP vintages interpolate cleanly between benchmarks, which makes the pair the backbone of any store-density, territory-design or bottom-up sizing feature. The dealer-cut variant lives on U.S. Census County Business Patterns - Automobile Dealers Establishments, and browsable table versions sit on Census Data Tables & data.census.gov.

Two discovery hubs widen the aperture when a build needs exogenous context beyond the slice: Data.gov's catalog search spans 552,271 harvested federal and state records, and data.europa.eu's hub answered a single telecommunications query with 1,259 matches inside a 1,725,936-record index drawn from 210 catalogues. Through Datadory the split between feeds and consolidated files stops mattering - every layer lands under the same typed-column contract, delivered daily, weekly, or hourly.

Is Yelp's review corpus safe to build a product on?

Yelp's business-review corpus is the opinion layer of the pool: as training data, unambiguously valuable; as a production dependency, know what you are holding. Inside sit 6,990,280 reviews of 150,346 businesses across 11 US metropolitan areas, with per-business structured attributes - ambience, parking, good-for-kids, alcohol, outdoor seating - category aliases, hours by weekday, star ratings and 200,100 photos. Business, review, user and photo objects carry declared schemas, which is why the corpus is the standard benchmark for recommendation, sentiment and NLP work on real service businesses.

Two caveats shape expectations before anything ships. Restaurants dominate the category mix, so personal-care venues arrive as a minority slice rather than a curated vertical - filter by category before drawing conclusions about salon coverage. And the corpus moves as periodic snapshots rather than a continuous stream, so any panel you build needs its snapshot vintage stamped onto the rows; Datadory attaches that vintage to every delivery, which keeps a training set reproducible months later.

That snapshot behaviour is also why the corpus fits prototyping and model work better than live opinion features: production rating surfaces want current state, and current state comes from the marketplace rows above. For teams extending past reviews into language-model work, the pool adds the Hugging Face Datasets Hub - Fashion/Apparel Datasets record, listing over a million datasets with declared feature schemas to prototype against.

How do you join UK service-business counts into your own tables?

UK service-business structure comes from UK Business Register and Employment Survey (BRES), drawn from an IDBR snapshot taken 14 March 2025: 2.73 million VAT/PAYE enterprises and 3.2 million local units, laid out across 28 numbered tables cut by 4-digit UK SIC 2007 class, country, region, county, district and employment size band, with legal status crossed in. One implementation detail saves a debugging afternoon: counts are control-rounded to base 5, so treat them as ranges rather than exact integers, and aggregate with that rounding in mind.

Annual editions reach back to 1994, which turns a single workbook into a longitudinal panel once vintages are stitched - pre-2017 editions split across separate table files, and cross-tabs beyond the published tables need the companion query dataset rather than the reference extract. The deeper dive sits in uk business population by sic code.

What does a production-ready integration stack look like?

A builder wiring this pool into a working service ends up with five steps, cheapest dependencies first:

  1. Prove the join on real rows. Request a sample cut to the actual question - one city's venue rows, one county-year CBP panel, one SIC class - and confirm the keys resolve before anything recurring starts.
  1. Fix the grain. Decide whether rows resolve at venue, establishment-cell, enterprise or element level; each record's field dictionary states its native grain, so nothing gets silently aggregated twice.
  1. Load history in layers. Five-yearly Economic Census benchmarks sit under annual CBP vintages; BRES editions concatenate back to 1994 once the early split-file layouts are mapped; OSM history reconstructs to a timestamp.
  1. Schedule around the decision, not the source. Daily-or-faster for venue state where ratings move mid-week, month-close rhythm for turnover indices, versioned files keyed to snapshot dates for the periodic registers.
  1. Join on four identifiers. Geography codes (county, place, ZIP, region), classification codes (NAICS, UK SIC 2007), venue names typed for matching, and period. Every other column hangs off those keys.

Ranked for developer experience - join readiness first, documentation second, depth third - the pool stacks up as follows:

Where to go next

The specialized consumer services data guide is the pillar post: all 15 pooled records scored, field-documented and grouped by workflow, with the census, survey and POI layers mapped end to end. The best specialized-consumer-services datasets ranking orders every record by quality score, and the specialized-consumer-services data hub indexes the complete scored shelf.

Sibling angles get their own posts: what data exists on salons, barbershops and spas works the venue-and-price layer, census data api county business patterns unpacks the American establishment grid, and extract poi data from openstreetmap the geometry layer. The persona-scored shortlist behind this article sits on developers-builders resources, which collects the sibling industry slices when you need an adjacent vertical. For provenance beyond this slice, the U.S. Census Bureau source profile and the UK Office for National Statistics profile cover what else each publisher ships.

Pick up where this leaves off

Every one of these ships with sample rows before you commit to anything.

Soft Drinks & Non-Alcoholic Beverages 120+ countries reported

Fresha - Global Salon, Barbershop & Spa Marketplace

Restaurants United States - 11 metropolitan areas, restaurants the…

Yelp structured datasets

Systems Software United States: national, states, counties, metropolitan and…

U.S. Census Bureau Data API - CBP / Economic Census / Wholesale Trade

ESTAB · EMP · PAYANN

Highways & Railtracks Global crowd-mapped coverage on every continent, with density…

OpenStreetMap Overpass API

Hotels, Resorts & Cruise Lines Worldwide wherever mapped - every continent represented…

OpenStreetMap Hotels via Overpass Turbo

Want rows instead of a pitch? Name the datasets.

API, files, or your warehouse. Daily, weekly, or hourly.

Get a sample

Questions worth asking

Which dataset carries coordinates and prices for salons and spas?

Fresha - Global Salon, Barbershop & Spa Marketplace. Each of its 130,000-plus partner venue rows carries name, business type, street address, telephone, latitude and longitude, a starting-price band such as 'From GBP 35', and an aggregate rating with review count. One London hair-salon batch yielded 130 complete venue records.

How many salons and personal-care businesses are counted per area?

On the US side, County Business Patterns reports employer establishments, mid-March employment and annual payroll by six-digit NAICS down to ZIP code across vintages 1986-2023, with disclosure flags marking thin cells. On the UK side, BRES counts 2.73 million enterprises and 3.2 million local units by 4-digit SIC class, region and employment size band, rounded to base 5.

Can I ship a commercial product built on this pool?

Yes. The count, geometry and venue layers clear standard commercial product use; the review corpus behaves as a benchmark-and-prototype snapshot, so production opinion features should read from delivered rows rather than raw archive copies. Each record's constraints travel in its dictionary, so the check belongs in ingestion code rather than in paperwork discovered after launch.