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
I'm contributing to a renewed effort to support geographically-aligned orientation (or Geo-alignment) in user agents currently under way in the W3C Immersive Web group. This is primarily aimed at Extended Reality (XR) use cases, but overlaps with other areas such as WebVMT for geotagged video. In addition, several of the group are involved in parallel work at the Open Geospatial Consortium (OGC) which is standardising GeoPose (location and orientation) for the geospatial community.
W3C Geolocation API already supports 3D location and heading which constitute four of the six degrees of freedom included in Geo-alignment and GeoPose, so this seems like a good moment to discuss ways in which to align our work given that we share a lot of common ground.
Please let me know whether this is of interest and who best to contact. Many thanks.
The text was updated successfully, but these errors were encountered:
I've skimmed some of your documentation and it appears that a combination of the Geolocation API and AbsolutionOrientationSensor interface should provide all of the information necessary to construct a GeoPose through I agree that for XR purposes it is likely more useful to time this data with the rest of the XR positioning information rather than constructing it piecemeal from a number of unrelated APIs.
I'm contributing to a renewed effort to support geographically-aligned orientation (or Geo-alignment) in user agents currently under way in the W3C Immersive Web group. This is primarily aimed at Extended Reality (XR) use cases, but overlaps with other areas such as WebVMT for geotagged video. In addition, several of the group are involved in parallel work at the Open Geospatial Consortium (OGC) which is standardising GeoPose (location and orientation) for the geospatial community.
W3C Geolocation API already supports 3D location and heading which constitute four of the six degrees of freedom included in Geo-alignment and GeoPose, so this seems like a good moment to discuss ways in which to align our work given that we share a lot of common ground.
Please let me know whether this is of interest and who best to contact. Many thanks.
The text was updated successfully, but these errors were encountered: