Information technology — JPEG 2000 image coding system: Interactivity tools, APIs and protocols — Part 9: — Amendment 3: JPIP extensions to 3D data

Technologies de l'information — Système de codage d'images JPEG 2000: Outils d'interactivité, interfaces de programmes d'application et protocoles — Partie 9: — Amendement 3: Extensions JPIP aux données 3D

General Information

Publication Date
Current Stage
Ref Project


Buy Standard

ISO/IEC 15444-9:2005/Amd 3:2008 - JPIP extensions to 3D data
English language
5 pages
sale 15% off
sale 15% off

Standards Content (Sample)

STANDARD 15444-9
First edition
Information technology — JPEG 2000
image coding system: Interactivity tools,
APIs and protocols
AMENDMENT 3: JPIP extensions to 3D data
Technologies de l'information — Système de codage d'images
JPEG 2000: Outils d'interactivité, interfaces de programmes
d'application et protocoles
AMENDEMENT 3: Extensions JPIP aux données 3D

Reference number
ISO/IEC 15444-9:2005/Amd.3:2008(E)
ISO/IEC 2008
ISO/IEC 15444-9:2005/Amd.3:2008(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO/IEC 2008
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
Published in Switzerland
ii © ISO/IEC 2008 – All rights reserved

ISO/IEC 15444-9:2005/Amd.3:2008(E)

1) Subclause 3.3. 1
2) Subclause 3.4. 1
3) Subclause A.3.2.1. 1
4) Subclause C.4.1. 1
5) Subclause C.4.1. 2
6) Subclause C.4.5. 3
7) Subclauses C.4.6 and C.4.7. 3
8) Subclause C.4.5. 4
9) Subclause C.4.7. 4
10) Subclause C.4.11. 4
11) Subclause D.2. 4

© ISO/IEC 2008 – All rights reserved iii

ISO/IEC 15444-9:2005/Amd.3:2008(E)
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 3 to ISO/IEC 15444-9:2005 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information, in conjunction with ITU-T. The identical text is published as ITU-T
Rec. T.808 (01/2005)/FDAM 3(E).

iv © ISO/IEC 2008 – All rights reserved

ISO/IEC 15444-9:2005/Amd.3:2008 (E)
Information technology – JPEG 2000 image coding system:
Interactivity tools, APIs and protocols
Amendment 3
JPIP extensions to 3D data
1) Subclause 3.3
Add the following item:
3.3.23 slice: A subset of voxels in a volumetric image with constant Z coordinates.
2) Subclause 3.4
Add the following items:
fz z-axis frame size for client request view-window
fz' z-axis frame size for suitable codestream resolution
fz'' modified jpx z-axis frame size for suitable resolution
oz z-axis offset for client request view-window
oz' z-axis offset for suitable codestream/component region
oz'' modified z-axis offset for suitable region
sz z-axis size of client request view-window
sz' z-axis size for suitable codestream region
sz'' modified jpx z-axis size for suitable region
3) Subclause A.3.2.1
After the third paragraph, add the following:
For volumetric images encoded in JP3D (Rec. ITU-T T.809 | ISO/IEC 15444-10), the sequence number of precincts
within a tile-component is computed as follows: All precincts of the lowest resolution level, i.e., those containing only
the [L|X][L|X][L|X] samples are sequenced first, starting from zero, following a raster scan order as defined by 3.11 of
Rec. ITU-T T.809 | ISO/IEC 15444-10. The precincts from each successive resolution level are sequenced in turn, again
following the raster scan order of 3.11. The precinct with sequence number 0 thus refers to the front most, upper left
hand precinct of the lowest resolution sub-band of the image component 0 in tile 0.
4) Subclause C.4.1
Replace the third paragraph with:
Codestream image regions are described using 3 n-dimensional parameters where n is the number of dimensions
required to describe this image. The size parameters and offset parameters specify the extent and location of the desired
codestream image region with respect to a whole image that has the given frame size. Figure C.1 demonstrates this
set-up for regular images with n = 2, but the construction carries over naturally to a higher number of dimensions. For
the rest of this subclause, we will consider only this case, naming the frame size fx and fy, the offset of the region ox
and oy and its size sx and sy as indicated in Figure C.1.
Rec. ITU-T T.808 (2005)/Amd.3 (06/2008) 1

ISO/IEC 15444-9:2005/Amd.3:2008 (E)
5) Subclause C.4.1
At the end of C.4.1, add the following:
The above considerations for two dimensional images carry over naturally to images of higher dimensionality, e.g., to
the case n = 3 where a third coordinate is added to each group of parameters. Specifically, the frame size is then
represented by three numbers fx, fy and fz, the offset by ox, oy and oz and the region size by sx, sy and sz. In that case,
Equation C-1 extends to:
⎡ZOsiz⎤ ⎡Zsiz⎤
ZOsiz′ = Zsiz′ =
⎢ ⎥ ⎢ ⎥
r r
⎢ 2 ⎥ ⎢ 2 ⎥
where ZOsiz and Zsiz specify the original image offset and canvas size in the Z direction, respectively. Equation C-2
extends to:
⎢ fz′ ⎥ fz′
⎛ ⎞ ⎡ ⎤
oz′ = oz ⋅ sz′ = (sz + oz)⋅ − oz′
⎜ ⎟
⎢ ⎥
⎢ ⎥
fz fz
⎝ ⎠ ⎢ ⎥
⎣ ⎦
For images represented within Rec. ITU-T T.809 | ISO/IEC 15444-10 codestream, ZOsiz and Zsiz are taken from the
relevant NSI marker segment.
In addition, a server may choose to identify a Rec. ITU-T T.801 | ISO/IEC 15444-2 codestream making use of wavelet
transformations as a multi-component transformation with a volume image using generated components to represent the
third (Z) dimension. The identification by which generated components constitute which slice is then at the discretion of
the server, and so is the choice of suitable values for ZOsiz and Zsiz. In this situation, clients may either choose to use
the two-dimensional or three-dimensional request syntax to fetch data from the client. For two-dimensional requests, it
is up to the client to identify slices with components and make the necessary requests; for three-dimensional requests, it
is the duty of the server to find the relevant components for the requested image volume. In the latter case, servers are
not required to honour the comp and mctres fields, see C.4.5 and C.4.11, and their usage is discouraged in this case.
Application Note:
In case servers have to identify a Rec. ITU-T T.801 | ISO/IEC 15444-2 encoded image with volumetric data, they are
recommended to use the following choices for ZOsiz and Zsiz to provide an efficient and consistent definition of
resolution levels in the Z direction:
• ZOsiz shall be taken identical to the minimum of all Omcc values in all MCC markers within the
codestream identified by the request, see Annex A.3.8 of Rec. ITU-T T.801 | ISO/IEC 15444-2. This
choice ensures a reasonable definition of the resolution levels in the Z direction compatible to the origin
of the wavelet transformation, and eases the extraction of lower-resolution images from the stream.
• Zsiz is to be taken identical to the number of slices identified by methods described below plus ZOsiz as
computed by the procedure above.
It is recommended to use the following procedure to identify the generated components that make up a slice in case a
Rec. ITU-T T.801 | ISO/IEC 15444-2 conforming file format is available for the target of the request:
• Identify all compositing layers of the file that use the codestream the request targets at. Each compositing
layer in this set defines exactly one slice of the volumetric image. The Z coordinate to be assigned to the
first compositing layer in this set is to be ZOsiz, as defined above, and all following slices are assigned
continuously ascending Z coordinates in the order they appear in the file.
• Within each compositing layer, scan for a channel definition box. If there is a channel definition box,
identify the channels that are associated to a colour by testing the Asoc field of the cdef box for that
channel and perform the next step. Otherwise, apply the next step to all channels.
• Identify within the compositing layer the generated components providing the data for the channels
found in the step above. For direct mapping, this is a 1:1 relation, but for palette mapped images, the
component mapping box must be parsed.
If no Rec. ITU-T T.801 | ISO/IEC 15444-2 conforming file format is available, other metadata outside the scope of this
Recommendation | International Standard might be available to identify which generated components define which
slice. In this case, servers are expected to use whatever metadata is available and be consistent with the specifications
made there.
2 Rec. ITU-T T.808 (2005)/Amd.3 (06/2008)

ISO/IEC 15444-9:2005/Amd.3:2008 (E)
In case no additional meta-data, neither inside 15444 nor outside of it, is available, the following algorithm can be used
as a last resort to come to a reasonable definition of slices:
A codestream is identified as grey scale volume image if each generated component is reconstructed by exactly one
transformation stage in the sense of Annex J of Rec. ITU-T T.801 | ISO/IEC 15444-2, and if that type of the
transformation stage is a wavelet transformation. A codestream is identified as colour volume image, if each generated
component is reconstructed by exactly two transformation stages of which the first one, which is applied to the spatial
components of the codestream, is a wavelet transformation, and of which the second one is not a wavelet
transformation, but a decorrelation or dependency transformation. All other set-ups cannot be handled.
The Z coordinate of the slice a generated component contributes to is identified as follows: For generated component g,
identify the MCC marker MCC that describes the wavelet transformation step taken to compute g from the spatial
components of the canvas system. According to the above definition, there should be exactly one such marker. If the
image is a grey-scale image, find the index j in the output component collection of that marker such that Wmcc
equals g, i.e., find the output slot in the transformation generating this component. Then generated component g
contributes then to the slice with Z = j + Omcc. This will define a Z coordinate for the component g based on the
ordering of the output of the wavelet transformation step.
For colour images, first identify all intermediate input components of the dependency or decorrelation transformation
required to reconstruct the generated component g, and find for each of them its Z coordinate as described above. It is
required that this Z coordinate does not depend on which of the intermediate components required to reconstruct
generated component g has been chosen; otherwise, this algorithm fails.
6) Subclause C.4.5
Insert the following after C.4.4 and update the following subclause numbers accordingly:
C.4.5 Frame size for variable dimension data (fvsiz)
fvsiz = "fvsiz" "=" 1#UINT ["," round-direction]
round-direction = "round-up" / "round-down" / "closest"
This request takes a variable number of arguments. There shall be as many numerical arguments as there are dimensions
in the source codestream. Specifically, if the

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.