Reference · built on requestCommons signalAir, water & environment

sensor.community

Particulate, temperature, and humidity readings from contributor-run sensors worldwide, as JSON updated every few minutes.

Request accessPricing ↗

About

sensor.community is a contributor-driven sensor network started by Open Data Stuttgart, formerly luftdaten.info. Volunteers build airRohr devices with an SDS011 particulate sensor and optional DHT22, BME280, or BMP180 sensors and post readings to api.sensor.community. Data for public sensors are served from data.sensor.community and exported to archive.sensor.community as CSV once a day.

An operator on Fibric reads the sensors within a radius of each site, takes the hourly average of PM10 and PM2.5, and treats the result as a neighbourhood signal beside your own monitors.

This is a reference listing. It documents what Fibric would read from sensor.community and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Last five minutes of readings for all sensors through static/v1/data.json
  • Sensors filtered by type, area (lat, lon, radius in km), box, or country through airrohr/v1/filter/{query}
  • One sensor's last five minutes through airrohr/v1/sensor/{apiID}/
  • Per-sensor averages over 5 minutes, 1 hour, and 24 hours through static/v2/data.json, data.1h.json, and data.24h.json
  • Dust-only and temperature-only slices through data.dust.min.json and data.temp.min.json
  • Daily CSV history per sensor at archive.sensor.community

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Sanity-check your own outdoor sensor

    Compare a rooftop PM2.5 monitor against the hourly average of community sensors nearby and flag drift when they diverge for a sustained period.

    With Sensor Health

  • Add a neighbourhood reading to a complaint

    When an occupant reports smoke or dust, pull the nearest sensors' last hour and include the values in the reply draft.

    With Comfort Complaint, Indoor Air

  • Notice a local spike early

    Watch the 5-minute dust feed within a few kilometres of each site and raise a notice when PM10 jumps against its 24-hour average.

    With Anomaly Notice

Requirements

  • A User-Agent string with contact details; required since 2022-11-04
  • Sensor API IDs (not chip IDs) or a location and radius for the filter endpoint
  • Reads against data.sensor.community, not api.sensor.community, which is for receiving data
Authentication
None. GET requests need no credentials, but every client must send a User-Agent header that lets the project contact you.

Limits

  • Readings come from volunteer devices; siting and sensor condition vary by contributor
  • Data are not immediate: last-minute endpoints refresh every minute, 24-hour endpoints every five minutes
  • No history endpoint; anything older than 24 hours comes from the daily CSV archive
  • Sensors near your site may be absent or go offline without notice

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request sensor.community ↗

Questions and answers

How current are the readings?
The project states that an endpoint covering the last minute updates every minute and an endpoint covering the last 24 hours updates every five minutes. The v1 data.json holds the last five minutes of measurements.
Is there a key or rate limit?
No key. The wiki requires a User-Agent header so the project can reach the source of excessive requests. Serve reads from data.sensor.community; api.sensor.community is for devices posting data.
Under what licence are the data?
sensor.community lists the Database Contents License (DbCL) 1.0 for its data, CC0 for photos, and GPL-3.0 for the firmware.
Ask about sensor.community

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by sensor.community / Open Data Stuttgart (data.sensor.community). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy