Expanding OGC GeoPose Support for Visual Positioning

Open Geospatial Consortium (OGC) and Metaverse Standards Forum invite you to this workshop for the new OGC GeoPose standards that are reaching draft stage—help shape the future of interoperable Visual Positioning Services (VPS) and real-world spatial computing.

Register

Background

A geographically-anchored pose, or ”GeoPose” for short, is a real or digital object’s pose that is defined relative to a geographical frame of reference. All physical world objects have a geographically-anchored pose. Digital objects may be assigned/attributed a GeoPose. The OGC GeoPose 1.0 Data Exchange Standard defines rules and requirements for specifying, managing and exchanging the location and orientation (“poses”) of real or virtual objects within reference frames anchored to the Earth’s surface (“geo”) or within other coordinate systems tied to other objects than the Earth. The OGC GeoPose 1.0 Data Exchange Standard was approved in 2022. See GeoPose.org for more information.

The Real/Virtual World Integration Working Group of the Metaverse Standards Forum (MSF) focuses on use cases that identify requirements for merging the physical and digital world. The Ride Hailing Use Case is the basis for a prototype project. This project uses Visual Positioning System to identify the position and orientation of both vehicles and riders.

Requirements identified in the Working Group’s project were sent to the OGC. These are now the subject of new Work Packages in the GeoPose SWG.

Current Status and Call for Contributors

After six months of research and discussions, the GeoPose SWG’s GeoPose 1.x proposals for new standards are ready for review and feedback from Real/Virtual World Integration Working Group and Forum members and other stakeholders who could adopt the future standards or contribute to their development.

Please consult the OGC Call for Contributors page for more information on how Work Packages will address change requests and how you can add value.

Workshop Goal

The goal of this workshop is to share the current status of three GeoPose Work Packages and to solicit feedback and insights from a wide variety of professionals and communities that will help the GeoPose SWG produce the best possible results.

Partnership

This workshop is organized jointly with the Real/Virtual World Integration Working Group of the Metaverse Standards Forum, the Open Geospatial Consortium GeoPose Standards Working Group, and Open AR Cloud Europe contributors and partners working on OSCAR4US, an NGI Search project.

Focus

This workshop will focus on the proposed enhancements of GeoPose 1.0 that address change requests required to fully support open and interoperable Visual Positioning System (VPS) services. The core functionality of a VPS is to respond to a request containing an image received from a device with its position and orientation, in this case, a GeoPose. VPS is a key use case for GeoPose as it depends on the ability of GeoPoses and linked GeoPoses to model the relationships between imaging sensors rooted in their own local space, the local spaces of other sensors, and a shared space of the local environment.

GeoPose 1.x Work Packages 5 (Time), 7 (Uncertainty), and 8 (VPS support) provide the data objects required to support the VPS prototypes. The  Real/Virtual World Integration Working Group of the Metaverse Standards Forum progress to date has revealed that an open and interoperable VPS also requires:

• Depth Map – a field of poses
• Camera Model – a specialized frame transform
• Camera Calibration – another specialized frame transform
• Target Set – a set of discrete poses
• Radiance Field – a full or partial radiance model
• Links and Context: linking functionality and a “sticky rule” for the JSON encoding

Solutions to address the change requests in these WPs are being explored and approaches tested in the MSF R/V WI Working Group which is developing its VPS prototype service in parallel and collaboration with the OSCAR4US project OpenVPS prototype. The services use different methods to support functionally similar APIs.

Agenda