sensebox / opensensemap-api Goto Github PK

@SpeckiJ on sensebox/openSenseMap#105:

The official Filter Function located in the "Filter Submenu" does not work given a Time Interval.

Steps to Reproduce the Issue:
1. Select Random Interval in Filter-Function on the official OpenSenseMap Site
2. apply Filter
3. Wait :)

After a considerable amount of Time the GET-Request fails and responds with HTTP Response Code 502.
There is **no** visual Feedback (besides inside the console log) indicating that the Request has failed. In the UI the User is still shown the loading Message of "Bitte warten, die Daten werden geladen...", albeit no Data being loaded anymore after the initial GET Request failed.

The Process can only be stopped by reloading the Site as the "reset Filter" Button is greyed out while a filter is being applied.

--------------------------------------------------------------------------------------------------------------
Auf der openSenseMap im Untermenü "Filter" funktioniert das filtern unter Angabe eines Zeitraumes nicht. 

Schritte zum Reproduzieren:

1. In der Filter Funktion der OpenSenseMap einen Zeitraum angeben
2. "Filter anwenden" drücken
3. Warten :)

Nach erheblicher (!) Wartezeit antwortet die API mit einem Http Response Code 502 und der GET-Request schlägt fehlt.
Es gibt **kein** visuelles Feedback (ausserhalb der Konsole) das anzeigt das der Request abgelehnt wurde und dem Nutzer wird weiter "Bitte warten, die Daten werden geladen..." angezeigt, obwohl keine Daten mehr geladen werden.
Der Prozess kann nur durch ein komplettes Neuladen der Seite gestoppt werden, da der "Filter zurücksetzen"-Button ausgegraut ist während gerade ein Filter angewendet wird.

sensebox/openSenseMap#146

@noerw Please write a migration on database to make sure mqtt works after the development branch is rolled out in production.

Es wäre toll wenn die API GeoJson kompatibel wäre, so das man die Box(en) direkt in in GIS oder Webapp stecken könnte.

As a phenomenon may be measured in different units, the sensors unit of measurement should be included in the CSV download (/boxes/data?...) to allow proper data evaluation

some route accept a bbox parameter. It should be checked if its an valid bounding box for wgs84

Currently, we can configure the location of a senseBox.

Having information about the height over sea level would be very useful in statistical analysis of pressure, temperature and lighting data.

If a box has no height information, or the user does not want to find and provide any information, a checkbox in the GUI could tell the API to use the height from openDEM ( http://opendem.info/download_srtm.html ). For the already existing boxes, this checkbox should be initialized to "true" so all boxes immediately have valid height information.

Also, this information should be returned in the "loc" item of the API call.

Someone just pointed out to me that every 13 minutes we have a gap in nearly every series.

I'll investigate!

• The problem seems to be the call /boxes/:boxId/data/:sensorId
• In the date parsing

632bec6#diff-0364f57fbff2fabbe941ed20c328ef1aR15

this causes the database host variable from the config to be ignored

List all available routes under https://api.opensensemap.org/ and add verison number (commit sha)

Let users configure webhooks for several conditions like value of sensor x is above n

currently the user recieves { code: 422, message: 'validation failed' }on invalid requests to PUT /boxes.

it would be helpful to return the actual specific validation requirement, which is provided by mongoose

check parameters before feeding them to mongodb..!

If you delete a senseBox over the api and send the request a second time the response is "Box deleted" but it should be instead NotFoundError

The registering user should be notified via email if their sensebox transmits unlikely data:

• very high or very low values
  • e.g. <-20 or >45°C temperature
  • possibly region depending
  • possibly season depending
• constant values for days
  • e.g. 100% humidity
  • good threshold IMO: three days?
• no transmission for days
  • i.e. when the status changes to inactive
  • or even earlier (again three days?)

That could help discover (and respond to) issues with ones sensebox earlier - when the two senseboxes I'm operating have issues I usually don't notice that for days or weeks as I don't manually check the OSeM very often.

Unify response message format to:

{
    code: "", // e.g. NotAuthorized or NotFound (restify errors) , Ok or Created for 2xx responses!
    message: "" // e.g. ApiKey valid or box data
}

Please add timestamps as extra attribute to interpolation response

{
    data: {
        breaks: [],
        featureCollection: {},
        timestamps: [] // new attribute
    }
}

lib/models/box.js:293:in then

It would be good if we add the old senseBox:basic template in the osem again. A lot of users have the old setup and would like to setup up the box without adding all sensors manually and edit the code.

When opening the archieve for https://opensensemap.org/explore/5710de1a45fd40c8198ccece, no archive can be found (404). Maybe due to the letter ü in the senseBox name?

send a mail to [email protected] with the URL of the new sensebox.

When setting up a manually configured sense box with more than one temperature sensor, both sensors are assigned the same name (TEMPSENSOR_ID) in the mailed sensebox.ino file. Numbering (for example TEMPSENSOR2_ID) would be desirable.

Also, (at least) humidity and light (digital) sensors are named SENSOR1_ID (here numbering works) with their phenomenon only mentioned in a comment. Naming as done with temperature sensors would be desirable.

Specifying a power of 9 through the power parameter yields an error:
{"code":"BadRequestError","message":"parameter power must be between 1 and 9"}

I just discovered that my box stopped working at 02:44 this morning due to a failing data transmission to the sensebox API. After restarting it's still the same. I checked several other boxes, they too don't have any data since last night, so the error must be on the API side.

It appears that measurement object's sensor_id property is wrong, at least in newer measurements.

How to reproduce:

Query some recent data

db.measurements.find({
    createdAt: { 
            $gt: ISODate("2016-02-13 12:00:00.000Z"),
            $lt: ISODate("2016-02-13 13:30:00.000Z") 
    }
})

Copy the "sensor_id" and query sensors:

db.sensors.find({
    _id: ObjectId("stuff") 
})

No results on new measurement sensor_ids. Works fine on old measurements.sensor_ids.

Hi,

is it possible to integrate a moveable SenseBox? For a example a SenseBox which is mounted on a bicycle? At the moment every SenseBox is fixed to one location and the measurements don't store an individual location.

Kind regards,
Marius

including apikey in mail would be great

For example for

• boxes
• measurements of boxes
• last measurements of single boxes

(RSS, atom)

There are some devices unable to speak tls

check the referenced issue: sensebox/OER#17

Add a new parameter exposure to /boxes to filter for indoor or outdoor boxes

Nice project!
What do you think about an real time API (WebSocket)?
For example: A client opens a WebSocket connection and tells the server on which sensor it (the client) pays attention on. If the sensor pushes data, the API server looks, if there is a client which is paying attention on this event and if yes, the client(s) is/are receiving the change.
I don't know if you consider this as a good or just complicated feature.

Also for #49

This would allow to use both box and sensor ids and slugified names in urls

Possible package: https://github.com/pid/speakingurl

In combination with gzip frontend stuff (sensebox/openSenseMap#148) also gzip api responses if possible

"Yeah, a new senseBox has been registered on openSenseMap! Check it out: URL"

or at least, send us an email

it should allow to:

• delete all measurements of a sensor
• delete one measurement of a sensor specified by timestamp
• delete measurements between two timestamps of a sensor

related to sensebox/openSenseMap#85

Let users submit their values as csv like

sensorID,value(,createdAt)
.....