# SensorML 2.0 Examples

## Sensor with Dynamic Position

In order to support a wide variety of needs for providing location, orientation, and dynamic state of a physical component or system, there are several means for specifying "where". These include byDescription, byPoint, byLocation, byState, byTrajectory, and byProcess.

For a dynamic location (e.g. the motion of an airplane), one must use a swe:DataArray which takes a swe:DataRecord as it's elementType. The first field of the swe:DataRecord must be a Quantity designating time tags for each step along the trajectory. The remaining fields must consist of one or more swe:Vector elements describing location, and perhaps orientation and dynamic state (e.g. linear velocity and acceleration, and angular velocity and acceleration).

In the example below, only location is required and provided since the dynamic sensor simply takes in-situ temperature measurements along its path. For dynamic remote sensors, orientation and dynamic state may also be required. Also in this example, the values for the trajectory are provided inline for a given time segment with each line of the 10 measurements consisting of time (in ISO-8601 encoding), ltitude, and longitude, as described for the DataRecord. Other options for providing the trajectory values would be to provide an online reference link for the values:

<swe:values xlink:href="http://myServer.com/mySensor/position.dat"/>

or to provide a link to a web service (see byProcess described in other examples).

NOTE: SensorML 2.0 is not yet approved by the Open Geospatial Consortium (OGC). Examples are provided for evaluation and are subject to change during the standards review and approval process. Contact mike.botts@botts-inc.net for questions or recommendations.