W3C home > Mailing lists > Public > public-poiwg@w3.org > November 2011

RE: yaw, pitch and roll ? and position accuracy?

From: Seiler, Karl <karl.seiler@navteq.com>
Date: Tue, 1 Nov 2011 10:05:26 -0500
To: Mike Liebhold <mnl@well.com>, "public-poiwg@w3.org W3C" <public-poiwg@w3.org>
Message-ID: <133ACBBC61BE0E4081B6E35E542ECE230F185666@hq-ex-mb03.ad.navteq.com>
What is an example use case for a Place specification that includes yaw, pitch and roll?

Yes, CM and MM accuracy is certainly here given the amount of Lidar place mapping this is in turn leading to high rez-3D models of places. This gets you to navigating to the entrance door handle for sight impaired and robotics.

Karl Seiler
Director Location Technology & Services
NOKIA Places Content & Operations - Chicago
(T)  +312-894-7231
(M) +312-375-5932

-----Original Message-----
From: Mike Liebhold [mailto:mnl@well.com]
Sent: Monday, October 31, 2011 6:38 PM
To: public-poiwg@w3.org W3C
Subject: yaw, pitch and roll ? and position accuracy?

Very sorry to jump in so late in the dialog. ( i've been buried elsewhere)

But, I have a couple of quick questions about the core data model:

Besides latitude, longitude and altitude attributes of position, What
has been decided about yaw, pitch and roll?

Can someone tell me if i'm correct in  assuming that the nominal CRS
would allow for a designation of the accuracy of the position. ( I"m
seeing the emergence of use cases requiring millimeter accurate positioning)

Many thanks,

Mike Liebhold

The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above.  If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited.  If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.
Received on Tuesday, 1 November 2011 15:06:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:31 UTC