opendata-stuttgart / feinstaub-api Goto Github PK

Maybe I'm missing something, but from what I see, the permission to post data for a specific sensor node is solely based on its id? That could potentially be bad, as you can get ids that are activated pretty easily.

Hey!
Is there any official API documentation?

Right now API seems rather... unpleasant at best. Here are my thoughts:

• Add filtering to /api/v1/now/ (mostly by country code, maybe by lat/lon + average radius) - right now it takes about 2.5min to generate this view, maybe some caching would be a sensible option as well?
• Find a way of accessing related sensors (right now I am only able to find sensor ID of my SDS011 by looking at maps.luftdaten.info, but not the node ID, which would give me a look into both SDS011 and DHT22 values) - even returning node_id in /api/v1/sensor/.../ response would be enough

https://github.com/makinacorpus/django-geojson

Deliver pre aggregated sensor data by Uid/id.
...

• management command
• cronjob

Steps to reproduce (for example, from github.com):

jQuery.get("http://archive.luftdaten.info/2015-10-01/2015-10-01_ppd42ns_sensor_27.csv").then(function(response) { console.log("response", response); });
Object { state: .Deferred/r.state(), always: .Deferred/r.always(), then: .Deferred/r.then(), promise: .Deferred/r.promise(), pipe: .Deferred/r.then(), done: Q.Callbacks/f.add(), fail: Q.Callbacks/f.add(), progress: Q.Callbacks/f.add() }
Content Security Policy: The page's settings blocked the loading of a resource at http://archive.luftdaten.info/2015-10-01/2015-10-01_ppd42ns_sensor_27.csv ("connect-src https://github.com https://uploads.github.com https://status.github.com https://api.github.com https://www.google-analytics.com https://github-cloud.s3.amazonaws.com https://api.braintreegateway.com https://client-analytics.braintreegateway.com wss://live.github.com").

Albeit this is CSP, it would be handy to have a way to request the data via XHR (aka "Ajax").
Therefore CORS must be enabled. This way I could write a client-side only JavaScript application which pulls the data in. JSONP would be fine, too.

As far as I understood CSP you would need to declare a website which is allowed access to http://archive.luftdaten.info/2015-10-01/2015-10-01_ppd42ns_sensor_27.csv.

List list with the following infos for each sensor for displaying in the interactive map.
Format = json
Data:

• Uid/id
• lat/long (rounded to 3-4 decimals)
• sensor type
• description (optional)
• active/inactive flag
• last measurement timestamp

Hint: DB view

The api.sensor.community/v1/ is extremely slow and causes my integration on home assistant to fail (timeouts).

Can this be improved?

Hi Luftdaten project tema,

unfortunately the Home Assistant user agents are getting blocked 403 on the API.

It looks like the webserver is blocking specific HA version strings (0.84.3 through 0.84.6)

This is also surprising as the project is listing Home Assistant as an official client/plugin on https://luftdaten.info/faq/#toggle-id-8

Please also see the issue on the Home Assistant project home-assistant/core#19622

Do you experienced any issues with the Home Assistant plugin which need to be fixed?

Thanks

Maybe there are differences in small particles collected depending if the sensor is on the ground or mounted on the 5th floor.
If a sensor reports barometric pressure and has GPS data included, this could be used to calculate the elevation of the sensor.
BME180 provides "Up to 0.03hPa / 0.25m resolution", which seems to be good enough to do get that estimate.
Calculating it can be achieved using https://en.wikipedia.org/wiki/Barometric_formula assuming a constant temperature between reference and actual location and either the "standard" sea-level pressure and the GPS-based altitude or the data for the local (based on GPS) barometric pressure.

See also (german wikipedia) https://de.wikipedia.org/wiki/Barometrische_H%F6henmessung#Physikalischer_Hintergrund_der_barometrischen_Methode

Moin,
da ich dazu bisher keine Infos finden konnte: Wurden die timestamp-Einträge in den csv-Dateien auf archive.luftdaten.info auf MEZ-Werte geändert bzw. auf ihre entsprechenden Zeitzone korrigiert, oder sind diese wie die timestamps in den JSON-Uploads auf data.sensor.community im UTC-Format?
Betrachte ich die Werte für Silvester 19/20 als Referenz, sprechen die Höchstwerte meiner Sensoren um 00:00 Uhr für eine Korrektur auf MEZ, aber ich würde mich diesbezüglich gerne vergewissern.
Cheers!

For the 'Luchtdata project' in Arnhem (the Netherlands) we use the data from Madavi.de and archive.luftdaten.info for some analyzes.
Now we see a lot of gaps between measurements in the daily CSV dumps on http://archive.luftdaten.info/ and also on Madavi.de.

we see big gaps, for example on 8-2-2020 between aprox. 9 and 11:15 and on 12-10-2020 between 01:15 and 02:30 for all sensors. And then there are a lot of sensors with smaller (but more frequently) interruptions from 5 to 15 minuuts (or more). We thought the time between each measurement was/is approximately 145/150 seconds.

Is this a known issue and why so many interruptions between meassurements? This problem seems to be getting bigger the last days/weeks. Is this a database/server issue or maybe a sending problem of the sensors?

Alsow the monthly data from last January is missing, is this on his way?