Parent Topic: GDB

Exportable File Formats

This is a sub-list of the Supported File Formats, representing all supported formats which are exportable.

OTHG Vector file (.OTG)

The OTHT Gold formatted product is designed to conform to the Canadian Department of National Defence ITG MTF standard format. The OTHT contact report format allows for reporting significantly more information than that which is available from the analysis of spaceborne SAR images. The OFW OTHT Gold format product is therefore a simplified version of the complete product. The product consists of a message header, the message body and a message termination sequence. The fields in a message set are separated by field markers (/). Fields are categorised as mandatory and optional. If there is no information for a specific fields, it may be omitted, although the field delimiters must be retained. Each line can be maximum 69 characters long. Fields can not be split between lines.

The OFW target detection message body in OTHT Gold format is a contact report that consists of a minimum of two lines of data. The first line is used to identify the contact, and starts with the identifier CTC. The following line is used to indicate a contact's position, time of position and other relevant information about the track. This line starts with POS as an identifier. In the OFW implementation, the probability of a target being a ship, the wake quality and course and speed are provided in comment or remark lines. These lines are identified with the sequence RMKS in the first field of the line.

Georeferencing information is supported also.

Hyperspectral Image Data format (.VQ)

The format for compressed hyperspectral image data

Data format version 2: Datatype Description Unsigned short Version Unsigned short Number of bits required to represent a

                           codebook vector index (#bits)

Unsigned short Number of rows (#rows) Unsigned short Number of columns (#cloumns) Unsigned short Number of spectral bands (#bands) Unsigned short Maximum intensity to be plotted Byte[64] String giving the unit for intensities Float[#bands] Wavelengths in microns Unsigned short[#bands][2^#bits] Codebook vectors Usigned byte-packed[#rows][#columns] Byte-packed Index map

Byte-packed compressed data is organized as follows: 1. The bits that represent each element are in general spread

   across two or more bytes in memory (exception: when the data 
   word size equals 8 bits)

2. The byte that contains the element's higher-order bits precedes

   in memory the bytes that contain the element's lower-order bits

3. Data is packed contiguously. Higher-order bits are filled first,

   and lower-order bits are made available for storage of the next 
   element.

4. The word size of each element is between 8 and 16 inclusively.

Map Info Table (.TAB)

The Map Info Tables in the form of TAB format are supported by the GeoGateway library for import,export.These format are exported with a type of ".tab".

All graphical object( feature) include TABFCPoint,TABFCFontPoint, TABFCCustomPoint,TABFCText, TABFCPolyline, TABFCArc,TABFCRectangle, TABFCEllipse, TABFCRegion. they are imported with all their attributes.

The Dataset of map info tab typically consists of at least five files which have same file name and different file sxtension( .dat, .id, .ind, .map, .tab). They are binary file except .tab which is small text file describing the format of the file containing your data,When you open a set of mitab file you have to select .tab file.these files must be kept together in same directory in order to be accessed.

MITAB library is an Open Source C++ library to read and write MapInfo .TAB (binary) and .MIF/MID files. It is based on the OGR library which is an implementation of the Open GIS Consortium Simple Feature specification. more info see: http://pages.infinit.net/danmo/e00/index-mitab.html

See MapInfo Data Interchange Format(MIF) for information on georeferencing.