FME can access data in AIRCOM International’s ENTERPRISE format.
Overview
For reading, FME considers an AIRCOM ENTERPRISE dataset to be the location of an index.txt file in one of the ENTERPRISE subfolders. For writing, the dataset is the name of the subfolder to write a single ENTERPRISE type. The reader can automatically determine which type of data is in this subfolder. The writer determines which ENTERPRISE type is being written and creates an appropriate folder structure and index.txt file for the destination dataset.
The AIRCOM ENTERPRISE format is a collection of different types of data. These types of data include height, clutter, vector, text, building vector, and population vector. The data is stored in a hierarchy of folders, with each subfolder containing a different type of data. Each subfolder will contain an index.txt file that will act as a guide to the location and type of data that is in the folder.
There can be an unlimited number of subfolders under the main folder. These subfolders can have any name that is legal for that operating system, but each subfolder can only contain one type of data. The index.txt file contained in each subfolder contains different fields depending upon the type of data contained in that subfolder.
The type of data that is stored is described below.
- Height Data: The data file name corresponds to a binary file that contains height values for each square on the raster defined by the easting-northing coordinates.
- Clutter Data: The data file name corresponds to a binary file that contains key values for the each square on the raster defined by the easting-northing coordinates. The key values correspond to strings found in the menu.txt file.
- Array Data: The data file name corresponds to a binary file that contains array values for the each square on the raster defined by the easting-northing coordinates.
- Vector Data: Each data file listed in the index file contains a set of 2D vectors that all have the same feature name.
- Text Data: Each data file listed in the index file contains a set of text features that all have the same feature name.
- Population Vector Data: Each data file listed in the index file contains a set of 2D polygons that all have the same feature name.
- Building Vector Data: Each data file listed in the index file contains a set of 2D polygons that all have the same feature name.
Reader Overview
The ENTERPRISE reader produces FME features for all feature data held in those files listed in the index.txt file.
The reader only returns the selected feature names. If none were specified, then all the features are read. When the index.txt file is exhausted, the reader is closed.
Writer Overview
The ENTERPRISE writer creates and writes feature data of a single type (Vector, Clutter, Heights, etc.) into a single folder specified by the Dataset parameter. The folder need not exist before the translation occurs. Any old files in the folder may be overwritten with the new feature data without warning.
The type of data that will be written by FME is determined by what is selected in the data type drop-down list in the ENTERPRISE writer parameter box. If first_feature is selected, the first feature routed to the ENTERPRISE writer by FME determines the type of data that will be written and all subsequent features will be written out as that type, if possible. Each of the other options corresponds to the selected ENTERPRISE feature type being written out.
ENTERPRISE only supports a limited set of coordinate systems. Please consult your ENTERPRISE documentation to ensure that you are writing data using one of the supported coordinate systems.
FME Raster Features
FME raster features represent raster data and use several concepts that are unlike those used in the handling of vector data.
For comprehensive information about how FME processes raster data, see Rasters.
The Height feature type supports rasters with a single numeric band.
The Clutter feature type supports rasters with a single band that has a string palette.
The Array feature type supports multiple numeric bands. The exact makeup of the bands depends on the array type (see the enterprise_array_type attribute).