Attached Network Error appears nearly daily.

How/where to report this to fix?

please test all browsers:

Chrome will work
Firefox will work
Safari - you can see no sensors, map will be seen
Windows Internet Explorer - not tested

Hi All

Could IE11 Support be added?

Lodash, Leaflet, D3, Vue and whatwg-fetch supports IE11 but a Promise Polyfill is missing:

SCRIPT5009: "Promise" ist undefiniert
Datei: vendor.f97452c07040b3f93115.js, Zeile: 14, Spalte: 24183

IE11 is still a common browser and is used by a lot of governments/administration officies

Hi,
I would like to push my measurements to other services e.g. temperature and humidity to wunderground.com
Is that possible?

Auf der Karte nur die SDS011
Und Temperatur und Feuchtigkeit gleichzeitig anzeigen lassen

Hi rashfael,
I've written a small "extension" to select a city as start focus. Code:
Old:
function(t,e){"use strict";t.exports={center:[48.7791878,9.107176]}}

New:

function(t,e){
        "use strict";
        var locationstring = String(window.location);
        if (locationstring.indexOf("?") > 0) {
                var town = decodeURIComponent(locationstring.substring(locationstring.indexOf("?")+1));
        } 
        var towns = new Array();
        towns["Stuttgart"] = [48.7791878,9.107176];
        towns["Augsburg"] = [48.3585423,10.8943915];
        towns["Berlin"] = [52.5093007,13.4398506];
        towns["Hamburg"] = [53.5464148,9.984099];
        towns["Konstanz"] = [47.7068168,9.1338518];
        towns["München"] = [48.1541385,11.5411414];
        towns["Münster"] = [51.9502139,7.591131];
        towns["Ulm"] = [48.3843119,9.949304];

        if (typeof town !== 'undefined') {
                if (Array.isArray(towns[town])) {
                        t.exports={center:towns[town]}
                } else {
                        t.exports={center:towns["Stuttgart"]}
                }
        } else {
                t.exports={center:towns["Stuttgart"]}
        }
}

Example: Hamburg

Vue is running in development mode on the web site:

You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html

I can see the map, but when I click on the (+) the graphic does not load.
It doese not work on Opera and Firefox.

Aufgrund der mir bisher bekannten Informationen war ich der Annahme, dass der SDS011 für PM2.5 recht zuverlässige Werte im Vergleich zu Profigeräten liefert.

Bei der aktuellen Wetterlage in Nordwestdeutschland (Regen, hohe Luftfeuchtigkeit) sieht es allerdings so aus, als ob auch die Werte für PM2.5 zu hoch sind.

Hier ein Screenshot von heute, 19. September, ca. 09:10 Uhr:

In den Kommentaren zu http://luftdaten.info/2017/06/30/lubw-bericht-zum-feinstaubsensor/ gibt es einige Links auf weitere Studien.

Ich versuche einen Überblick zu bekommen, welche der erhobenen Daten für eine Interpretation/Auswertung geeignet sind.

Hierzu wäre es hilfreich, irgendwo einen Bereich zu haben, in dem alle Erkenntnisse und Studien zur Genauigkeit/Verlässlichkeit der Sensordaten verfügbar sind.

Perhaps i am missing a point, but for the moment, just SDS are visible in
https://api.luftdaten.info/static/v2/data.dust.min.json

consequence: PMS sensordate are not shown on the map.

Code in src/feinstaub-api.js is changed, please deploy new version

Unfortunately it is not possible to enter WiFi passwords with more than 32 characters in the config form provided with the latest firmware binary:

https://github.com/opendata-stuttgart/sensors-software/blob/master/esp8266-arduino/ppd42ns-wificonfig-ppd-sds-dht/ppd42ns-wificonfig-ppd-sds-dht.ino.nodemcu.bin

maxlength= "32"

<input name="wlanpwd" id="wlanpwd" placeholder="Passwort" value="IWouldLikeToEnterALongPasswordHe" maxlength="32" type="password">

michael kreil has changed the css for the osm tiles. looks good. you can see the changes on https://michaelkreil.github.io/feinstaub-map/ .
So we can get rid of all those color in higher zoom levels ;-)

Hi there,

since the aggregated hexagons with mean and the hexagons for a single sensor look alike, some users seem to make wrong assumption about the values in a certrain area. IMO a different kind of visualization for these two types would increase usability a lot. Yet I don't know how to solve this, but I wanted to leave this here for discussion.

Edit: This especially applies to mobile users, because they do not see the sidebar panel immediately.

Cheerio

Hi,

i wonder, if someone could get in contact with other map providers, for example, start with wunderground.com, to include thos datasources in their map. This whould not only bring forward the use of public bigdata it whould also bring a bigger impact on the world.

Another interesting idea, maybe we can see a correlation betwen weather changes and the feinstaub measurements.

Example: Sensor 3149, today, 16.6.2017.
second chart, "Last 24 hours"

The last values where between 0 and 15 µg.
But one PM10 value was more than 2k. Doesn't matter, messure was wrong.
BUT: The Chart "last 24 hours" uses this wrong 2k value for max. So the normal values between 0 and 15
Aren't displayed well because of one wrong value.

The goal should be to determine such wrong values and perhaps cut them to display the correct
values correctly.

• Now there is one red limit at 50 μg/m³.
• an additional WHO limit at 20 μg/m³ (green) could be useful as "goal".

how to introduce, e.g.:
rename 50 μg limit, add limit-who in
src/legend.vue

Right now the api returns a 502.
Handle any api errors and show a big message instead of an empty map.

We currently do not set any headers when requesting from the api.
This seems to result in differing behaviour in different browsers.
Chrome sends accept header "/", Firefox sends "text/html..."

Fix: Explicitly set accept headers to application/json

Aus P1 = PM10
Aus P2 = PM2,5

I have problems to install the map on windows 10.
After npm install I get the error message:
npm WARN [email protected] requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of webpack@^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.

This is what I tried to install:
instaledl Git
installed Phyton v 3.6
istalled Django frameset
installed node.js v 8
start Powerschell as administrator and execute:
npm install -g --production windows-build-tools

start normal shell and execute
npm install
npm audit fix --force
npm install
copy config.js.dist config.js
npm start
start browser with http://localhost:8880/

map is not loading js error in d3

With Open Suse linux i have done without problems:
installed npm v8
installed gcc-c++
execute from shell:
npm install
npm start
start browser with http://localhost:8880/

map is loading

Have anybody installed the map with windows 10? Did I forget something?

please change file src/feinstaub-api.js:
line 19: - sensor.sensordatavalues.length == 6
line 19: + (sensor.sensordatavalues.length == 6 || sensor.sensordatavalues.length == 9)

thx, Rajko

Call of sensor-Map via specific city url leads gets corrects location from places.js
but uses zoomlevel #2.

example:
passau.maps.luftdaten.info
leads to
http://passau.maps.luftdaten.info/#2/48.6/13.2
showing whole earth.

Stuttgart:
http://stuttgart.maps.luftdaten.info leads to:
http://stuttgart.maps.luftdaten.info/#2/48.8/9.2

Deutschland works:
http://deutschland.maps.luftdaten.info leads to:
http://deutschland.maps.luftdaten.info/#6/51.165/10.455

Baden-Württemberg works also.
http://baden-wuerttemberg.maps.luftdaten.info/ leads to
http://baden-wuerttemberg.maps.luftdaten.info/#8/48.530/9.050

seems, only citys are affected.
Checked with Chrome 58 and Firefox 54 on Windows 10

I can't see the map as all request to mapbox made by the website return a "401 Unauthorized".

Right now, it is afaik impossible to link to a specific location on the map and/or a specific tile.

would also contribute the change if you prefer.

I would like to implement some changes for this map: https://www.madavi.de/sensor/feinstaub-map-dht/
But I was unable to find the sources somewhere.

Can you tell me if contribution is possible?

Es scheint, das Schreiben als CSV-Dateien in eine Datei scheint derzeit mit der gestiegenen Anzahl von Sensoren und daraus resultierenden Datenmengen auf dem Server an die Grenze zu kommen.
Wäre es nicht sinnvoller, die Datenmengen in eine Datenbank zu schreiben und auf die dort vorhanden Sicherheits- und Backup-Mechanismen zu nutzen?
Auf Anforderung könnte auch die Ausgabe spezifischer Sensordaten als CSV-Datei immer noch erfolgen.
Man könnte mit einer entsprechenden API auch schneller/einfacher regionale Zusammenfassungen und Analysen machen. (Select * from Data where sensor in "sensor1, sensor4, sensor 16" )
Die querys wären aufgrund der Datenstruktur wohl recht einfach.
Inserts und Selects. Wohl keine Updates und keine joins. Da ist nix komplexes dabei.
Die Anzahl der Einträge ist zwar schnell ansteigend, aber konstant und ließe sich wohl gut voraussagen.
Abfragen könnte auf eine gespiegelte DB laufen zur Lastverteilung.

Hi,
Opensensmap.org accepts light sensors like the TSL45315 and UV sensors like the VEML6070.
Both connect via i2c.
I would like to submit theese data as well.
Would it be possible to add the function in the firmware?
I've ordered a bmp180 already to submit the barometric pressure to Opensensemap as well.

matthias said we shouldn't use the openstreetmap tile servers directly. I've set up a caching proxy for this. By now you can reach those proxy with (https://){a,b,c}.tiles.madavi.de. Tis will change later to {a,b,c}.tiles.luftdaten.info.
Could you test those proxy and change the the map to this, if everything is okay?

Hallo, seit einigen Stunden liefert dieser Aufruf https://api.luftdaten.info/v1/filter/type=SDS011&area=48.323368,14.298756,50 nicht mehr die gewünschten Daten.
Es sieht so aus als ob alle Daten ausgespuckt werden.
Was mache ich falsch?
Kann ich mir Hilfe erwarten?
Tolles Projekt, vielen Dank.

Liebe Grüße
Stefan

Hy, i have a sensor that is not on the map. I'd like to compare the madavi graphs woth sensors on the map. Is there a way to obtain their id off the map?
Thx

Seit vorhin.
Heut Mittag gings noch
Android 7, chrome, via Unitymedia.

Provide way to connect sensor via LoRaWan
Document how to do this

should be in English as well

In the current graph plots

it's next to impossible to distinguish between the individual days. It'd be great to have grid lines at 12am every day. This makes it easier to tell if the daily average is smaller or larger than the legal limit of 50 µg/m^3.

Touch devices can't see the individual values of a cell, enable touch events.
Render the value panel responsive (full screen with X perhaps).

As suggested by @Marwe

Use https://www.madavi.de/sensor/feinstaub-map-sds/data.json as api url.

BLOCKER

CORS header is not set.
Can somebody set the HTTP header to

Access-Control-Allow-Origin: *

Links to the map are generally given in terms of geo-coordinates. I would like to get a link to the individual sensor installed at my house, ideally with popped up graphs. This would make it easier to share the info with the other tenants.

Hi guys,
As I wrote in the title, I was wondering why, after about a month, I still do not find my sensor on the luftdaten map. I also sent some emails, but I have not received an answer. I care because I would like to share with my fellow citizens what was detected by the control unit in a very difficult area.
Thank you

Currently the color range spans dynamically from 0(green) to the highest value(red).
This leads to most of the cells showing green, even if they are over the threshold, when some sensor reports weird, high values.

How to fix it:

• Define a hard color range with proper thresholds.
• Don't use the data from the PPD42NS sensors for the color range, because they are not reliable.

I'd be happy to implement this, somebody just needs to tell me some thresholds (Grenzwerte) for the data from SDS011. I can then also add a useful legend.

My fine dust sensor did pick up almost no particles during the last days see.
Today I got suspicious. I opened the case and checked. All o.k.
I re cabled. No change - Values around 0 µg/m³.

Only when I removed the tube the values got to 10 µg/m³.
Inspecting the tube I found this BUG ;)

Even after rinsing the BUG out almost no water passed though the tube. I had to physically remove the web created by the BUG. It seems to me the web was filtering out almost all fine dust particles.

Now the serious part. Is there any way you can alert the owner of a sensor producing unfeasible values. Maybe you could display a warning sign and disregard the reading.

... needless to say this bug has no high priority anymore

Auf der neuen Webseite (Sensorwerte-Map) gibt es den Erklärungstext, und der verwendet zweimal das Wort "offiziellen [Werte/n]"

Bitte um Erklärung bzw. Korrektur.

showing trend of

• specific sensor

• sensor with same region (e.g. Stuttgart, Baden-Württemberg, NRW, Germany)

• all sensors

What is needed to get this started?

I tried a fresh debian/jessie and node.js but got awful lot of dependecies... Gave up tonight after hours.

We'd like to host our own map centered on Bielefeld using your data.

Cheers,

Ralf.

Add a graph visualizing pollution over time, both for all sensors and, if a cell is selected, for a single cell.
Allow selection of the time slice for the map via this graph.
Offer an autoplay function to animate the changes over time in a loop.

Possible Visualizations: Line, Bar, Calendar Heatmaps.

Bonus Feature for later: Live-Update.

Open Questions:

• What's the data source for historical data?
• How many points in time do we want to display / what resolution?
• How far back do we want to go?

Hi! Is luftdaten.info only about the crowdsourced sensors or do you want to track official sensors as well? There is another sensor map by @maltehuebner based on state-run sensors, so maybe you could cooperate here?

kann man es einrichten, dass ich auf die Sensor Nummer klicke und dann die Daten entweder als CSV Datei oder die Grafiken bekomme?
Vielleicht auch noch die Einträge zur Umgebebung?
Das wäre sehr hilfreich

Hello,
when I go over the map with the mouse and want to see values of different sensors, sometimes the column on the right is not being updated (e.g. the PM-alues shown do not match with the color on the map).

Thx for advising
Y

In the EU, PM10 particles can legally take a concentration of more than 50µg/m^3 on average per day at most 35 day per year. It'd be great if the details popup could show just how many times this threshold was violated in the last 365 days.