Skip to content
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

Spatial Transforms in OGC SensorML #110

Closed
Sam-Bolling opened this issue Dec 17, 2024 · 2 comments · Fixed by #131
Closed

Spatial Transforms in OGC SensorML #110

Sam-Bolling opened this issue Dec 17, 2024 · 2 comments · Fixed by #131
Assignees
Labels
ready Was discussed during a telecon and a decision was made sensorml

Comments

@Sam-Bolling
Copy link

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).

@alexrobin
Copy link
Collaborator

Discussed during 01/09 telecon.

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).

@alexrobin alexrobin added the ready Was discussed during a telecon and a decision was made label Jan 9, 2025
@autermann
Copy link
Member

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...

@autermann autermann linked a pull request Feb 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Was discussed during a telecon and a decision was made sensorml
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants