Specification

The aid library provides a Footlocker class that is initialized with the name of an electronic footlocker; this should be a simple string naming a directory on the system. If not provided, the class will initialize using an environment variable named FOOTLOCKER. If neither are provided, or if the named directory does not exist, the Footlocker's init function should return failure to the caller.

Location

On vulcan, the normal or default footlocker will be located at e:/footlocker

On chapman, the beginnings of a footlocker for testing appears at /space/krz/wasp/foot

Rsync is your friend; keep these in sync.

Triangle Registration

The triangle registration process loads a set of tables into memory in order to register images. These tables are typically raw arrays of indexes (offsets) and pixel weights. They are written in little-endian format as IEEE four byte reals (float) or unsigned 32 bit integers (ACE_UINT32).

In the footlocker directory, we will have a subdirectory that contains all the data files used by triangle registration. These files will have the names:

• LWT.dat
• LWC.dat
• MWT.dat
• MWC.dat
• SWT.dat
• SWC.dat
• LWTR.dat
• LWCR.dat
• MWTR.dat
• MWCR.dat

Other files may be present in this directory; they will be ignored.

The name of this subdirectory must start with treg. Multiple directories, each containing one set of registration data files, may be present on the system. A client tool can present to the operator a list of all directories that begin with treg for selection. These subdirectories do not nest; only directories starting with treg that appear in the FOOTLOCKER directory are valid.

There must be a directory named treg510 provided, in addition to any others. This is the default name used by the triangle registration process. A method for selecting and choosing other table directories for the ADP registration object will be provided later, but treg510 must be provided now.

Note: The files that appear in this directory must be named as shown above. Names like LWT510.dat will not be recognized. In short, the file names are fixed, so vary the directory names instead.

Fire Detection

• Q: Does fire detection require any external data, or is it purely a standalone algorithm?
  • A: As of July 27, 2005, fire detection does not require any external data. It operates solely on registered image data.

DEM

The footlocker will contain a directory called dems that contains all available digital elevation maps. For each DEM, there should be two files: one with an extension of .img and another with the extension .rrd. These files are to be "rectified images" as generated by (or compatible with) Imagine.

Interior Orientation

Each camera has associated with it an interior orientation. These will be present in a footlocker directory named intorient. In this directory will be one file for each camera, the name of the camera's band being the name of the file: LWIR MWIR SWIR VNIR

The contents of each file are seven decimal reals, separated by whitespace. The values must be, in order:

1. CCD size (mm²)
2. focal length (mm)
3. principal point, x
4. principal point, y
5. camera's radial distortion coefficient 1
6. camera's radial distortion coefficient 2
7. camera's radial distortion coefficient 3

As an example, here's the SWIR interior orientation.

: chapman; cat $FOOTLOCKER/intorient/SWIR
0.025
25.0940
0.1851
0.4193
8.0062e-3
-1.6737600e-4
-4.30041e-8

NUC

The ADP selects among NUC tables that are preloaded into each camera. It isn't clear if there's any call for loading NUC tables from disk at this point.

Boresights

Each camera has three principal boresight numbers associated with it. These will be provided as decimal reals in the electronic footlocker under a directory named boresights. The values for each camera band is in a file named by the band. For example,

: chapman; cat $FOOTLOCKER/boresights/SWIR       
0.227599
-0.173365
-89.0432

It is expected that the exterior orientation calculator will compute the boresight matrix from these three principal values.

Netmaps

All static network map files (called netmap files) are located in a directory named netmap. Names should be chosen according to configuration or role of the deployed system (e.g., dhs, flight). The actual contents of each of these files is detailed in WaspNetmapFile.