-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do we indicate the FoI being Observed by a Sensor? #253
Comments
What about using |
Especially when no observation is created yet ... => that's why we created ObservingCapability in OMS (actually in INSPIRE:EF and moving it to OMS)
the point raised by Kathi is that we see many Environmental Monitoring Use Case in Europe where you need to know more : the uFoI, the ObsProperty, the procedure etc... thus the ObservingCapability in OMS (https://docs.ogc.org/as/20-082r4/20-082r4.html#_observingcapability) |
Easy:
|
Proposed fix No new properties. Just supplementing the domainIncludes and rangeIncludes of existing properties hasFeatureOfInterest and isFeatureOfInterestOf |
Telecon discussion suggests that adding The link from a Sensor to a FoI is a deployment related issue. More helpful might be to add We need stronger examples/patterns of deployments to show how to do this. |
|
@dr-shorthair I totally agree that associating an FoI to a sensor is a deployment related issue. The association can also be created via an Observation, but it is often useful to also associate an FoI at the deployment level because very often some kind of FoI is known ahead of time (i.e. before any obs are produced). This is especially true for static in-situ sensors, but it can also be used to identify a larger FoI for mobile or remote sensors. For example, the sample/proximate FoI for a photo taken by a drone may be the exact image footprint (this would be associated to the observation), but often a less specific FoI can also be associated to the deployment (e.g. a specific area, building or other object such as a bridge, etc. that is of interest for a particular mission/deployment. This would often be the sampled feature / ultimate feature of interest, but it can also be a sample itself, e.g. a specific portion of a river that the drone is deployed over). So what you propose (adding |
2024-11-13 Telecon generally likes this approach, which expands domain of
@ldesousa notes that a |
Opens interesting options:
|
Proposed fix One new property, |
How do we indicate the FoI being Observed by a Sensor?
If we use an FoI-specific Property (PropertyOfInterest), we can state that the Sensor observes this PropertyOfInterest, that is in turn linked to the FoI.
However, if we use a neutral ObservableProperty, there is no direct way to indicate this link. The current workaround seems to be creating a specialization of Observation for this purpose. If this is a common use case, we may want to add this to SOSA, align with the ObservingCapability class from OMS
The text was updated successfully, but these errors were encountered: