angelfire metadata format - ngageoint/voxel-globe GitHub Wiki
![AngelFire](https://camo.githubusercontent.com/e38588646e2b49d6ebffe04c7c2bc1fcd64be522a237a9322ecd6400bf0a97b8/687474703a2f2f7777772e676c6f62616c73656375726974792e6f72672f696e74656c6c2f73797374656d732f696d616765732f616e67656c2d666972652d696d61676530322e6a7067)
- AngelFire data consists of 6 images take are taken simultaneously from a matrix of cameras, similar to CLIF
- The images are named “YYYYMMDDhhmmss-%08d-%02d-VIS.jpg” with the first number being the frame number and the second number being the camera number
- There is a corresponding .pos metadata file for each set of 6 frames.
- The text files describe the position and heading of the plane and have the following 15 data fields (comma separated one line files):
- Magic Number – Just the string “$ANGELFIRE” without the quotes
- Rotation about the z-axis – Rotations in degrees
- Rotation about the x-axis – Rotation in degrees
- Rotation about the y-axis – Rotation in degrees
- Final rotation order is z-x-y, where x and y were negative
- Latitude – WGS-84 degrees
- Longitude – WGS-84 degrees
- Altitude – Feet above the WGS-84 ellipsoid
- GPS time – Seconds after midnight Sunday
- GPS week – Weeks since Jan 6, 1980
- North Velocity
- East Velocity
- Up Velocity
- IMU status
- Local Adjustment
- Daylight Savings time flag
- Pos files are named for cameras 0 only.
- The orientation of the cameras represent the orientation of the camera plate, not camera 0
- Each individual camera is rotated so that there is about 100 pixels of overlap
⚠️ **GitHub.com Fallback** ⚠️