Difference between revisions of "CSM:Toolbox"
From its-wiki.no
Seraj.Fayyad (Talk | contribs) (→Supported Sensors) |
Seraj.Fayyad (Talk | contribs) (→Supported Sensors) |
||
Line 32: | Line 32: | ||
* LEO, http://citisense.ateknea.com/ | * LEO, http://citisense.ateknea.com/ | ||
− | {| ! ! ! | + | {| ! Sensor platform! link!Gases |
|- | | | | |- | | | | ||
|- | | | | |- | | | |
Revision as of 14:10, 5 February 2016
Toolbox | |||||
---|---|---|---|---|---|
|
The main goal of the toolbox developed in Citi-Sense-MOB is to provide guidance for the future, to include novel sensors for air quality monitoring. The toolbox addressed the following components
- server side management of sensor data
- user applicability, using apps
- widgets and code-snippets
The Citi-Sense-MOB toolbox
Server infrastructure
- GEOserver at NILU,
- WFS server
The server development has been in tight collaboration with the EU CITI-SENSE project
Inclusion of existing information
- Fixed stations
- Pollen information for
App development
Github repository of App code
https://github.com/unikdrift/air-quality-app
Supported Sensors
This section presents links to sensors platforms being used and tested in the Citi-Sense-MOB project:
- DunavNET, http://www.dunavnet.eu/
- UrVaMM Ingenieros Asesores, http://www.ingenierosasesores.com/index.php
- Cairpol, http://www.cairpol.com/index.php?lang=en
- AQMesh, http://www.aqmesh.com/
- LEO, http://citisense.ateknea.com/
Step-by-step procedure to add your sensor
The way on how to include a new sensor consists of the following steps
- 1. Buy a sensor, currently we support the sensors listed in #Supported Sensors
- 2. With your sensor you will receive a SensorID, e.g. xxxxxx (for Dunavnet sensor)
- 3. Send us your sensor idea through the #Register your sensor form
- 4. We will then get in contact with you to explain how the sensors can be integrated
Register your sensor
as soon as we have filled in the page, I will protect it such that we can test CSM_Sensor_Registration
Register your sensorEmailForm is only active on protected pages. |