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.

Sign up for GitHub

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

Jump to bottom

GeoPose as a representation of OGC API - Moving Features temporal geometry #31

Open
jerstlouis opened this issue Jan 21, 2023 · 0 comments
Open

GeoPose as a representation of OGC API - Moving Features temporal geometry #31

jerstlouis opened this issue Jan 21, 2023 · 0 comments

Comments

@jerstlouis
Copy link
Member

The basic conceptual model / capabilities seems to overlap between OGC API - Moving Features (overview / draft) and GeoPose:

  • MF coordinates / GP position (or parameters latitude / longitude in Advanced encoding)
  • MF datetimes / GP validTime (in advanced encoding only? -- see #70)
  • MF orientations .angles / GP angles / quaternion

Could a GeoPose sequence possibly be supported as a representation for the OGC API - Moving Features temporal geometries response, providing the position, time and orientation along a sequence (see also opengeospatial/GeoPose#73)?

(also asked in GeoPose: opengeospatial/GeoPose#71)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jerstlouis