ROAF Tutorial Trail Overview


These Tutorial Trails are a very compressed version of the book. Readers of the book should follow the Trails to execute the 'hands-on' instructions, while reading the code development in the book. Naturally you will find problems revealed by readers or discovered after publication. Also all internet links are listed and updated regularly in the tutorials.

Trail 1 / Chapter 4: The roaf.gps Package

The roaf.gps package has classes and interfaces to deal with geographical coordinates (WGS84) and universal time (UTC). This package is a prerequisite to synchronize Real Objects in Real Object Applications, which will be introduced later.

The  Position interface, its GeoPoint implementation and its Route collection are ROAF tools to handle (lat,lon) coordinates anywhere on the globe. The GPSinfo interface, its GPSpoint implementation and its GPStrace collection add a timestamp to the (lat,lon) coordinates. The GPSunit makes use of these positioning and timing classes.

Trail 2 / Chapter 5: The roafx.gui Package

As a matter of principle the RO, ROA and ROAF components are developed without a graphical representation. Nevertheless human perception is dominated by visual information, and it is more intuitive to display traces on a map rather than looking at large amounts of decimal numbers. Therefor some Java Swing components are specialized to a simple mapping frontend as a demonstation to visualize positions and routes and to animate traces for ROAF development.

Trail 3 / Chapter 6: The roaf.ros.RealObject class

The ROAF is a platform to collect real world scenarios or ROApps composed of Real Objects. 
Every real world scenario can focus on different objects like cars, people, houses -- any thing. 

The RealObject (RO) is the root class of any real-world object to represent any physical thing known from the real world. Due to the different fields of ROApplications the RealObject is abstract and needs to be implemented for every operational area. The roaf.ros.RealObject class is preimplemented to provide

    • a location and speed relative to the external coordinate system at any time and
    • a mass and a body (size or shape) claiming space at its location and
    • connectivity to authenticate on a server to enter and interact in the scenario

Trail 4 / Chapter 7: Processing Digital (OSM) Maps

The Viewers developed in the previous Trails (i.e., GPX Viewer and Tile/MapViewer) are using map images tiles to display Traces on top of a map image. For a computer, these images are practically useless, and it would be almost impossible for the computer to identify roads. 

A machine can only interpret digital maps describing the mapped area by structured information - often referred to as spatial data. This Tutorial Trail describes how to process digital maps for dedicated applications with a Map Compiler. At the open source project OpenStreetMap, you can find free digital-map data for your geographical area to set up your own OSM Map Compiler.


Please be patient!

Due to time constraints the ROAF Online Tutorials are still under construction.