Best use for travel intelligence
For travel decisions, noise-barrier layers help explain why one side of a road, rail line, or airport corridor can feel much quieter than another.
Data cluster
Barrier geometry and source-proxy layers that help explain where noise shielding exists and where it does not.
For travel decisions, noise-barrier layers help explain why one side of a road, rail line, or airport corridor can feel much quieter than another.
0 of 3 sources look official or agency-backed.
3 sources expose API, feed, CKAN/DataStore, JSON, XML, or similar machine-readable access.
0 sources have live, hourly, event-driven, warning, or frequent update language.
Treat barriers as geometry and source-mitigation context only; they should modify confidence and modeled risk, not masquerade as direct measurements.
Last checked: 2026-05-11.
Source confidence: This cluster is strongest when several sources describe the same traveler problem from different angles: official context, machine-readable feeds, and slower fallback documentation.
Geospatial noise-mitigation and modeling layer for wall=noise_barrier and related barrier geometry near roads, rail lines, airports, and settlements.
OpenStreetMap Overpass API and ODbL geospatial data Geospatial and satelliteGeospatial enrichment for man_made=monitoring_station with monitoring:noise tagging, useful for mapping public or private noise-monitoring locations and nearby source context.
OpenStreetMap Overpass API and ODbL geospatial data TransportAirports of Thailand public environmental-management page describing environmental governance across all 6 AOT airports plus public complaint and community-contact context for airport-noise and related environmental impacts. Useful as reference and disclosure context, but direct automated fetch behavior can vary and it should not be treated as a stable live measurement feed.
Public sustainability and environmental reporting page