PM2.5 aggregates, averaging periods and comparison limits

MapScale currently exposes published PCD area-level PM2.5 aggregates for the Bangkok metropolitan region. Compare a value with a standard only after matching pollutant, unit and averaging period. These aggregates are not current station readings or personal exposure estimates.

Procedure

  1. Read the source reference period and spatial aggregation before extracting a value.
  2. Record pollutant, unit, averaging period and the official standard source; leave unknown fields empty.
  3. Compare only compatible measurements, and obtain current official readings for time-sensitive decisions.

Interpretation checks

Input or conditionHow to interpret it
Annual vs short-termA yearly aggregate cannot be compared as if it were a daily reading.
Area vs stationSpatial aggregation masks variation within the area.
Unknown unit or periodStop the threshold comparison and consult the source definition.

Illustrative working example

Code illustrates a review procedure, not an observed result. Replace illustrative inputs with verified records; missing values deliberately remain unknown.

comparison = {
    "pollutant": "PM2.5", "unit": "micrograms/m3",
    "averaging_period": None, "reference_period": None,
    "threshold_source": None
}
# Do not compare until all periods and the standard are known.

Bounded API request

Read-only public request, limited to 100 features. Check HTTP status, freshness and pagination before interpreting the result. Foundation layers use their dedicated APIs; this is not a bulk database export.

curl --fail 'https://api.mapscale.io/v1/public/atlas/layers/air-quality?bbox=100.4%2C13.6%2C100.9%2C14.1&limit=100'

Useful output and decision limits

A documented comparability check, rather than an unsupported pass/fail badge. It does not give health advice or certify regulatory compliance.

Datasets, coverage and source contracts

Related customer workflows