[X3D-Public] [X3D-Earth] revised GpsSensor node proposal

[Alan Hudson]

On 12/16/2010 6:03 PM, Don Brutzman wrote:
> http://www.web3d.org/membership/login/memberwiki/index.php/X3D_v3.3_Specification_Changes#GpsSensor_node
>
>
> _GpsSensor node_
>
Looks like a useful node.

> GPS sensing devices have been stable for many years. GPS inputs are very
> useful for animating X3D scenes. GpsSensor will be a valuable addition
> to the forthcoming X3D Mobile Profile.
>
> Status. Active review and refinement needed by X3D Earth and X3D Working
> Groups in order to be ready for X3D v3.3.
>
> Use cases. The definition of use cases helps define the requirements and
> field data types for this new node.
>
> 1. Primary common use: ROUTE the GPS position_changed to GeoLocation or
> GeoTransform position field.
> 2. What are outputs if no GPS signal is available, or if the author
> wants to deliberately ignore values? The typical X3D way to handle these
> kinds of usage is with isActive and enabled fields. Thus GpsSensor
> should inherit X3DSensorNode interface.
> 3. Exposing date/time of new position record may be helpful for
> animations. Thus need timeStamp field.
> 4. May want to play back an NMEA file of GPS data points from memory.
> Thus need url field.

Not sure I see the reason to add a url to a sensor node.  None of the 
other sensor nodes have this capability.  Usually you store archived 
values back in interpolator nodes.

Do the timestamped values come out in x3d time of their values or do you 
play them back starting at world load with the first value and use the 
times to space them out?

Having this url will also make a desire to control the time base happen, 
ie to accelerate or decelerate events.  This would mean you'd likely 
start adding timesensor capabilities or need an external clock.




-- 
Alan Hudson

President Yumetech, Inc.                               www.yumetech.com
206 340 8900 ext 111