EDX software allows you to use a wide variety of EDX databases or your own custom databases.

Types

Here is a list of the types of databases EDX software can access:

Terrain

Terrain databases.

Clutter

Clutter databases.

Map information

Roads, railroads, political boundaries, coastlines, city and town locations and names, street data, and custom GIS map databases.

Demographics

U.S. Census (in EDX format) and custom demographic databases.

Traffic

You can create and use databases of telecommunication traffic density in units of milli-Erlangs or Mbps for each sector based on criteria such as uniform distribution, land use, demographic, or traffic databases.

Measurement

You can make use of collected test & measurement data for statistical analysis, propagation model tuning, creation of sector-specific propagation models, and for prediction purposes in lieu of propagation models.

Buildings/Floor plans

EDX building outlines and custom building/floor plan databases.

Images

Raster images for use as map background layers.

Installation

Installing a database is as simple as copying the files into folders on your hard drives. Some thought should be put into the structure of the folders and files, as well as their location. If you are a single engineer using the software, and you foresee no need to share your projects with other engineers, a suggested structure is: create a folder in your C:\Users\logged_in_user\Documents\EDX\named data. In that folder create a terrain folder, a clutter folder, a GIS folder, etc. and copy the terrain files (.201) to the terrain folder, the clutter files (.gcv) to the clutter folder, etc. If you have terrain or clutter in a different format than our default, they should get their own named folder.

Sharing

If you anticipate sharing projects and data with other engineers, you have a few options. Create the above folder structure, but on the root level (C:\) of your hard drive. Another option is to use an external drive, just make sure to bind that eternal drive to a specific drive letter. Another option is to put the data on a networked drive. Be aware that since we read a lot of data from those directories, performance can be impacted by network latency.