US 200700.97230A1 (19) United States (12) Patent Application Publication (10) Pub. No.: US 2007/0097230 A1 Parulski et al. (43) Pub. Date: May 3, 2007

(54) IMAGE FILE FOR STORING DIGITAL Related U.S. Application Data IMAGES AND ANCILLARY DATA VALUES USING MULTIPLE ENCOOING METHODS (63) Continuation of application No. 09/950,199, filed on Sep. 10, 2001, which is a continuation of application No. 09/028,682, filed on Feb. 24, 1998, now Pat. No. (76) Inventors: Kenneth A. Parulski, Rochester, NY 6,310,647. (US); Joseph Ward, Hilton, NY (US); George E. Lathrop, Dansville, NY Publication Classification (US); J. Scott Houchin, Rochester, NY (51) Int. Cl. (US); Eddie Jennings, Rochester, NY H04N 5/76 (2006.01) (US); Brett Vansprewenburg, (52) U.S. Cl...... 348/2312 Henrietta, NY (US) (57) ABSTRACT An image format for storing digital images within a baseline Correspondence Address: DCT compatible bitstream comprises entropy coded image Pamela R. Crocker data, a first application marker storing a first data value using Patent Legal Staff a first encoding method to convey a first information value Eastman Kodak Company related to the image, and a second application marker storing 343 State Street a second data value using a second encoding method to Rochester, NY 14650-2201 (US) convey the same said first information value related to the image. More specifically, the first application marker uses TIFF tags within an application marker and the second (21) Appl. No.: 11/564,867 application marker uses a FlashPix compatible structured storage stream, while the entropy coded data includes restart markers to define tile boundaries within the entropy coded (22) Filed: Nov. 30, 2006 image data.

DOS/FAT MAGE IMAGE | | IMAGE MASEa DIRECTORY FILES IFILE all IFILEIN 42 4.O s -- DIGITAL ST Lt. CAMERA MEMORY REMOVABLE 26 CARD MEMORY INTERFACE 8 2O CCD IMAGE A/D SENSOR CONVERTER

lens6 USER 32 BUTTON

COLOR LCD MAGE DISPLAY HOST HOST fr14 COMPUTER is r12 COMPUTER - 2 A? FLASHPIX -NON FLASHPIX OSPLAY ENABLED ENABLED MONITOR APPLICATIONS APPLICATIONS

PC - KEYBOARD PC + KEYBOARD MEMORY CARD MEMORYREADER CARD ill------5O READER L-----Fi f------Patent Application Publication May 3, 2007 US 2007/0097230 A1

|----F----–––––––––––––- 22O2 èJELÀ:E/\NOO

OBJVO„NAJOWEJW 8.EQW738

O9

US 2007/0097230 A1 May 3, 2007

IMAGE FILE FOR STORING DIGITAL MAGES tion, version 1.0, (Eastman Kodak Company, Sep. 11, 1996), AND ANCILLARY DATA VALUES USING which is available from Eastman Kodak Co. or at the MULTIPLE ENCOOING METHODS Eastman Kodak Co. Web site at www.kodak.com/go/flash pix, and is incorporated herein by reference. CROSS REFERENCE TO RELATED 0006 Unfortunately, because FlashPix is a relatively new APPLICATIONS format, many computer applications are not yet capable of 0001. This is a continuation of application Ser. No. reading FlashPix image files. On the other hand, most 09/950,199, filed Sep. 10, 2001 which is a continuation of applications are able to open images stored in “JPEG U.S. application Ser. No. 09/028,682, now U.S. Pat. No. interchange format” (JIF) files defined by the Baseline DCT 6,310,647 issued Oct. 30, 2001. (JPEG) version of ISO/IEC 10918-1, which is incorporated herein by reference. This standard allows “application mark FIELD OF THE INVENTION ers' to be included in the JIF bitstream. The data inside an application marker is ignored by applications that are not 0002 The invention relates generally to the field of familiar with the marker. A number of , and in particular to image file formats have been developed which use a single application marker developed for use with digital cameras and their applica segment to store ancillary data and a reduced-resolution tions. “thumbnail’ image. These image formats include JFIF, defined in “JPEG File Interchange Format Version 1.02 Sep. BACKGROUND OF THE INVENTION 1, 1992 C-Cube Microsystems”, the JPEG compressed ver 0003 Electronic still cameras typically capture, digitize, sion of Exif (Exchangeable image format) described in and store images on a removable memory device. Such as a “Digital Still Camera Image Proposal (Exif) PCMCIA or Compact Flash card. The images are stored on Version 1.0 Mar. 24, 1995 JEIDA/Electronic Still Camera the card in separate image files. Many different image file Working Group” and SPIFF, defined in “ITU-T Rec. T84, formats may be used. To increase the number of images Annex F Still Picture Interchange File Format, 1995”, stored per card, image compression is typically used to which are each incorporated herein by reference. reduce the file size. The most popular compression standard 0007 For example, Exif allows some camera-related is the JPEG (Joint Photographic Expert Group) baseline ancillary data, Such as the date and time, lens finumber, etc. DCT (discrete cosine transform) method, which compresses to be recorded using TIFF (Tag image file format) tags the image components (for example a luminance component within an application marker 1 (APP 1) segment in the JIF Y and two color difference components Cb and Cr) using bitstream. (TIFF is defined in the TIFF Revision 6.0, Jun. 3, 8x8 pixel blocks. 1992, by Adobe Corp. and available on the Web at http:// 0004. It is desirable for digital cameras to produce images www. Adobe.com, and incorporated herein by reference.) that can be easily transferred into other digital devices (e.g. Exif images can be opened by any computer application computers) for editing, display, transmission, archival Stor software that incorporates a JPEG reader. However, the age, and printing. This requires a standard image data ancillary data in the Exif file can only be accessed by format, not just standards for the physical and electrical applications designed specifically for Exif. When an Exif file compatibility of the removable memory card. The format is converted to a FlashPix file (e.g. by the Microsoft Picture.It should be Supported by popular application software, so that application), the information recorded using the TIFF tags is the user does not need to worry about whether the image typically ignored by the reader, since the FlashPix conver format is compatible with the various image-capable appli sion programs are typically not familiar with the structure of cations on their computer. the Exif application marker and therefore ignore it. Thus, the ancillary information is lost. If the FlashPix application was 0005. The “FlashPix” image format (defined in FlashPix familiar with the Exif application marker, it would need to Format Specification, version 1.0, (Eastman Kodak Com read each individual TIFF tag, decode the information pany, Sep. 11, 1996)) has been developed to serve as both an values from each tag (for example, one specific tag encodes “interchange' format between devices (e.g. cameras) and the camera f/number as a rational number value) and then applications (e.g. computer picture editing packages), and as re-encode the values using the encoding method specified by a “native' format for image editing that allows the images to FlashPix (which encodes the camera f/number as a real be easily and rapidly edited. This is accomplished using a number value, rather than a rational number value, for hierarchical, tiled image representation within a "structured example) Each resolution level of a FlashPix image is storage file. A FlashPix file contains the complete image “tiled into 64x64 pixel images, and stored as a group, or plus a hierarchy of several lower-resolution copies within 'stream” of these Small image sections. the same file. Images at each resolution also are divided into rectangular tiles (e.g., squares), which enable the application 0008. However, the baseline DCT JPEG standard does to minimize the amount of image data processed to access, not allow the image data to be stored in tiles. Instead, the display or print a portion of the scene content. FlashPix data is stored as a single image record, by encoding all of the allows optional “ancillary” data to be stored in the same image blocks from left to right and top to bottom into a structured storage file, along with the image data. This single data record. Therefore, to convert an Exif or other JIF ancillary data can include digital audio recordings and compatible file format to a FlashPix image, the full resolu parameters such as the time and date the photo was taken, tion image is normally decompressed, tiled, and then recom the camera Zoom position and focus distance, the scene pressed. This process takes time, and may add compression illumination level, camera calibration data, image copyright artifacts. owner, etc. For further information about the FlashPix image 0009 What is needed is an image file format that is format see the aforementioned FlashPix Format Specifica completely compatible with the Baseline DCT (JPEG) ver US 2007/0097230 A1 May 3, 2007

sion of ISO/IEC 10918-1, so that it can be opened by all aspects of the present description may be implemented in existing “JPEG' enabled software applications, yet can be software. Unless otherwise specified, all software imple quickly and easily converted to the FlashPix format, so that mentation is conventional and within the ordinary skill in the new applications can take advantage of the tiling and programming arts. ancillary information capabilities offered by FlashPix. 0023 The invention is an image file format developed to SUMMARY OF THE INVENTION be compatible with or easily transcodable to multiple image 0010. The present invention is directed to overcoming formats. The format follows the Baseline DCT (“JPEG') one or more of the problems set forth above. Briefly sum version of ISO/IEC 10918-1, so that it can be opened by marized, according to one aspect of the present invention, existing “JPEG' enabled software applications such as there is provided a single digital image file, comprising: Microsoft Word for Windows, , etc. In addition, it can include application markers for both Exif and 0.011) a) entropy coded image data provided by process SPIFF, two different JPEG interchange format (JIF) based ing a digital image captured by a ; image formats. Furthermore, it includes features that allow 0012 b) a first ancillary data value using a first encoding easy transcoding to the FlashPix image format. Such as: (1) method to convey a first information value related to the an application marker segment that includes the “Image Info digital image captured by the digital camera; and Property Set' defined in the FlashPix standard, so that this data can be copied into the FlashPix file. (2) restart markers 0013 c) a second ancillary data value, different from said that define 64x64 tile segments added to the entropy coded first ancillary data value and encoded using a second encod image, so that the entropy coded Baseline DCT full size ing method, different from said first encoding method, image can be converted into the proper size tiles required by wherein the second ancillary data value conveys the same the FlashPix image format without decompression. said first information value. 0024. A system block diagram according to the invention 0014) Another aspect of the present invention is to pro is shown in FIG. 1 of a digital still camera 10 and respective vide a memory for storing digital image files, comprising: first and second host computers 12 and 14. Images are 0015 a) a plurality of digital image files, and captured through a lens 16 by a CCD sensor 18, converted to digital image data by an A/D converter 20, processed by 0016 b) a directory that indicates where the data for each a programmable processor 22, and stored on a removable of the plurality of digital image files is stored on the memory memory card 24 via an interface 26. The card 24 stores a card, wherein each of the plurality of digital image files single file 40 for each digital image (image #1, image #2, . comprises: . . image #N) and a directory 42 that indicates how many 0017) i) entropy coded image data; image files 40 exist on the card 24, and where the data for each file is located. The memory card 24 can then be 0018 ii) a first ancillary data value using a first encod removed from the camera and inserted into card readers 50 ing method to convey a first information value related in the host computers 12 and 14 where an image can be to the digital image captured by the digital camera; and edited, displayed, printed, transmitted, etc using various 0019 iii) a second ancillary data value, different from Software applications. Some of these computer applications, said first ancillary data value and encoded using a e.g., the host computer 12, may be capable of reading second encoding method, different from said first FlashPix and JIF files, while others, e.g., the host computer encoding method, wherein the second ancillary data 14, may be capable of only reading JIF files. value conveys the same said first information value. 0025. Each of the image files 40 is organized as shown in 0020. These and other aspects, objects, features and TABLE 1. The SOI, DQT, DHT, SOF SOS, and EOI advantages of the present invention will be more clearly markers, which are all well known since they are defined in understood and appreciated from a review of the following ISO/IEC 10918-1, comprise the following: detailed description of the preferred embodiments and appended claims, and by reference to the accompanying TABLE 1. drawings. Image File BRIEF DESCRIPTION OF THE DRAWINGS SOI (Start of Image) 0021 FIG. 1 is a block diagram of a digital imaging APP8 segment system including a digital camera that generates a multi (SPIFF fixed data) format compatible image file format according to the inven APP 1 segment tion. (ExifTIFF tags, plus additional TIFF/EP tags, Kodak camera.Info tags DETAILED DESCRIPTION OF THE and TIFF thumbnail) INVENTION APP2 segments (FlashPix standard 0022. Because imaging systems and formats are well image data area and known, the present description will be directed in particular Image Info Property Set) DQT to elements forming part of, or cooperating more directly (Quantization Table) with, systems and formats in accordance with the present DHT invention. Elements not specifically shown or described (Huffman Table) herein may be selected from those known in the art. Many US 2007/0097230 A1 May 3, 2007

0.031) Three components (Y. Cr. Cb) TABLE 1-continued 0032 Crand Cb subsampling (Crand Cb have / as many Image File lines and pixels per line as Y) SOF 0033) Which quantization table is used for Y. Cb, and Cr. (Start of Frame) SOS TABLE 3 (Start of Scan) Entropy Coded Data Exif application marker Y. Cb, Cr 4:1:1 data derived from SRGB APP1 Marker = 0x FEE EOI APP1 Length (End of Image) Exif Identifier & Pad TIFF Header IFD 0 describing JPEG Compressed Image Number of directory entries image:Description 1. SOI (Start of Image) is the marker code “FFD8” which Make, etc. defines the beginning of the file. ExifIFD Tag Pointer Next IFD Offset 0026. 2. The SPIFF marker is defined in the reference Exif Private IFD Number of directory entries cited earlier. The format of this marker segment is shown in Exif Version Table 2. DateTimeOriginal etc. Next IFD Offset TABLE 2 IFD 1 describing Thumbnail Image (mage Width image Length SPIFF application marker BitsPerSample Compression Type PhotometricInterpretation Parameter and size Value StripOffsets SamplesPerPixel MN (magic number) I.32 XFFD8FFE8(includes SOI) RowsPerStrip HLEN (header length) I.16 28 (Not including MN) StripByteCounts IDENT (SPIFF identifier) I.32 X53504600 XResolution VERS (Version) I.16 XO100 YResolution P (Profile) I.8 XO1 (Continuous tone) Resolution Unit C (Compression type) I.8 X*05 (JPEG continuous tone) Next IFD Offset S (Color space) I.8 X-03 (JFIF color) Thumbnail Image data (1 strip RGB image R (Resolution units) I.8 XO1 (dots per inch) data) HEIGHT I.32 Lines in luma input image WIDTH I.32 Pixels per line in luma input image WRES I.32 72 dots HRES I.32 72 dots 8. SOS (Start of Scan) is a marker code segment that begins with “FFDA’. It provides the following parameter informa tion: 3. The Exif marker is defined in the reference cited earlier. 0034 Indicates that there are three components in the The format of this marker segment is shown in Table 3. SCa 4. The FlashPix Image Info Property Set marker is defined 0035) Indicates which Huffman tables are used for Y. Cb, later in this document. and Cr. 5. DQT (Define Quantization Table) is a marker code 0036 9. The Entropy Coded Data is tiled as shown in segment that begins with “FFD9 which defines the begin Table 5. Each 64x64 pixel (4096 pixel) tile includes an 8x8 ning of the quantization tables used for JPEG compression. group (64 total) of luminance DCT blocks and 4x4 group Three kinds of tables are included, one for luminance (Y) (16 total) Cb and Cr chroma DCT blocks. Each macroblock and one for each of the two color difference signals Cb and consists of 4 luminance and 1 each Cb and Cr chrominance Cr. blocks. Therefore, restart markers are placed after appropri 6. DHT (Define Huffman Table) is a marker code segment ate groups of macroblocks. that begins with “FFC4” which defines the Huffman Tables 10. EOI (End of Image) is the marker code “FFD9” which used for JPEG compression. Within the DHT, four sets of defines the end of the file. parameters are recorded. These are the DC and AC tables for Y and C, respectively. FPXR Application Segments 7. SOF (Start of Frame) is a marker code segment that begins 0037 All FPXR (FlashPix ready) application segments with “FFCO. It provides the following parameter informa have a similar structure. This structure is depicted in Table tion: 4. It consists of a 2-byte APP2 marker followed by a 2-byte segment length (L) value stored in big endian format. The 0027 Indicates baseline JPEG compression is used initial 4 bytes follow the application marker specification in ISO/IEC 10918-1. Following this is 5 bytes consisting of a 0028 Sample precision in bits NULL-terminated string “FPXR.” The next byte is a version number. The next byte is a type followed by a series of L-9 0029) Number of vertical lines in the Y image bytes whose format depends on this type. Bytes 0 through 10 0030 Number of horizontal pixels in the Y image are referred to as the FPXR segment header. US 2007/0097230 A1 May 3, 2007

TABLE 4 TABLE 5-continued FPXRApplication Segment. FPXR Standard Image Data Area. Offset Value Description Offset Value Description 21

0xFF Marker for APP2 22 Offset to start OXE2 23 of JPEG SOF header Segment length = L 24 (big endian) FPXR 25 Segment 26 Offset to start of JPEG “FPXR Header 27 compressed data 28

String NULL terminator Version (must be zero) 0040. The valid values for color space are: 10 FPXR type 11 FPXR data area (format depends on FPXR type) - L-9 bytes in length L + 1 Value Description OxO3 NIFRGB OxO1 Monochrome Note that the segment length, L, is a 16-bit number. There fore, the maximum size allowed in any one FPXR data area is 65526 bytes. 0041. These values are consistent with their definitions in the FlashPix specification. The chroma subsampling value is 0038. The valid values for FPXR types are: stored exactly as in the tile header table of the Subimage Header Stream of the FlashPix file. The valid values are:

Value Description of FPXR Data Area Required Optional OxOO Standard Image Data required Value Horizontal Subsampling Ratio Vertical Subsampling Ratio OXO1 Contents List optional OxO2 Stream data optional Ox11 1 1 Ox21 2 1 Ox22 2 2 The exact format of the various FPXR data areas will be described in the following sections. 0042. In the case of monochrome, the subsampling value FPXR Standard Image Data Area is not meaningful and is set to Zero. 0039 Each image file contains (as the first FPXRAPP2 segment) a single FPXR standard image data segment 0043. In addition, there are three file offsets (measured in (FPXR type 0x00). In some cases, a digital camera could bytes from the beginning of the FPXR file) to aid the create an image file which has no other FlashPix specific application in putting together pieces of the FPXR file to data. This single segment serves to establish that the file form the abbreviated JPEG header table in the Compression includes restart markers that define the tile boundaries, as Description Group of the Image Contents Property Set of the described later. The format of the standard image data area FlashPix file and also to build tile headers. Each of these is defined in Table 5. Even though these values are embed offsets are stored in 32-bit unsigned integer (big endian). ded in the JPEG stream, they are repeated here for the The first offset is the address of the first byte of the DQT convenience of the application reading the FPXR file. header in the FPXR file. The second offset is the address of the first byte of the SOF header in the file. The last offset is TABLE 5 the address of the first byte of the actual compressed data FPXR Standard Image Data Area. (i.e., following the SOS segment). Offset Value Description FPXR Contents List Data Area 11 Pixel X dimension 0044) The image file may also include an FPXR contents 12 (# pixels per line) 13 Pixel Y dimension list segment (FPXR type 0x01). This segment contains a list 14 (# lines) of streams that are to be added to the FlashPix image object 15 Color space created from the JIF file. Since property sets, such as the 16 Chroma Subsampling 17 FlashPix Image Information Property Set, are special cases 18 Offset to start of streams, they are easily handled via this mechanism. 19 of JPEG DQT header 2O 0045. The format of the FPXR contents list data area is defined in Table 6 below. US 2007/0097230 A1 May 3, 2007

would be Zero. In other cases, the stream data is separated TABLE 6 across multiple FPXR segments all of which have the same “index number (and each having different offset numbers). FPXR Contents List Data Area. Creating Property Sets Offset Value Description 0051. The binary format for property sets is contained in 11 Number of entries 12 =N section A.2 of the aforementioned FlashPix Specification. To 13 Name/size pairs - include this information within a JIF compatible file, the one pair for each FPXR stream data area of the application segment (i.e., entry starting at byte 17 in the segment) contains the binary content of a property set. A property set consists of a Property Set Header followed by a Property Set Format 0046) The number of entries, N, is a 16-bit unsigned ID/Offset Pair followed by the one and only one Property Set integer in big endian format defining how many streams are Section containing the actual properties. The Property Set to be added to the FlashPix image object. For each of these Header is a fixed size array (28 bytes) containing constants entries, a pair is provided giving the name of the stream to values (per property set). The Format ID/Offset Pair is a create and the size (in bytes) of the stream data. These pairs fixed size array (20 bytes) also containing constant values are packed tightly in the bytes of the file starting at offset 13 (per property set). Therefore, the only variable portion is that in the FPXR segment. Each pair has an associated index of the section. number (0, 1,..., N-1) that is implicitly derived from its position in the array of pairs. 0.052 The format of a Property Set Section follows the conventions of Appendix A of the FlashPix Specification. A 0047 The first member of each name/size pair is a section consists of a Section Header, followed by an array of WCHAR (16-bit per character, null-terminated string in the Property ID/Offset Pairs, followed by an array of Property Unicode code page) containing the name of the FlashPix Type/Value pairs. The section header contains two stream to create. The stream includes a complete pathname DWORDs (i.e., 32-bit integer values). The first DWORD is specification relative to the FlashPix image object storage, the size of the section (in bytes). The second DWORD is the for example “\005Summary Information. The second mem count of properties, m, contained in the section. ber of each name/size pair specifies the size (in bytes) of the stream that is being created. 0053 Immediately following the header is an array of m pairs. Each pair consists of two DWORDs. The first FPXR Stream Data Area DWORD in a pair contains a Property ID (PID). The second 0.048 For every entry in the FPXR contents list segment, DWORD contains the offset within the section to the first there are 1 or more FPXR stream data segments that define byte of the type/value pair for the property with the PID the contents of the streams to be created. Since APPn specified in the first DWORD. These offsets are measured in segments are limited to a size of 64K bytes each, it is bytes from the start of a section to the start of the type/value possible that stream data might be split across multiple pair. This means that the offsets can be copied directly from FPXR segments (e.g., an audio extension). Therefore, the the FPXR application segment into a structured storage file FPXR stream data segment provides a mechanism for such property set without any recalculation of offsets. This array splitting. of pairs is not required to be sorted in any particular order (i.e., the PIDs are in any order chosen by the writer). The 0049. The format of the FPXR stream data area is defined PIDs that are allowed to be contained in the array are those in Table 7 below. defined by the corresponding property sets in the FlashPix format. TABLE 7 0054 Immediately following the PID/offset array is a FPXR Stream Data Area. “list of m pairs. Each pair consists of a DWORD type indicator and the value for a particular property. The value Offset Value Description is variable size in length as dictated by the type indicator. All 11 Index in contents type/value pairs begin on a 32-bit boundary in the section. 12 list The possible types are given in Table 8 below. 13 14 Offset to start 15 of data in full FlashPix TABLE 8 16 Stream 17 Stream data Property Types Type Name Type Value 0050. The first entry is a 16-bit unsigned integer that VT I2 2 VT I4 3 specifies the index number from the contents list that this VT R4 4 stream data corresponds to. The second entry is a 32-bit VT R8 5 unsigned integer that specifies the offset (measured in bytes, VT DATE 7 VT BOOL 11 relative to Zero) into the full FlashPix stream where the VT VARIANT 12 following data belongs. The size of the stream data in a VT I1 16 particular FPXR stream data area is L-15 bytes (where L was VT UI1 17 defined as in Table 5). In the most simple case, a stream VT UI2 18 completely in one FPXR segment, and the offset value US 2007/0097230 A1 May 3, 2007

0065. 14 second host computer TABLE 8-continued 0.066 16 lens Property Types 0067. 18 CCD sensor Type Name Type Value 0068. 20 A/D converter VT UI4 19 0069) 22 programmable processor VT I8 2O VT UI8 21 0070 24 removable memory card VT INT 22 VT UINT 23 0.071) 26 interface VT LPSTR 30 VT LPWSTR 31 0072 28 image memory VT FILETIME 64 VT BLOB 65 0.073 30 color LCD display VT CF 71 VT CLSID 72 0074) 32 user button VT VECTOR Ox1OOO VT ARRAY Ox2OOO 0075 40 file 0.076 42 directory 0.055 The data formats corresponding to each of the 0.077 50 card reader property types are contained in section A.2.3 of the FlashPix Specification. What is claimed is: JPEG Restart Markers 1. A single digital image file, comprising: 0056. The compressed image data in the JPEG stream a) entropy coded image data provided by processing a must contain restart markers (RST) at the beginning of every digital image captured by a digital camera; JPEG block that begins a new 64-pixel boundary. The b) a first ancillary data value using a first encoding method number of minimal coding units (MCUs) that this corre to convey a first information value related to the digital sponds to varies depending on the chroma Subsampling and image captured by the digital camera; and component interleaving methods being applied. c) a second ancillary data value, different from said first 0057. An MCU block is comprised of the total number of ancillary data value and encoded using a second encod MCUs necessary to encode all Supplied components accord ing method, different from said first encoding method, ing to their sampling factor and interleaving method. All wherein the second ancillary data value conveys the components are interleaved in FPXR files. same said first information value. 0.058. In the case of chroma subsampling value 0x11 2. A single digital image file as claimed in claim 1 wherein (horizontal and vertical Subsampling ratios of 1), there are 3 the first data value is encoded using a TIFF tag, and the MCUs per each 8x8-pixel block (no subsampling therefore second data value is encoded using a second encoding no reconstruction). Therefore, the RST markers occur every method other than TIFF tags. 8 MCU blocks (24 MCUs). 3. A single digital image file as claimed in claim 1 wherein 0059 For a chroma subsampling value of 0x22 (H/V the entropy coded image data is discrete cosine transform ratios of 2), there are 6 MCUs per each 16x16 pixel block compressed data. (after reconstruction is performed). Therefore, the RST 4. A single digital image file as claimed in claim 1 wherein markers occur every 4 MCU blocks (24 MCUs). the first data value is encoded using a TIFF tag, and the 0060 For a chroma subsampling value of 0x2 1 (Hori second data value is encoded using a second encoding Zontal Subsampling ratio of 2, Vertical of 1), there are 4 method other than TIFF tags. MCUs per each 16x8 pixel block (after reconstruction is 5. A single digital image file as claimed in claim 1 wherein performed). Therefore, the RST markers occur every 4 MCU the first information value provides an image capture date of blocks (16 MCUs). the digital image captured by the digital camera. 6. A single digital image file as claimed in claim 1 wherein 0061 The locations specified above for RST markers are the first information value provides a camera parameter. the only ones included in a file containing the FPXR 7. A single digital image file as claimed in claim 1 wherein application marker. In other words, a reader application that the first information value provides a camera lens Zoom senses that a JIF file is in fact an FPXR file can safely position. assume that the only RST markers that will be encountered 8. A single digital image file as claimed in claim 1 wherein in the JPEG stream are those that are placed according to the the first information value provides a camera lens focus above rules to facilitate the tiling of the FlashPix data. distance. 0062) The invention has been described with reference to 9. A single digital image file as claimed in claim 1 wherein a preferred embodiment. However, it will be appreciated that the first information value provides an image copyright variations and modifications can be effected by a person of owner of the digital image captured by the digital camera. ordinary skill in the art without departing from the scope of 10. A single digital image file as claimed in claim 1 the invention. wherein the first information value provides a description of PARTS LIST the digital image captured by the digital camera. 0063) 10 digital still camera 11. A memory for storing digital image files, comprising: 0064. 12 first host computer a) a plurality of digital image files, and US 2007/0097230 A1 May 3, 2007

b) a directory that indicates where the data for each of the 14. A memory as claimed in claim 11, wherein the first plurality of digital image files is stored on the memory data value is encoded using a TIFF tag, and the second data card, wherein each of the plurality of digital image files value is encoded using a second encoding method other than comprises: TIFF tags. i) entropy coded image data; 15. A memory card claimed in claim 11, wherein the first ii) a first ancillary data value using a first encoding information value provides an image capture date of the method to convey a first information value related to digital image captured by the digital camera. the digital image captured by the digital camera; and 16. A memory as claimed in claim 11, wherein the first iii) a second ancillary data value, different from said information value provides a camera parameter. first ancillary data value and encoded using a second 17. A memory as claimed in claim 11, wherein the first encoding method, different from said first encoding information value provides an image copyright owner of the method, wherein the second ancillary data value digital image captured by the digital camera. conveys the same said first information value. 18. A memory as claimed in claim 11, wherein the first 12. A memory card claimed in claim 11, wherein the first information value provides a description of the digital image data value is encoded using a TIFF tag, and the second data captured by the digital camera. value is encoded using a second encoding method other than TIFF tags. 19. A memory as claimed in claim 11, wherein the 13. A memory as claimed in claim 11, wherein the entropy memory is a removable memory card. coded image data is discrete cosine transform compressed data.