Exif
In 353 camera in JPEG images we use standard EXIF fields (EXIF 2.2 specification from exif.org) for image description. All JPEG images have mentioned below fields (you can check this with any program what have support of Exif, in Linux with "exif" command line program, for example):
Tag name | Tag ID | Sample value | description |
Image description | 0x010E | coming soon... | |
Manufacturer | 0x010F | Elphel, Inc | standard |
Model | 0x0110 | 353 | standard |
Software | 0x0131 | 7.1.0.18 | firmware version of camera at exposition moment |
Date and Time | 0x0132 | 1970:01:01 01:50:14 | standard; time from FPGA RTC at sensor start moment |
Artist | 0x013B | 00:0E:64:01:02:03 | serial number of camera (Ethernet MAC address), ASCIIZ value |
Exposure Time | 0x829A | 1/49 sec. | standard |
Date and Time (original) | 0x9003 | 1970:01:01 01:50:14 | standard; time from FPGA RTC at sensor start moment |
SubSecTimeOriginal | 0x9291 | 686527 | standard; time from FPGA RTC at sensor start moment |
Note: in latest at this moment firmware (7.1.0.18) for 353 camera (CMOS sensor) all fields are correct, but with 363 camera (CCD sensor) we have wrong exposure time and shifted timestamp - TODO.
Exif data supported by Imgsrv and Camogm is described in Imgsrv#imgsrv_and_Exif_data. More changes are expected shortly - software will support more flexible Exif data including GPS-related fields.--Andrey.filippov 10:40, 28 March 2008 (CDT)
EXIF Data Extraction Example Script
This example script was written by Konstantin Kim in PHP and based on PEL (PHP Exif Library) from Martin Geisler.
Both are released under GNU GPL V3.
The script extracts EXIF data from a MOV file and writes it to a KML file. It's easy to modify to do something else.
Though the script has a design error, it needs to load the entire MOV file into RAM. So dont use it with 32GB files ;)