Previous Next        Current Page: NeXtMidas User's Guide / Files / Blue Files / FileTypes / Type 5000 Files
FAQs   
Release Information   
Getting Help   
Basic Concepts   
Result Parameters   
XML Support   
Files   
   - AUX List   
   - Inferred Content   
   - Qualifiers   
   - File Trimmers   
   - Access from Macros   
   - Blue Files   
      - File Structure   
      - FileTypes   
         - Type 1000 Files   
         - Type 2000 Files   
         - Type 3000 Files   
         - Type 5000 Files   
         - Type 6000 Files   
      - Header Content   
         - Basic Header   
         - Adjunct Header   
         - Extended Header   
System Operation   
Macros   
Applets and WebStart   
Graphics   
X-Midas Interoperability   
Third-Party Compatibility   
Installation and Customization   
Running NeXtMidas Independently   
Glossary   


Type 5000

Type 5000 files contain record-oriented data structures. These more complex structures typically support operations dealing with motion in three-dimensional space, such as orbital state vectors and propagation of electromagnetic energy. In a Type 5000 file one data element is one record, but now the record contains up to 14 contiguous components. Each component is associated with a name and data format, but because they are contiguous no offset is needed. Instead, the component takes on a unit value and a type value, such as spherical, Cartesian, geodetic, etc. In addition, the Type 5000 header can contain quadwords defining the frame of reference for the file. The header of Type 5000 files contains:

  • physical abscissa units
  • physical abscissa starting value
  • physical abscissa increment
  • number of components
  • bytes per record
  • frame of reference and other pertinent quadwords
  • component structure, including format, type, and units

Classes of Type 5000 Files

There are several special classes of Type 5000 files, each with a specific purpose. The class for each is determined by the names of the components in the file.

Class Name Component Names (Type) Example
Position POS  (VD)
NAME (1A)
cities.prm
Ellipse POS  (VD)
ELPS (VD)
NAME (1A)
ellipse5000.prm
EllipseFlags POS  (VD)
ELPS (VD)
NAME (1A)
FLAG (8B)
ellipseflags5000.prm
Cone POS  (VD)
POSP (VD)
CONE (VD)
NAME (1A)
cone5000.prm
ConeFlags POS  (VD)
POSP (VD)
CONE (VD)
NAME (1A)
FLAG (8B)
coneflags5000.prm

The complets set of supported fields are listed below. Note that ELPS and CONE are mutually exclusive. The NAME and POS fields are required, the other fields are typically optional (except in the case of the defined file types listed above).

 Name   Format   Description 
NAME 1A Name of the point.
NOTE 1A Note to accompany point.
POS VD Point position (ALT,LAT,LON).
POSP VD Secondary position for cone (ALT,LAT,LON).
ELPS VD Ellipse Parameters (semiMaj,semiMin,tilt).
  semiMaj - the length of the semi-major axis in meters
  semiMin - the length of the semi-minor axis in meters
  tilt - the tilt of the ellipse (i.e. the orientation of the semi-major axis) in degrees where 0=North, 90=East, etc. Note: this should only have values in the range [0,180] since the ellipse is symmetric across the semi-minor axis Ellipse drawing
CONE VD Cone parameters (radius,angle,angle).
CONN SB Draw line to previous point (1=draw or 0=no draw).
HDG SF Cardinal heading to use for the symbol (0..360).
FLAG 8B Draw flags:   FLAG[0] - Length of the name (in characters).
  FLAG[1] - Name position. (Not Supported)
  FLAG[2] - The color (by index).
  FLAG[3] - Background color. (Not Supported)
  FLAG[4] - Cone/Ellipse type (0=hidden, -9=visible).
  FLAG[5] - Invert. (Not Supported)
  FLAG[6] - X-Midas Symbol ID.
  FLAG[7] - Symbol size.
Note: NAME and NOTE can be ASCII fields of any length. 1A is most common for NAME while longer fields are typical for NOTE.