It would be really useful if you could click on a download link for a specific sensor on the map and specify the start and end date and simply download the historic data. PurpleAir have this function and it makes it really easy to look at historic data.
I dont want to mess around with scripts, make it simple and people will use it.
Keep up the good work!
kind regards
Peter
Hi,
Can you post a picture of the button. I can’t find it.
Won’t such function overload our servers ?
We provide a button to show the curves on the map and a Grafana Dashboard were you can see a lot of information (and also download csv)
For example:
https://maps.sensor.community/grafana/d/000000004/single-sensor-view-for-map?orgId=1&var-node=ID
And this lin with the board ID:
https://api-rrd.madavi.de/grafana/d/GUaL5aZMz/pm-sensors?orgId=1&var-chipID=esp8266-ID
You can download from there and also in the archives.
Hi,
Download button bottom right of screen.
Then you choose dates and frequency etc and download data from A or B sensor as PurpleAir have two sensors for resilience. Its an easy to use solution and very neat.
Have a good weekend!
kind regards
Peter
Download button is the arrow pointing down . . . not easy to see.
OK now I see.
Of course people can argue than PurpleAir is neat, easy, better… But why does it cost 279 $ ? The PMS7003 cost 10 $ each…
Where is the source code of the map, the firmware… ?
What are the accomplishments of PurpleAir ?
Do the support answer as fast as I do on the forum, the Gihub etc. ?
Do they organize weekly call to build a community ?
Do PurpleAir use its GitHb account : PurpleAir · GitHub ?
Do you work for the company ?
Hi,
Firstly, I do not work for the company PurpleAir but have researched air quality monitoring systems and came across PurpleAir. I will be building Luftdaten sensors and want to get local schools and councils involved with using Public data from low cost air quality monitors in the East of England and make people aware of their local air quality. But, the User interface needs to be simple and easy to use.
I am not criticizing the luftdaten solution please dont misunderstand me, I think its amazing what has been done to date. But we could make the User interface easier and less complicated to look at historic data and compare datasets.
I know we could use scripts to do stuff with FTP archives but school kids and adult users want a simple interface that’s easy and intuitive to use. Could we not have a download button for each sensor on the map that brings up a simple interface to enter start date, end date and download the data?
If there is no solution I will look to implement my own solution as I see others have done and pull the data down into a custom dashboard. I am not keen on this as I would prefer to see a solution with Luftdaten map for all sensors.
I will keep you advised on my efforts here in the East of England.
Have a good weekend!
kind regards
Peter
Would it be okay to not have the latest data (only those from the archive)?
Hi,
Certainly be better than what we have now to be able to download the last 24hrs data collected.
hi all
I’ve just updated this app because the old one was not working (and also to change Luftdaten for sensor.community)
[app}(Recupera y analiza datos de sensores Sensor.Community)
repo: Source en Gitlab: ShinyApp/CS_data_retrieval · master · Fernando Castro / MonitoreoAbierto · GitLab
saludos
I know I’m late to the party, but I’m hoping this information may help some.
I built my sensor box in a workshop, and part of that workshop was registering the box with 3 different platforms. This one (sensor.community - great forum, hi guys), a platform liaised with our national air quality institute, and with openSenseMap.org, which has a nice raw data download function.
I just downloaded my raw data over the last 3 months, 2 files PM10 & PM2.5 of a little over 5 MB each.
So no need to re-invent the wheel there.
@wired4net - you are here on Forum.Sensor.Community
Luftdaten.info was our local german project from 2016-2018.
→ Sensor.Community is the global open environmental data platform.
We have 2023 and now in the 5th year of Sensor.Community you should only refer to Sensor.Community.
