Canonical meanings for every term used across Territori — schema, formulas, UI copy and editorial. When a term appears anywhere in this product, its meaning is the one defined here.
Average Daily Rate. The average revenue earned per occupied key per night. Territori uses realized ADR — the rate actually paid — not list price. Source: comp data or operator-reported rates. Unit: USD.
The 85th-percentile realized ADR among comparable operators — same acreage band, same property type, same catchment ring. Represents the realistic revenue ceiling a new entrant can target if it executes well but does not yet hold a dominant category position. Used in parcel scoring and displayed in the S02 mini card and right panel.
See also: ADR, territori-formulas Section 5
The primary demand generator that a Market orbits. For Olympic National Park Gateway, the Anchor is Olympic National Park. Anchors provide visitor volume, seasonality and accessibility context. A Market may have multiple Anchors.
See also: Market, Visitor Nights
total_keys × days_in_period. The total supply-side denominator for a given measurement window. Pre-computed and stored on DemandPressureSnapshots for query performance. See also: Key, DemandPressureSnapshots.
See also: Key, DemandPressureSnapshots
Territori's application-level taxonomy for classifying hospitality developments — the labels operators actually think in (STR, BnB, Hotel, Lodge, Resort, Campground, RV, MPR). Distinct from county Land Use definitions, which use legal vocabulary specific to each jurisdiction. The mapping between a Build Type and the corresponding county Land Use(s) is managed by the BuildTypeLandUseMap entity, which acts as a translator between Territori's language and county law.
See also: Land Use
A drive-time radius used to define the competitive set around an Anchor. Territori uses 30-minute, 60-minute and 90-minute catchments. All supply, demand and operator data is scoped to a selected catchment.
A named positioning territory that an operator can own — e.g. "The Timber & Rain Lodge." Categories are distinct from amenity stacks. Two operators can have identical amenities but occupy different categories. Territori identifies unclaimed categories as whitespace opportunities.
An administrative approval granted by county planning staff or a hearing officer that allows a land use that is conditionally permitted in a zone — not permitted as-of-right, but allowable if the project meets specific criteria. CUPs are discretionary decisions (the county can impose conditions or deny) but are handled at the staff or board level, not requiring a legislative vote. Typically takes weeks to months, not years. Contrast with Comprehensive Plan Amendment (CPA), which requires a legislative act.
See also: CPA, Zone Designation
A legislative act required to change a county's comprehensive plan — the governing land use policy document. Required for Master Planned Resort designation in most Washington jurisdictions. Unlike a CUP (an administrative decision), a CPA requires a formal public hearing process and a vote by the county commission or council. Typically takes 1–3 years. In Territori's zoning data model, CPA_REQUIRED is a distinct status in ZoneLandUseStatus, separate from CONDITIONAL (which implies a CUP).
See also: CUP, Zone Designation
The degree to which operators in a Market are positioning similarly. High convergence means operators look alike to guests — same keywords, amenities, positioning pillars. Measured by the Positioning Convergence Index (PCI).
See also: PCI
visitor_nights ÷ available_keys_per_period. Measures how hard existing supply is being worked. A value ≥ 1.0 means demand equals or exceeds supply. Displayed as DPI Index (DPI × 100). Thresholds: ≥ 100 Demand exceeds supply (Sage); 70–99 Approaching capacity (Gold); 0–69 Low demand pressure (Rust).
See also: Visitor Nights, Key, territori-formulas
A period-based record storing the raw inputs and derived DPI values for a Market. One row per market per period. The time-series backing the DPI bar chart on the dashboard. Fields include: period_start, period_end, total_keys, visitor_nights, available_keys_per_period, dpi, dpi_index.
See also: Period, schema reference entity 25
A Market where incumbents already hold distinct positioning — low PCI (≤ 50). A new entrant must find an unclaimed gap rather than relying on category whitespace. Contrast with: Converging.
A composite 0–100 measure of how hard it is for a new operator to enter a Market — incorporating permit approval rates, regulatory sentiment and STR policy posture. Higher = more friction. Post-v0.1.
A polygon representing the area reachable from an Anchor within a given drive time (15, 30 or 60 minutes). Used to define catchment boundaries and scope supply data.
The canonical unit of accommodation supply in Territori.
Hotels: one key = one room (from public room-count data)
STRs and BnBs: one key = one bedroom (not one listing)
Using bedrooms for non-hotel inventory gives a comparable supply unit across property types. A 4-bedroom STR contributes 4 keys, not 1.
A named geographic catchment that Territori analyzes on an ongoing basis. "Olympic National Park Gateway" is the MVP Market. Everything — operators, parcels, scores, narratives — is scoped to a Market. A Market is the unit of subscription.
A positioning dimension that can be owned by an operator as a durable competitive advantage. Territori tracks 15 moat dimensions across four groups: Place, Context, Asset, Operator. Each dimension is scored for saturation — how many operators are actively claiming it.
See also: Moat Saturation, territori-formulas
How many operators are actively holding a given moat dimension in a catchment. Saturation levels: Wide open (score 10) → Open (8) → Contested (5) → Claimed (2) → Saturated (0). See territori-formulas for numeric score mapping.
Any entity running an accommodation business within a catchment — hotel groups, boutique lodges, STR owners, glamping operators, BnBs. The primary Territori user type.
A 2×2 strategic grid plotting PCI (convergence) against DPI (demand pressure). The four quadrants rank entry conditions for a new operator:
1 — Prime Entry: High PCI · High DPI. Best conditions.
2 — Find Your Angle: Low PCI · High DPI. Demand present, positions are taken.
3 — Steal the Audience: High PCI · Low DPI. Room to differentiate, thin demand.
4 — Avoid: Low PCI · Low DPI. Both challenges at once.
A specific real estate parcel that Territori has identified as a candidate site. Parcels are scored against moat dimensions, zoning and acreage requirements. The site-level unit of analysis.
A time window used for DemandPressureSnapshots records. Currently monthly — period_start is the first day of the month (e.g. 2026-01-01), period_end is the last day (e.g. 2026-01-31). Daily cadence is supported without schema migration.
A 0–100 composite measure of how similar competitors' positioning already is. High PCI = operators look alike (opportunity for a new entrant to stand out). Low PCI = incumbents hold distinct positions. Computed from five sub-axes: keyword overlap, positioning frequency, amenity similarity, price dispersion, review-axis overlap. Displayed as PCI Index (PCI × 100).
See also: territori-formulas §2, ConvergenceSnapshot (schema entity 24)
The ideal market condition for a new entrant: DPI ≥ 70 (demand is arriving) AND PCI ≥ 51 (operators are converging on sameness). The top-right quadrant of the Opportunity Matrix.
A residential property listed on platforms such as Airbnb or VRBO for short-term stays. Treated as non-hotel accommodation inventory. For supply purposes, STR keys = bedroom count.
See also: Key
A point-in-time intelligence snapshot generated for a Market, tied to a User subscription. Live seat subscribers receive ongoing Studies; report-tier subscribers receive a single Study.
The abbreviated zone code used in a county's GIS parcel export data — often a shortened or normalized version of the canonical code used in the actual zoning ordinance. For example, Clallam County parcel exports use R5 where the zoning text uses RCC5 (Rural Character Conservation 5-acre minimum). Stored as gis_code on the ZoneDesignations entity. Normalization between GIS codes and canonical codes is currently handled in TypeScript via ZONE_CODE_ALIASES until the ZoneDesignations table is seeded.
See also: Zone Designation
A regulated use category as formally defined in a county's zoning code — the legal vocabulary that determines what activities are permitted on a parcel within a given zone. Examples from Clallam County Ord. 1026: "Vacation Rental," "Bed and Breakfast Inn," "Outdoor-oriented Recreation Facility," "Master Planned Resort." Stored in the LandUses entity with verbatim definitions from the code. Distinct from Territori's application-level Build Types, which use operator-facing language. The translation between the two is managed by BuildTypeLandUseMap.
See also: Build Type, Zone Designation
Total guest-nights booked across all operators in a catchment during a measurement period. The demand numerator in the DPI formula. Source: NPS data, STR platform data or proxy counts.
See also: DPI
The official regulatory classification assigned to a parcel by the county — the formal name of the zone the parcel sits within. Each county defines its own set of zone designations in its zoning ordinance (e.g. Clallam County §33.05.010 defines 39 designations including RCC5 — Rural Character Conservation 5-acre minimum). Stored in the ZoneDesignations entity with both the GIS code (short form from parcel export data) and the canonical code (full form from the ordinance). The set of zone designations is county-specific — the same code may mean something different in a different county.
An editorial score from 1–5 indicating how complex a county's zoning system is to navigate for hospitality development. Stored as zoning_complexity on the Counties entity. Computed from three weighted factors: zone count (weight 0.4), hospitality permit posture — how often hospitality uses require conditional approval or legislative action (weight 0.4), and administrative burden — number of overlays, special review processes, and board approvals (weight 0.2). Formula: round(0.4 × zone_factor + 0.4 × permit_factor + 0.2 × burden_factor) where each factor is 1–5. Clallam County scores 4 (39 zones, MPR requires CPA, some overlay districts).
See also: Zone Designation, CPA, CUP