---
title: "Area"
description: "A bounded geographical region: a neighborhood, a region, a grid cell, a ZIP code. Area datasets describe activity *within* an area, useful when point-of-interest granularity is too narrow."
slug: "/docs/concepts/location-types/area"
last_updated: "2026-08-31"
location_type: "area"
available_metric_count: 6
example_use_case_count: 3
---


# Area

A bounded geographical region: a neighborhood, a region, a grid cell, a ZIP code. Area datasets describe activity *within* an area, useful when point-of-interest granularity is too narrow.

## Available metrics

- [Foot Traffic w/ Visitor, Worker & Resident](/docs/concepts/metrics/foot-traffic-vwr.md) (what+when) — Foot-traffic at the area level split by visitor / worker / resident roles. Lets you separate transient activity from baseline residential activity.
- [Visit Length](/docs/concepts/metrics/visit-length-area.md) (what+when) — Distribution of visit durations within an area.
- [Visitor Profile](/docs/concepts/metrics/visitor-profile-area.md) (who) — Aggregated profile of visitors entering an area.
- [Visitor Demographics](/docs/concepts/metrics/visitor-demographics-area.md) (who) — Demographic breakdown of visitors to an area.
- [Origin-Destination Matrix](/docs/concepts/metrics/origin-destination.md) (how) — Flows of visitors between origin and destination areas over a time window. Foundational for transportation modeling and spatial-economy analysis. Currently Nordics-only.
- [Trade Area](/docs/concepts/metrics/trade-area-area.md) (how) — The geographic area that contributes the most visitors to a target area.


## Location sets of this type

- [Estonian Neighborhoods (al3)](/docs/datasets/est/location-sets/neighborhood_est.md) — EST
- [Estonian Regions (al2)](/docs/datasets/est/location-sets/region_est.md) — EST
- [Estonian 250m Grid](/docs/datasets/est/location-sets/grid_est.md) — EST
- [Norwegian Basic Statistical Units (al4)](/docs/datasets/nor/location-sets/neighborhood_al4_nor.md) — NOR
- [Norwegian Statistical Tracts (al3)](/docs/datasets/nor/location-sets/neighborhood_al3_nor.md) — NOR
- [Norwegian Municipalities (al2)](/docs/datasets/nor/location-sets/region_nor.md) — NOR
- [Norwegian 250m Grid](/docs/datasets/nor/location-sets/grid_nor.md) — NOR
- [Swedish Districts (al3)](/docs/datasets/swe/location-sets/neighborhood_al3_swe.md) — SWE
- [Swedish Municipalities (al2)](/docs/datasets/swe/location-sets/region_swe.md) — SWE
- [Swedish 250m Grid](/docs/datasets/swe/location-sets/grid_swe.md) — SWE
- [Finnish Postal Codes (al3)](/docs/datasets/fin/location-sets/neighborhood_al3_fin.md) — FIN
- [Finnish Municipalities (al2)](/docs/datasets/fin/location-sets/region_fin.md) — FIN
- [Finnish 250m Grid](/docs/datasets/fin/location-sets/grid_fin.md) — FIN


## Example use cases

- Reporting of area development: track foot traffic at the neighborhood level
- Public infrastructure planning: identify high-density zones
- Real-estate due diligence: understand local visitor flows


## Custom boundaries

You are not limited to the pre-built location sets. If you have your own map (trade zones, sales territories, property outlines, catchment polygons), Pine59 can attribute its metrics to boundaries you define, so the data lines up with the geography your organization already thinks in. Reach out to support@pine59.com to set up custom boundaries for your account.