You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This public comment is respectfully submitted by the Web Service Technical Panel (WSTP) of the Defence Geospatial Information Working Group (DGIWG). This comment is specifically directed toward 23-000 OGC SENSORML ENCODING STANDARD. Spatial transforms are in-scope of this standard (page 2, second last sentence in the last paragraph on the page). It would be good to get a bit more of an understanding as to what is meant by this in the context, however, this is unclear. This is especially important in terms of the ModSpec approach (section 4, page 10).
The text was updated successfully, but these errors were encountered:
Explain that we adopted GeoPose basic to specify position relative to the earth, then extended it for relative positioning. We decided not to use GeoPose to describe transform chains because SensorML already had a way to do this (through definition of reference frames and relative positions between them).
I think we missed the point of the comment. This is not about reference frames or GeoPose, it's about use cases for different processes:
The process model defined in SensorML can be used to describe a wide variety of processes, including not only sensors, but also actuators, spatial transforms, and data processes, to name a few.
Maybe spatial transforms is a little bit odd in this list, as it is to specific...
This public comment is respectfully submitted by the Web Service Technical Panel (WSTP) of the Defence Geospatial Information Working Group (DGIWG). This comment is specifically directed toward 23-000 OGC SENSORML ENCODING STANDARD. Spatial transforms are in-scope of this standard (page 2, second last sentence in the last paragraph on the page). It would be good to get a bit more of an understanding as to what is meant by this in the context, however, this is unclear. This is especially important in terms of the ModSpec approach (section 4, page 10).
The text was updated successfully, but these errors were encountered: