Who is already feeding this neighborhood?

The unit of analysis

What restaurant location analysis actually examines

General business location analysis asks what is true around any address. The restaurant version sharpens that question to a format with particular dependencies: a kitchen trades on proximity — food supply within walking distance, daytime and evening population, the anchors that put strangers on the street, and the direct competition already serving the same meals. It is also where evidence discipline matters most, because restaurant location is the field where confident vibes are cheapest and most expensive.

This page is therefore not a shortlist tool — comparing candidate addresses is site selection — and not a score. It is what a careful operator checks about one address, one category, before anyone signs.

The food-side evidence

The restaurants and food places around your point

The analyzer's activity controls carry a Food & Drink group with a Restaurants preset (and a Coffee Shops one, which is the same mechanism for a coffee shop location analysis). Selecting it does two things across the analysis surface: the competitive view orders the food-matched places by distance — its own definition, in the interface's words, is “a view over the same nearby places data; facts from the place records, no scoring” — and the category mix shows how the food supply sits against everything else loaded.

“Matched” is honest about its mechanism. On the live Google Places path, matching uses documented place types (restaurant, meal takeaway and delivery, fast food). On the open-data path, places from Overture and OpenStreetMap fall into a Food & Drink bucket through the platform's category grouping — and every record keeps its original source label viewable underneath, because grouping is a reading aid, not data. Density is computed as unique loaded place records per square kilometer of the study radius: a raw count with arithmetic attached, not an index of how hard your opening will be.

What a food listing can show, and where it comes from:

Beyond the direct competitors

What else is on these streets

A restaurant lives off context as much as competition. Loaded places are grouped into sixteen readable categories — Grocery, Retail, Healthcare, Hotels, Education, Fitness, Parks & Outdoors and more — and the inevitable “Other” bucket is clickable down to the raw source tags behind each place, so no classification is taken on trust. That mix around your point is the area's category profile, visible as shares of what actually exists.

For sharper questions there are the two opt-in tools: Co-location counts the specific categories you name — hotels, offices, gyms, supermarkets — around the site, without assuming any of them is complementary to a restaurant; and White Space probes categories you suspect are missing. Both are deliberate about their limit: “not observed” means no record was found in the loaded sources for this area — absence of evidence, kept clearly apart from evidence of absence. The deeper mechanics of all of this belong to competitor analysis; the restaurant reading is which of those questions you actually ask about a dining street.

Audience and access

People nearby, and how far minutes carry

Inside your study extent — a radius from roughly 100 metres to 20 kilometres, or a boundary you draw on the map yourself — population is summed from gridded datasets and shown beside the nearest city context: who is in the area, per the grid's own version and vintage. Land-cover shares and building-footprint counts, where published for the region, describe what kind of ground that population lives on.

For reach, the product is precise about its two instruments. The map's dashed rings are pure distance — labeled in metres, never sold as travel time. The separate drive-time probe routes a sample of points in a study area to the destination you fixed and reports measured minutes: average, fastest, longest, the share inside ten, fifteen and twenty minutes, and a five-minute distribution — with unroutable points excluded and counted, and the result labeled for what it is: car travel over sampled points, not an isochrone and not a model of everyone's journeys. Framing the audience and access questions properly is the subject of trade area analysis.

Where the evidence ends

What restaurant location analysis here does not do

• No success arithmetic. Revenue, footfall, profitability and demand estimates are not computed by anything on the platform — the analysis note that ships with results reads “raw observations only — no ratings, no predictions, no advice,” and no feature quietly adds them.
• No verdict, no “best location.” There is no restaurant score, no ranking of addresses, no recommended site. Density and competition are facts you weigh; deciding what a saturated food street means for your format is yours.
• No property economics. Rent, income and employment data are not in the catalog at all — a gap stated as a gap, not estimated around.
• No coverage pretense. Thin source coverage shows as thin or empty blocks with their reason attached; a quiet count over an under-covered area is exactly the silence the labeling exists to expose.

One pass in a larger program

Where this fits in LocateRight

The restaurant pass sits on the general machinery: it is the category-tuned lens on the point dossier, asks its supply questions through competitive evidence, sizes audience inside the catchment you choose, and hands surviving candidates to the shortlist compare. For an opening program — or a multi-site restaurant group — the workflow continues into expansion analysis: a selected restaurant analysis even pre-names its campaign container after the activity. Screening many addresses at once is a spreadsheet job for bulk analysis, and the method under all of it is location intelligence with sources named.