ASPN: A data model for navigation measurements
Part of the Open Architecture Field Guide.
ASPN defines a common data model for navigation measurements. It gives sensor producers and estimation software a shared description of what was measured.
In this guide
A navigation measurement needs more than a number
A sensor reports a velocity of 3 m/s. Before navigation software can use that value, it needs to know the direction, the time of measurement, and the coordinate system in which the direction is expressed. A velocity along the vehicle's forward axis has a different meaning from a velocity toward geographic north. The same number can describe different motion when its context changes.
A navigation estimator uses measurements to infer quantities such as position, velocity, and orientation. It needs an unambiguous description of each measurement so that the observation can be related to the quantity being estimated. Units, reference frames, timing, and uncertainty are therefore part of the interface between a sensor and an estimator.
ASPN is a common data standard for positioning, navigation, and timing information. It defines representations that allow producers and consumers of navigation data to share the meaning of the information they exchange. [1] [2]
Describing the observation before choosing the estimator
The central design choice is to describe measurements in forms that can be used across sensor products and estimation methods. A range is a measurement of distance. A velocity measurement describes motion in a stated frame. The data representation needs to identify the observation and the information required to interpret it, while the estimator supplies the mathematical relationship to the navigation state.
Return to the velocity example. If the sensor reports motion in vehicle coordinates, the estimator must relate that frame to the one used for its state estimate. It also needs to relate the measurement time to the state being updated. An uncertainty description tells the estimator how the measurement's precision enters the estimation problem.
ASPN provides a shared representation at this boundary. Different systems can use different internal conventions while converting their data to and from a compliant representation. This lets a sensor producer preserve its internal implementation while supplying an agreed description to the software that consumes its output. [2]
Keeping data meaning separate from the algorithm
The same observation can be used by different estimation methods. One implementation might process measurements as they arrive, while another uses recorded observations in a batch calculation. Both need to know what was measured, but they can differ in how they combine that information with other observations and assumptions.
This separation gives algorithm development a stable input boundary. A team comparing two estimators can present the same defined measurements to each and examine the resulting estimates. It can then investigate differences in the calculation without first reconciling unrelated sensor-data formats.
The sensor side gains a corresponding boundary. A new source of a supported measurement can produce the shared representation, making its meaning available to software already designed to consume it. The data model supplies a common vocabulary; the integration connects the actual sensor observations to that vocabulary.
Transporting and processing the data
ASPN defines message content independently of a particular transport. The mechanism that carries a measurement between components is a separate design choice from the measurement's meaning. The model can therefore be used in recorded datasets and in software that exchanges observations during operation. [1]
pntOS uses ASPN within a framework for building sensor-fusion applications. ASPN describes the information exchanged; pntOS organizes components that process it. Understanding those separate responsibilities makes it easier to locate an integration question. An ambiguity about a measurement belongs at the data-model boundary, while a question about how an estimation component participates in the application belongs at the software interface.