roaf.gps.GPStrace extends Route
Note: In the Tutorial and Book the class resides in roaf.book.gps. In the actual ROAF it was moved to roaf.gps
As described earlier ( in space & time ) a trace reflects the exact path of an object implying its physical attributes (mass, acceleration etc.). Most GPS devices are able to record traces and store them for later analysis. The recording method can usually be set to time or distance intervals. Traces make routes authentic and have many real world implications, which can be useful to simulate the recorded trace and to determine plausibility. The top speed strips down the real world representation: An object traveling at 50 km/h for a long time is probably not a bicycle. The top acceleration might distinguish a normal car from a race car or motorcycle. etc.
The GPStrace internally makes use of the protected List sequence by implementing additional bookkeeping of the element’s types. The Route is responsible for the Positions, while the GPStrace is responsible to control the timestamps. A programmer should be aware of the casting mechanisms of different implementations for Position / GPSinfo and Route / GPStrace as demonstrated with the mixedRoute in the GPSapplication at the end of this lesson.
|« GPSpoint||Java API||GPSunit »|