Prediction Models and Corresponding Pre-Processed Database Files

Depending on the selected mode for the pre-processing run, different output files are generated. The different modes (and thus output files) are required for the different prediction models. All files produced during the pre-processing are stored in binary format.

For each mode, one different file is generated. This file contains the building data as well as the visibility information and the considered parameters for this pre-processing, for example, area, resolution.

The building data of the whole area covered by the ODB file is checked and saved to the corresponding pre-processing file in any case, even when creating database files for IRT prediction. This is because WinProp allows a post-processing of the prediction using the knife edge diffraction model. Therefore, the building information of the whole area is required for any prediction and thus always computed.

While the pre-processing for the COST and UDP models contains always the whole area (due to the point mentioned above), the area for the IRT pre-processing can be selected by the user.

Table 1. Urban Output Files.
Extension Result File Type
Outdoor Database Binary
Raw outdoor binary vector database. This database must be pre-processed first, to be used for a computation.
Outdoor COST Binary database
Pre-processed database for a prediction with one of the empirical vertical plane models (for example, COST).
Outdoor IRT Binary database
Pre-processed database for a prediction with the deterministic IRT (Intelligent Ray Tracing) model.
Outdoor UDP Binary database
Pre-processed database for a prediction with the UDP (urban dominant path) model.

If enabled by the option Generate log-file during pre-processing, a log file is written. The file name is the same as the database output file name (.odb) with the .log suffix. The file contains all (error) messages that are issued during the pre-processing as well as additional information.