MIE is a flexible format which may be used as a stand-alone meta information
format, for encapsulation of other files and information, or as a trailer
appended to other file formats. The tables below represent currently
defined MIE tags, however ExifTool will also extract any other information
present in a MIE file.
When writing MIE information, some special features are supported:
1) String values may be written as ASCII (ISO 8859-1) or UTF-8. ExifTool
automatically detects the presence of wide characters and treats the string
appropriately. Internally, UTF-8 text may be converted to UTF-16 or UTF-32
and stored in this format in the file if it is more compact.
2) All MIE string-value tags support localized text. Localized values are
written by adding a language/country code to the tag name in the form
TAG-xx_YY, where TAG is the tag name, xx is a 2-character lower
case ISO 639-1 language code, and YY is a 2-character upper case ISO
3166-1 alpha 2 country code (eg. Title-en_US). But as usual, the user
interface is case-insensitive, and ExifTool will write the correct case to
the file.
3) Some numerical MIE tags allow units of measurement to be specified. For
these tags, units may be added in brackets immediately following the value
(eg. 55(mi/h)). If no units are specified, the default units are
written.
4) ExifTool writes compressed metadata to MIE files if the Compress (-z)
option is used and Compress::Zlib is available.
(the capitalized common extension for this type of file. If the extension
has a dot-3 abbreviation, then the longer version is used here. For
instance, JPEG and TIFF are used, not JPG and TIF)
(16-byte MD5 digest written in binary form or as a 32-character hex-encoded
ASCII string. Value is an MD5 digest of the entire 0MIE group as it would be
with the digest value itself set to all null bytes)
'zmie'
TrailerSignature
undef
(used as the last element in the main "0MIE" group to identify a MIE trailer
when appended to another type of file. ExifTool will create this tag if set
to any value, but always with an empty data block)
For the Audio group (and any other group containing a 'data' element), tags
refer to the contained data if present, otherwise they refer to the main
SubfileData. The 0Type and 1Name elements should exist only if data
is present.
('deg' CW from true north unless 'deg{mag}' specified)
'DateTime'
GPSDateTime
string
'Datum'
GPSMapDatum
string
(WGS-84 assumed if not specified)
'Differential'
GPSDifferential
int8u
0 = No Correction
1 = Differential Corrected
'Distance'
GPSDestDistance
rational64s
('km' unless 'mi' or 'nmi' specified)
'Heading'
GPSTrack
rational64s
('deg' CW from true north unless 'deg{mag}' specified)
'Latitude'
GPSLatitude
rational64s[n]
(1 to 3 numbers: degrees, minutes then seconds. South latitudes are stored
as all negative numbers, but may be entered as positive numbers with a
trailing 'S' for convenience. For example, these are all equivalent: "-40
-30", "-40.5", "40 30 0.00 S")
'Longitude'
GPSLongitude
rational64s[n]
(1 to 3 numbers: degrees, minutes then seconds. West longitudes are
negative, but may be entered as positive numbers with a trailing 'W')
(standard ColorSpace values are "sRGB" and "Adobe RGB")
'Components'
ComponentsConfiguration
string
(string composed of R, G, B, Y, Cb and Cr)
'Compression'
CompressionRatio
rational32u
'ImageSize'
ImageSize
int16u[n]
(2 or 3 values, for number of XY or XYZ pixels)
'OriginalImageSize'
OriginalImageSize
int16u[n]
(size of original image before cropping)
'Resolution'
Resolution
rational64u[n]
(1 to 3 values. A single value for equal resolution in all directions, or
separate X, Y and Z values if necessary. Units are '/in' unless '/cm',
'/deg', '/arcmin', '/arcsec' or '' specified)
