- From: Mike Liebhold <mnl@well.com>
- Date: Tue, 01 Nov 2011 09:54:09 -0700
- To: "Seiler, Karl" <karl.seiler@navteq.com>
- CC: "public-poiwg@w3.org W3C" <public-poiwg@w3.org>
On 11/1/11 8:05 AM, Seiler, Karl wrote: > What is an example use case for a Place specification that includes yaw, pitch and roll? For AR, I'm assuming that a focal plane is the point of view. Notation for yaw pitch and roll are ideal for orientation of labels or graphics associated with specific orientation of a place or thing. For robotics, same thing plus, orientation for best direct kinetic access to a place or thing. To name a couple ... Thanks Karl. > > 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 16:56:55 UTC