</font>

The SoVRMLGeoViewpoint node defines a specific location in a local geospatial coordinate system from which the user might view the scene.

VRML X3D SPECIFICATION

This section describes the expected behavior of the node in a conforming X3D / VRML97 browser application. In some cases, the application is responsible for implementing portions of the expected behavior. Open Inventor viewer classes and IVF classes implement some of the application behaviors.

This section may reference portions of the X3D specification that are not present in this help file. The complete X3D spec is available at http://www.web3d.org.

The SoVRMLGeoViewpoint node allows the specification of a viewpoint in terms of a geospatial coordinate. This node can be used wherever a Viewpoint node can be used and can be combined with Viewpoint nodes in the same scene. The fieldOfView, jump, description, set_bind, bindTime, and isBound fields and events have the same behavior as the standard Viewpoint node. When a SoVRMLGeoViewpoint node is bound, it overrides the currently bound Viewpoint and NavigationInfo nodes in the scene. The geoOrigin field is used to specify a local coordinate frame for extended precision as described in 25.2.5 Dealing with high-precision coordinates. The geoSystem field is used to define the spatial reference frame and is described in 25.2.3 Specifying a spatial reference frame. The position is used to define the actual coordinate at which the viewpoint is to be located. It should be provided in a format consistent with that specified by geoSystem. There is also a set_position field which can be routed from the geovalue_changed field of a GeoPositionInterpolator node in order to animate the position of the SoVRMLGeoViewpoint. The orientation string defines a relative orientation from the local orientation frame that is defined by the position field. By default, the orientation of the viewpoint will always be aligned such that the +Y axis is the up vector for the local area (the normal to the tangent plane on the ellipsoid), -Z points towards the north pole, and +X is east. Therefore, if a SoVRMLGeoViewpoint is created that always looked straight down, no matter where on the planetary body is being observed, an orientation value of [ 1 0 0 -1.57 ] is used. The set_orientation field can be routed to the value_changed field of an OrientationInterpolator in order to animate the orientation of the SoVRMLGeoViewpoint. The navType field is used to specify the navigation type that is to be bound when this SoVRMLGeoViewpoint node is bound. The acceptable values for this field are the same as those for the type field of the NavigationInfo node. The headlight field is used to specify the whether the viewer shall turn on a headlight when this viewpoint is bound. A headlight is a directional light that always points in the direction that the user is looking. The SoVRMLGeoViewpoint node may be implemented as if there is an embedded NavigationInfo node that is bound and unbound with the SoVRMLGeoViewpoint node. The speedFactor field of the SoVRMLGeoViewpoint node is used as a multiplier to the elevation-based velocity that the node sets internally; i.e., this is a relative value and not an absolute speed as is the case for the NavigationInfo node.

FILE FORMAT/DEFAULT

VRMLGeoViewpoint {

description	""
fieldOfView	0.785398
headlight	true
jump	true
metadata	NULL
navType	["WALK","ANY"]
geoOrigin	NULL
geoSystem	["GD","WE"]
orientation	0 0 1 0
position	0 0 100000
speedFactor	1.0

}

EVENTS

eventIn

SoSFBool	set_bind (Note: Not implemented)
SoSFFloat	set_fieldOfView (Note: Not implemented)
SoSFBool	set_headlight (Note: Not implemented)
SoSFBool	set_jump (Note: Not implemented)
SoSFRotation	set_orientation (Note: Not implemented)
SoSFVec3f	set_position (Note: Not implemented)
SoSFString	set_description (Note: Not implemented)
SoMFString	set_navType (Note: Not implemented)
SoSFNode	set_metadata (Note: Not implemented)

eventOut

SoSFTime	bindTime (Note: Not implemented)
SoSFBool	isBound (Note: Not implemented)
SoSFFloat	fieldOfView_changed (Note: Not implemented)
SoSFString	description_changed (Note: Not implemented)
SoSFBool	headlight_changed (Note: Not implemented)
SoSFBool	jump_changed (Note: Not implemented)
SoMFString	navType_changed (Note: Not implemented)
SoSFNode	metadata_changed (Note: Not implemented)

Obsoletesince Open Inventor 9500 The VRML API is no longer supported. See section http://oivdoc95.vsg3d.com/content/compatibility-notes-4#Deprecation of the Reference Manual.

Reference