Catalog only
Geospatial and satellite
OSM noise monitoring stations.
Geospatial enrichment for man_made=monitoring_station with monitoring:noise tagging, useful for mapping public or private noise-monitoring locations and nearby source context.
Restricted
OpenStreetMap Overpass API and ODbL geospatial data
Free public with ODbL terms
Current community-edited data
2026-05-11
Exists and matters, but direct operational access is limited to authorized users or agencies.
page reference only
station ID, station type, area type, timestamp, LAeq 1h, LAeq 24h, Lmin, Lmax, L90, preliminary flag, complaint category, standard used, airport or road context, barrier geometry, confidence
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Catalog only
Not yet
No runtime entity scope yet.
No live observation ingestion yet.
Not wired into active decisions yet.
Profiled in the atlas and public pages, but not yet connected to live graph computation.
How this helps travel recommendations
Turns noise data into source-backed decisions about hotel quietness, roadside exposure, airport-neighborhood caution, nuisance-complaint routing, factory or construction risk, and how much confidence to place in a station versus a proxy.
Endpoint and API notes
Geospatial enrichment for man_made=monitoring_station with monitoring:noise tagging, useful for mapping public or private noise-monitoring locations and nearby source context.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use Noise4Thai and PCD CSV for ambient station truth, ECAP for complaint routing, CAAT and AOT materials for airport-noise context, DIW for factory measurement methods, Labour guidance for workplace exposure, and OSM only for noise barriers and source-proxy enrichment.
Refresh daily, or more often only when the source publishes explicit current-status fields.
Turns noise data into source-backed decisions about hotel quietness, roadside exposure, airport-neighborhood caution, nuisance-complaint routing, factory or construction risk, and how much confidence to place in a station versus a proxy.
PCD Noise4Thai, PCD CSV, ECAP, NSO, CAAT, AOT, DIW, Labour, OSM, and any project-specific airport or EIA reports that stay publicly accessible.
Example request
# Verify the documented noise endpoint before production use.
curl -L "https://overpass-turbo.eu/" -H "Accept: application/json"
Failure modes
- There is no complete national live noise map for Thailand.
- Ambient station readings do not prove a legal nuisance case by themselves.
- Daily noise data can be preliminary and should not be treated as litigation-grade evidence.
- Airport, factory, construction, nightlife, and workplace noise often live in reports, complaints, or private monitoring rather than public APIs.
- Station coverage is sparse relative to neighborhood-level hotel or condo decisions.
- Noise barriers and source proxies explain risk but are not measured dBA observations.
- Geospatial layers can be large, tiled, or projection-specific.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.