This tutorial shows you how to import and analyze measured data in Overture. Overture only supports basic visualization and analysis of measured data, and there are more sophisticated solutions available for detailed analysis from companies such as Xceed or Actix.

Installation

Overture does not require a license for many simple visualization and analysis tasks. Overture can be installed from the product page or by simply clicking on the installation button below:

A simple extension module has been created to support some of the tasks that are specific to measured data analysis, and this module can be installed by clicking here:

For more information about installing and using Overture, please consult our installation guide.

Using the Measured Data Module

The Measure Data Module was developed in consultation with Wider Networks and this tutorial is based around data in their format.

Importing Measured Data

Overture supports the import of point data in multiple GIS formats. Data collected from drive tests is typically a series of signal measurements with time and location information. The most common format for this data is a simple text file where the data columns are delimited by a comma or tab character, generically known as Commas Separated Values or CSVs.

Many drive test files are in proprietary, binary formats that are not supported directly by Overture. To use data in this format, it must first be exported as a text file. The ability to deal with data in its native format is one differentiating feature of the dedicated measured data tools mentioned above.

Wider Network's WIND raw data is in a binary format, but this data is post-processed to produce high accuracy signal information and server resolution. This post-processed data is in text format and can easily be imported into Overture. During post-processing, this data can be "binned" to average out local signal variations and reduce the size of the data file. This binned data is the recommended import format for Overture.

To import a Wider Networks data file, follow these instructions on point data import for a Spreadsheet Point Provider. The data file may not have an extension that is recognized by Overture, in which case, change the file dialog filter to All Files (*.*). The X Column and Y Column properties should be set to point to Lon and Lat respectively as shown below:

The data should now be visible on the map and in the data browser.

Pilot Pollution Analysis

The Measured Data Module adds a simple way of checking for pilot pollution in measured data streams. This is implemented as a point provider called Pilot Pollution Points, and can be added to the project by adding a new point map (as before) and adding a new point provider as follows:

Set the Signal Provider property to point at the drive test file, and set the Server Column and Signal Column properties to point at Sector_Code and RSCP for UMTS streams or Sector Code and SL for GSM streams.

There should now be two point maps in the project, one showing the original drive test and the other showing the locations with pilot pollution. To see the level of pollution, set the Selected Column to Count...

...and adjust the Numerical Key / Color Value Definitions to show the severity of the pollution like this...

Now the map should show locations that meet the pilot pollution criteria as shown here:

Also, both point data providers can be inspected using the Data Browser:

Importing Cell Database from Wider Networks

Overture can import the cell database in Wider Networks format using a dedicated network importer that is only available in the Measured Data Module. To import the cell database, go to the Start Page and through to the Network and Import sub-pages and press the Add a new component button:

Then select the "Wider Networks Importer" component:

Now point the Import File Name property at the network database file and press the Import action button on the toolbar. The technology (UMTS or GSM) is automatically determined and all of the data columns are imported into Overture. Columns like azimuth and downtilt are mapped to their Overture equivalents and columns like MCC and MNC are encapsulated in Flags.

To browse the imported network data, open the Site, Radio, and Sector Tables.

Exporting Cell Database to Wider Networks

If any modifications have been made to the network data, it can be exported in Wider Networks format by adding a "Wider Networks Exporter" from the Start > Network > Export menu option.

Pilot Pollution Server Resolution

If the network database is concurrent with the drive test data, it can be used to better resolve pilot pollution issues. For every point with pilot pollution, the server and interferer cell ID is recorded and can be matched to cells in the project. This is enabled by default, but can be controlled with the Resolve Servers property of the pilot pollution point provider. Setting this property to false treats all cell IDs as simple strings, which cannot be navigated in results tables. This is useful where the network database is incomplete or absent.

The easiest way to see the effect of server resolution is to create a statistic. Add a Statistic Data Provider for Points and configure it as shown below:

Then create a new Statistic that uses this data provider by going to Start > Analysis > Statistics and adding a new component:

Edit the data providers of this new statistic to include the pilot pollution statistic data provider that was created previously:

When the statistic is ready, press the Calculate action button to generate the results table. This will count the number of points with pilot pollution and group them by worst interferer like this:

Sorting the last column in descending order shows the worst interfering sectors first:

Because the server resolution option was active, selections made in this table will be reflected in other tables and the map. Double clicking on a sector name takes the map to that sector, making it easy to identify poorly configured sectors.