What the data for this category looks like
Data sources for aviation airport revenue yield data include publicly available civil aviation industry APIs and internal settlement data from airport operation management systems. Data is compiled and generated once daily in the early morning, covering full operational data from the previous day. Data is structured as JSON, including fields such as airport three-character code, daily takeoff and landing sorties, passenger throughput, landing fee revenue, non-aeronautical business revenue, average revenue per sortie, and revenue per passenger. Field units are as follows: takeoff and landing sorties are measured in sorties, passenger throughput is measured in passenger trips, revenue-related fields are measured in CNY yuan, and unit revenue-related fields are measured in yuan per sortie or yuan per passenger.
Constraints imposed on HTTP interfaces and external systems
Data comes from two categories: civil aviation public APIs and internal airport systems. External systems must support multi-source data pulling and merged validation to prevent broadcast interruptions caused by single data source failure. Full data is updated only once per day. HTTP API polling intervals must align with the data update schedule. Polling intervals shorter than 24 hours are not recommended, as they may trigger rate limiting rules from third-party APIs. Fields include numerical content with specified units. API request and return field validation rules must be strictly bound to preset field names and units to avoid revenue yield calculation deviations caused by unit conversion. Non-aeronautical revenue data for some remote airports may experience collection delays. External systems must support empty field scenarios to prevent API call failures caused by missing fields.
How to configure settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
external_api_poll_interval | 86400 seconds | Matches the daily update schedule of aviation airport revenue yield data, avoids repeated requests triggering third-party API rate limits |
external_api_source_mode | Dual-source pulling | Connects to both civil aviation public statistics APIs and airport internal operation systems, ensuring valid data can be obtained even if one data source fails |
field_unit_validation | Enabled | Validates that units of fields returned by APIs match preset rules, avoids revenue yield calculation deviations caused by unit conversion |
empty_field_policy | Retain empty values and mark | Compensates for collection delays of non-aeronautical revenue data in remote airports, avoids broadcast errors caused by forced field filling |
request_timeout | 300 seconds | Adapts to the data compilation time of airport internal systems, prevents data pulling processes from being interrupted by request timeouts |
rate_limit_quota | 12 requests per day | Matches official call frequency limits for civil aviation public APIs, prevents API ban |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by data format, data volume and business rules. Specific issues require individual analysis, and it is recommended to test on your own samples before finalizing settings.
Three common configuration mistakes
- Symptom: API returns status code 429, and logs show request frequency exceeded limit. Cause: Did not match the call frequency limit of civil aviation public APIs, set a polling interval shorter than 24 hours.
- Symptom: Unit format confusion appears in unit revenue fields in broadcast content. Cause: Did not enable field unit validation configuration, and arbitrarily converted the unit format returned by the API.
- Symptom: Revenue yield data for some remote airports is empty, causing HTTP API call failure. Cause: Did not configure empty field compatibility policy, forced requirement for all fields to be non-empty led to validation failure.
How to confirm configuration is complete
- Initiate a simulated request, verify that the API returned fields include the preset airport code, takeoff and landing sorties, revenue-related fields, and that units match preset rules.
- Review external system call logs, confirm that request frequency does not exceed the configured rate limit threshold, and that polling intervals follow the daily update requirement.
- Simulate API responses with empty fields, check that the system processes them per the configured policy, with no call failures or incorrect broadcasts.
- Switch to a single data source for testing, confirm that the system can successfully pull data from the backup data source when one data source fails.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.