Some notes on EDX and other software interoperability
EDX software was designed to take advantage of a large number of external data sources, making it easy for customers to switch to our product. However, there are some areas where we can’t import easily, and this document attempts to cover what we can and can’t do, and what this means for customers who use more than one planning tool.
Calculation Data Files
We can read a number of standard data formats from the USGS, and SRTM. We also read We usually suggest converting that data to our .201 format for speed and size reasons.
Terrain data formats we read directly are:
USGS ASCII DEM
DTED Level I and II
ESRI Binary Grid
SRTM in .hgt format
We can convert to .201 from other sources using EDXCV
Clutter formats we read directly are:
We can convert from ESRI Binary grid, and USGS ASCII formats using EDXCV
We only read our .mcs format files. These can be created/converted from .dwg files using BEditor or SignalIQ. We do not read in from Google earth or other programs.
Other Raster Data Files
We do not read census data directly. It needs to be converted for use in our tool
We do not read traffic data directly. It needs to be converted for use in our tool
We read the following measurement files:
Anritsu LMR Master[/list]
All other formats need to be put into a comma delimited format. NOTE: format change over time, so we may not read the latest versions of the listed files.
Display and Other Vector Files
We read most of the above formats directly. NOTE: they MUST be in a lat/long Transverse Mercator format. If they are in state plane or other format, they will not display in EDX.
We can display .tiff images if they have been geocoded. The .tiff format supports internal geocoding, or uses an accompanying .tab file that specifies the location of the 4 reference points in the file.
We do not read equipment locations or files directly from other software. If the equipment specifications and locations can be exported to a .csv format, they can be arranged onto our format and imported into EDX.
We do not read antenna patterns directly from other formats. They must be converted using CVANT or MS Excel.
We do not read other psd files directly. If they can be exported to a .csv format, they can be arranged on our format and used.
The project files (project.*.xml) make up the guts of a customer project. It’s plain text readable xml. We currently do not have a way to convert to or from our format to others. This represents the biggest hurdle to interoperability with other tools.
Currently, in EDX a user would have to create a project from scratch, and get the basic location values, study grid dimensions, and other setup and study related information from the user who has a different tool, then implement it in EDX. This represents the biggest amount of work. Another problem is the propagation models…we may have slightly different implementations of the same models vs other tools.