Best way to model handheld sensor #1935
-
|
Trying to understand the best way to model a handheld multiparameter sensor (used in water data collection - ph, nitrogen, ..). We have several HOBO water sensors/monitors at fixed locations that we collect data from - we augment this with data from a handheld monitor that we use to collect additional data at the same locations. I'd created a separate "Thing" and "Location" for each fixed monitor location - then "Sensor" for each of the types of sensors in the HOBO device (temperature, light), and then created "Datastreams" to tie them together. Since the handheld multiparameter swaps between the static locations - didn't know if the handheld sensor was best modeled as just multiple sensors tied to fixed "Things" and new "Sensors" and "Datastreams", or create a separate "Thing" with new "Sensors" and "Datastreams" but wasn't sure about tying it back to the same but multiple locations? If there's a better forum/place to ask/discuss let me know. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
General modelling questions are good to ask on the SensorThings GitHub What to model as the Thing in v1.1 is what you want to attach Datastreams to. In your use case, you probably want to have the time-series for your measurement locations, so those will have to be your things. If your device doesn't have and device-specific sensors, like for a battery-level, then you don't need to model the device as a Thing. |
Beta Was this translation helpful? Give feedback.
-
|
Ok can see that (tho still find a tad confusing) - like you suggested really want to have the time series attached to location so will handle that way. Our handheld has multiple sensors so will create one per sensor type. In future will post on SensorThings GitHub |
Beta Was this translation helpful? Give feedback.
-
|
Yes, in v1.1 the data model is not ideal for this use case. |
Beta Was this translation helpful? Give feedback.
General modelling questions are good to ask on the SensorThings GitHub
What to model as the Thing in v1.1 is what you want to attach Datastreams to. In your use case, you probably want to have the time-series for your measurement locations, so those will have to be your things.
You could then model your hand-held device as one or more Sensors, depending if you want to keep all details of the individual sub-sensors of the device separate, or if you can summarise them all in one Sensor entity.
If your device doesn't have and device-specific sensors, like for a battery-level, then you don't need to model the device as a Thing.