Replies: 1 comment 1 reply
-
This question would be better asked in the SensorThings API GitHub project...
We also have a demo where each Thing has 5 Locations that are all the same location, but in different resulutions/levels of details: |
Beta Was this translation helpful? Give feedback.
-
Does anyone know why the SensorThings specification allows/requires multiple
Location
s for a givenThing
? The complication of having to get a specific entry from a collection of oneLocation
for anyThing
is currently getting in my way with the client library I'm using, but I'm also wondering why this arrangement makes sense logically.I would think even a very large
Thing
with very disparateSensor
s could always be described and recorded as having a single currentLocation
, or as being multipleThing
s if multipleLocation
s really made sense for it. Is there some design consideration I hadn't thought of?Beta Was this translation helpful? Give feedback.
All reactions