Primary Use Case
Analyze origin, destination, and O&D market demand using weekly search activity and business or leisure segmentation.
Understand Demand Signals, Compare Airport Markets, and Build Fast Forecast Narratives.
DemandView is a browser-based airport demand scorecard that combines historical weekly search demand, geographical market views, and a lightweight predictive layer. This help page explains how the product is structured and how to use each view effectively.
Best For
Airport teams, network planners, revenue managers, and analysts who need a fast read on search demand trends and event-driven uplift.
Core Views
Searches Dashboard, Map View, Predictive Demand, and Admin each serve a different stage of market evaluation.
Overview
What DemandView Does
DemandView is designed as a single-page analytical workspace. Users select an origin city, destination city, or both, then the product aggregates weekly demand records into charts, rank tables, a map, and a forecast summary.
Single-page web app
Origin Mode
Select an origin city to study outbound search demand, top destination markets, seasonality, and weekly search movement from that origin.
Destination Mode
Select a destination city to study inbound demand, top origin markets, and the destination-side demand footprint visible in the historical search data.
Market Mode
Select both origin and destination to isolate a specific O&D market. Charts and tables narrow to the directional market relationship.
Dual-City Mode
Select the same city for both origin and destination to evaluate combined outbound and inbound demand around a single airport market.
Getting Started
How To Begin a Session
The product loads airport metadata first, then fetches demand data as you select cities. Initial usage is driven from the left-side filter column.
Recommended workflow
- Open the DemandView Airport Scorecard in a browser and wait for metadata to finish loading.
- Use
Origin Cityand/orDestination Citysearch fields to choose the market you want to analyze. - Refine results using
Trip Type,Sales Week, andBusiness and Leisure Insights. - Start in
Searches Dashboardto validate the market story before switching toMap VieworPredictive Demand. - Export charts or map outputs when you need a shareable snapshot for reporting.
Note: DemandView caches data as cities are loaded. Once a city has been queried, it can be reused in comparison and map views without another manual setup step.
Filters
Understand the Control Panel
The filter rail defines the analytical context for every chart and table. Choosing the right combination of city, trip type, time period, and traveler segment is the key to reading DemandView correctly.
Left-side controls
Origin City
Search by city name or code. When selected alone, all charts focus on outbound demand from that origin.
Destination City
Search by city name or code. When selected alone, all charts focus on inbound demand toward that destination.
Trip Type
Use All, O for one-way, or R for roundtrip to isolate search behavior by itinerary type.
Sales Week
Filter by all data, a specific year, a quarter, or an individual weekly snapshot. This affects trend lines, tables, map totals, and exports.
Business and Leisure Insights
Switch between total demand and segmented views for Business, Long Stay Leisure, or Weekend Leisure.
Predictive Controls
When the Predictive tab is active, the uplift slider and event filter modify the projected forecast and event capacity table.
Searches Dashboard
Core Analytical Workspace
This is the primary dashboard for validating market scale, seasonality, and directional movement. It combines summary metrics, market ranking, and three supporting chart types.
Default landing view
- Stats cards: Surface the high-level market read for the current selection and insight segment.
- Top 50 markets table: Ranks destination or origin markets depending on your selection context.
- Total Weekly Searches: Shows weekly trend lines by year so you can compare current and historical demand patterns.
- Multi-Airport Comparison: Uses cached city selections to compare search volume across loaded airports.
- Peak vs Off-Peak Pattern: Indexes demand to a baseline of 100 to show seasonal peaks and troughs more clearly.
- Advance Purchase Classification: Buckets demand by AP windows such as
0-6,7-13,21-59, and180+.
Interpretation tip: Use the trend chart to find changes in absolute volume and the peak/off-peak chart to understand whether the market is structurally seasonal or only temporarily elevated.
Map View
Visualize Geographic Search Demand
The map converts cached demand into proportional circles by city, making it easier to see where search activity is concentrated. This view is most useful after you have loaded more than one airport or market.
Leaflet demand map
- Circle size is scaled to the combined origin and destination demand currently active under the selected filters.
- Popups show city name, airport code, origin searches, destination searches, and total searches when both directions exist.
- The map automatically centers on the currently selected city when possible.
- The supporting market comparison chart shows directional O&D relationships across all loaded cities.
Best practice: Load several relevant airports before using the map. The geographic layer becomes much more informative when multiple cities are already cached in the session.
Predictive Demand
Build a Lightweight Forecast Narrative
The predictive view turns historical weekly searches into a forward-looking demand estimate. It is not a full forecasting engine; it is a fast scenario layer for communicating likely uplift and event pressure.
Scenario-based forecast
Revenue Manager Uplift
Adjust the manual uplift percentage to represent expected commercial upside beyond the selected historical baseline.
Event Focus
Filter forecast output to event windows such as Spring Break, FIFA, Independence Day, or Christmas.
Passenger Demand Forecasts
The main forecast chart contrasts the historical baseline with future projections and supports click-based point inspection.
Event-Based Forecast Table
Highlights elevated growth weeks, historical demand, forecast demand, and the recommended operational action.
Important: The current predictive model uses a rules-based baseline and fixed event uplift logic. Treat it as decision-support context, not as a production-grade forecasting model.
Admin Workspace
Operational and Platform Signals
The admin tab is currently a management-style workspace that presents product health, account activity, and customer usage examples rather than a live transactional admin console.
Platform overview
- Shows sample usage metrics such as active users, recent API volume, storage usage, and system health.
- Includes placeholders for user management, system logs, and audit export actions.
- Presents customer usage directory and featured customer focus cards for account monitoring narratives.
Data & Metrics
How the Underlying Data Is Interpreted
DemandView normalizes weekly records into a common structure for origin, destination, trip type, AP bucket, and traveler segment. Most visualizations are aggregated weekly before display.
Historical weekly demand
- Sales Week: An integer date field used as the weekly time anchor for trends and quarterly grouping.
- Origin / Destination city code: Airport city identifiers used to group and compare markets.
- Searches Out / Searches In: Directional demand measures used differently depending on the selection mode.
- Traveler segments: Business, long-stay leisure, and weekend leisure are available in outbound and inbound variants.
- AP buckets: Search demand is categorized into advance purchase windows for planning lead-time analysis.
Mode logic matters: In O&D market mode the dashboard emphasizes
searches_out for the chosen origin-to-destination pair. In destination-only mode it relies on searches_in to represent inbound demand.Exports
Create Shareable Snapshots
DemandView supports PDF export for charts and the map view. Exports include the current selection label and generation timestamp, which helps preserve analytical context when sharing outputs.
PDF output
- Each chart card includes a
Downloadbutton when data exists for that visualization. - Chart exports include the chart image and a tabular breakdown of the plotted values.
- Map export captures the visible map plus a city summary table of total searches.
- Exports use the active filters at the time the PDF is created.
FAQ
Common Questions
These answers are tailored to the current DemandView 2.0 implementation and how the page behaves in-browser today.
Quick answers
Why is the page empty when I first open it?
The dashboard waits for airport metadata and user selections. Until an origin or destination is chosen, the main analytical cards and charts have no demand context to render.
What happens if I select the same city for origin and destination?
The app switches into a combined-city view and adds outbound and inbound demand together for that city. This is useful when you want a broader demand picture around a single airport market.
Does DemandView forecast actual passengers?
Not directly. The predictive layer starts from search demand and applies a fixed search-to-passenger ratio in its summary cards. It should be treated as a directional scenario aid rather than a validated passenger forecast system.
Why do comparison charts improve after I load more cities?
Several views rely on cached city data from the current session. The more airports you load, the richer the multi-airport and map-market comparisons become.
Can I use business and leisure segmentation across all views?
Yes. The Business and Leisure Insights selector changes how the app reads directional demand values, and that selection flows through the main charts, table, map, and predictive outputs.