Automatic Alignment to Chainage/GIS
All data produced by the new (Network) system is accurately geolocated to an accuracy of 0.1 meters. An encoder is also used to ensure that the data is accurately co-located to an accuracy of around 1cm. Our processing allows import of a mapinfo polyline file for the road network. The processing software uses this high level road name, number, section number, chainage details and other parameters to split the data collected by the system into the different roads. Once the data is split into different roads, the section and chainage alignment points are automatically added at various positions along the road data. Once the mapinfo data is imported, this alignment processes is fully automatic.
The GPS information is retained in this process, allowing the data to be displayed in either a chainage format or in a GIS format. All tagged features exports have joint GPS and chainage values for accurate positioning.

Automatic Detection of Features
Data is downloaded to our/your main server for storage and processing. The data is automatically processed on the server, to produce a list of surface features. Each feature is located by its GPS position, its chainage, lateral position along the road, section and road name. Features have a number of measures, for example longitudinal cracks have the crack type, width, orientation, length and severity.
Assets may alternatively be manually analysed through the Portal4D software. These assets would include signage, walkway location and condition, guard-rail location and condition and some other roadside assets.

Figure 3.1: Raw image as produced by the linescan camera with artificial lighting. This is with only one lighting direction. Improved performance will be achieved with the full photometric lighting conditions.

Figure 3.2: The raw output from the crack detection algorithms, with the red lines indicating the automatically detected cracks within the pavement.

Figure 3.3: Stylized output of the crack results showing both crack width and length. Tags are then automatically created for these features which are then exported from the processing software suite for loading into Portal4D or an asset management database system.