ISO/IEC 23090-35

• Abstract:

  This document provides accompanying reference software for ISO/IEC 23090-30. The software is an integral part of this document. The use of this reference software is not required to make an implementation of an encoder or decoder in conformance to ISO/IEC 23090-30. Requirements established in ISO/IEC 23090-30 take precedence over the behaviour of the reference software. This document also specifies a set of tests and procedures designed to indicate whether encoders or decoders meet the normative requirements specified in ISO/IEC 23090-30.

• Status: Not Published
• ICS: 35.040.40 - Coding of audio, video, multimedia and hypermedia information
• Technical Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Drafting Committee: ISO/IEC JTC 1/SC 29/WG 7 - MPEG 3D Graphics coding
• Current Stage: 6000 - International Standard under publication
• Start Date: 07-Aug-2026
• Completion Date: 31-Oct-2026

ISO/IEC 23090-35 is an ISO/IEC standard for conformance and reference software for low latency, low complexity LiDAR coding (L3C2). It accompanies ISO/IEC 23090-30 and provides reference encoder and decoder software, plus test procedures and reference bitstreams, for people implementing or verifying conformant LiDAR coding systems. In practice, it helps developers, test labs, and quality teams check whether an encoder or decoder follows the coding specification.

What does ISO/IEC 23090-35 specify?

ISO/IEC 23090-35 specifies accompanying reference software and conformance testing for ISO/IEC 23090-30. The document is organized into seven clauses: scope, normative reference, terms and definitions, abbreviated terms, conventions, reference software, and conformance testing.

The scope is practical: the software is part of the document, but using that software is not required to claim conformance. ISO/IEC 23090-30 takes precedence over the behaviour of the reference software, so implementers must follow the core coding standard first.

Clause 6 covers the reference software package, and Clause 7 covers the conformance tests and the bitstream test suites used to exercise encoder and decoder behaviour.

What are the key requirements of ISO/IEC 23090-35?

ISO/IEC 23090-35 turns the ISO/IEC 23090-30 coding specification into something that can be exercised and checked. The document’s main value is that it gives implementers reference code and a structured way to test bitstream and decoder conformance.

Reference software is provided as an aid, not as a substitute for the coding standard

Clause 1 and the Introduction state that the reference software accompanies ISO/IEC 23090-30 and is not required to make an encoder or decoder conformant. In practice, this means an implementation can be conformant without using the supplied software, as long as it follows the normative requirements in ISO/IEC 23090-30.

The software package supports Simple and Main profiles

Clause 6 says the reference software package contains one part, the mpeg-pcc-tml software, with support for Simple and Main profiles. The manual is mpeg-pcc-tml-sw-manual.pdf, which is used to install and operate the software. For implementers, this is the starting point for decoding, encoding, and reproducing the examples used in testing.

Bitstream testing uses the reference software decoder

Clause 7.1 states that the normative tests use test data and the reference software decoder. Clause 7.4 requires a claimed conformant bitstream to be decoded by the reference software decoder without errors or non-conformance messages. In practice, this gives users a strong check on syntax and decoding behaviour, although the document also says that passing this test is only a strong presumption of full conformance.

Decoder conformance is tied to profile and level

Clause 7.5.1 explains that conformance bitstreams are identified by values of main_profile_compatibility_flag and level_idc that correspond to the constraints expected for a decoder profile and level. This matters because decoder testing is not generic: a decoder must be checked against the profile and level combination it claims to support.

The conformance tests cover both output and process

Clause 7.5.3 points to Clause 8 of ISO/IEC 23090-30 for the output of the decoding process, and says rendering is outside the scope of this document. In practice, the document tests decoded point cloud output, not any later rendering or display stage.

The test bitstreams exercise a wide range of coding features

Clause 7.6 and Table 1 define the reference bitstream set. The test categories include common functionality, geometry coding, attribute coding, level-of-detail handling, predictor search, direct predictors, neighbour bias, spherical domain coding, and attribute neighbour blending filtering.

That breadth matters because implementers can check more than one narrow case. The suite includes examples for entropy bypass and continuation, slice/tile behaviour, geometry parameter sets, axis coding order, geometry scaling, onechain geometry coding, duplicate point handling, coarse neighbours, vertical prediction, low latency attributes coding, unordered points, sensing coverage signalling, quantization, scalable lifting, and multiple LoD methods.

What terms does ISO/IEC 23090-35 define?

ISO/IEC 23090-35 reuses the terms and definitions from ISO/IEC 23090-30 and adds a small set of its own.

• Bitstream - A sequence of bits representing compressed point cloud data in the syntax of a specific coding specification.
• Decoder - A process or device that reconstructs point cloud data from a structured conforming bitstream; the note says rendering is not included.
• Encoder - An embodiment of a process that produces a bitstream.
• Reference software decoder - A software implementation of the decoding process that reconstructs point cloud data from a conforming structured bitstream.
• Reference software encoder - A software implementation that compresses point cloud data into a conforming structured bitstream.

These terms matter because they separate the coding process from later rendering and from the reference implementations used for testing.

Who uses ISO/IEC 23090-35?

ISO/IEC 23090-35 is used by engineers implementing LiDAR encoders and decoders, and by teams validating them against ISO/IEC 23090-30. It is also relevant to quality managers, interoperability testers, and laboratories that need repeatable conformance checks.

Buyer and integration teams can use it to understand what a supplied encoder or decoder is expected to handle, especially around profile support, bitstream constraints, and reference test material. Developers can use the reference software and test bitstreams to compare their implementation against known behaviour.

Which standards are used with ISO/IEC 23090-35?

ISO/IEC 23090-35 cites ISO/IEC 23090-30 as its normative reference. ISO/IEC 23090-30 provides the core specification for low latency, low complexity LiDAR coding, including the coding process, the conformance rules, the output of decoding, and the terms, abbreviations, and conventions that ISO/IEC 23090-35 applies.

What does the ISO/IEC 23090-35 document contain?

ISO/IEC 23090-35 contains the reference software package, a manual for using it, and the normative conformance-testing framework for bitstreams and decoders. It also provides online access to the software and to the test bitstream suites used for verification.

The test material is organized by feature group, with named bitstreams under categories such as EBS, EC, ST, GPS, APS, ACO, GS, OGC, PLCS, DPOC, UNEOC, UCN, UVP, LLA, UPOC, SCS, GATT, QuantATT, LodRAHT, SLOD, NumLOD, DecLoD, DisLoD, CentLoD, SL, PSInterLOD, PSIntraLOD, NumPRED, DirectPRED, NB, LCP, ICP, RahtPRED, SDC, and ANBF. This structure helps test specific coding tools rather than only overall decoder output.

For each conformance bitstream, the zipped file includes the bitstream file, a readme, an optional configuration file, an MD5 checksum, and decoded point cloud outputs with their checksums. That package supports reproducible testing, debugging, and comparison between implementations.

FINAL DRAFT
International
Standard
ISO/IEC
FDIS
23090-35
ISO/IEC JTC 1/SC 29
Information technology — Coded
Secretariat: JISC
representation of immersive
Voting begins on:
media —
2026-06-11
Part 35:
Voting terminates on:
2026-08-06
Conformance and reference
software for low latency, low
complexity LiDAR coding
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/IEC FDIS 23090­35:2026(en) © ISO/IEC 2026

FINAL DRAFT
ISO/IEC FDIS 23090-35:2026(en)
International
Standard
ISO/IEC
FDIS
23090-35
ISO/IEC JTC 1/SC 29
Information technology — Coded
Secretariat: JISC
representation of immersive
Voting begins on:
media —
Part 35:
Voting terminates on:
Conformance and reference
software for low latency, low
complexity LiDAR coding
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO/IEC 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ISO/IEC FDIS 23090­35:2026(en) © ISO/IEC 2026

© ISO/IEC 2026 – All rights reserved
ii
ISO/IEC FDIS 23090-35:2026(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative reference . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Conventions . 2
6 Reference software for ISO/IEC 23090-30 . 2
7 Conformance testing for ISO/IEC 23090-30 . 2
7.1 General .2
7.2 Bitstream conformance .2
7.3 Decoder conformance .2
7.4 Procedure to test bitstreams .2
7.5 Procedure to test decoder conformance .3
7.5.1 Conformance bitstreams .3
7.5.2 Contents of the bitstream file .3
7.5.3 Requirements on output of the decoding process .3
7.5.4 Recommendations.3
7.6 Specification of the test bitstreams .4
7.6.1 General .4
7.6.2 Test bitstreams .5

© ISO/IEC 2026 – All rights reserved
iii
ISO/IEC FDIS 23090-35:2026(en)
Foreword
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.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/
IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
A list of all parts in the ISO/IEC 23090 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.

© ISO/IEC 2026 – All rights reserved
iv
ISO/IEC FDIS 23090-35:2026(en)
Introduction
0.1  General
This document specifies reference software and conformance testing for ISO/IEC 23090-30 low latency, low
complexity LiDAR coding (L3C2).
0.2  Purpose
The purpose of this document is to provide the following:
— Reference decoder software for decoding ISO/IEC 23090-30 compliant bitstreams.
— Reference encoder software for generating ISO/IEC 23090-30 compliant bitstreams.
— Procedures to test bitstream and decoder conformance.
— A set of reference bitstreams conforming to ISO/IEC 23090-30.
0.3  Examples of use
Some examples of uses that may be appropriate for the reference decoder software are as follows:
— As an illustration of how to perform the decoding process specified in ISO/IEC 23090-30.
— As the starting basis for the implementation of a decoder that conforms to ISO/IEC 23090-30.
— For testing the conformance of a decoder implementation with the decoding process specified in
ISO/IEC 23090-30.
— For testing the conformance of a bitstream to the constraints specified for bitstream conformance in
ISO/IEC 23090-30, as the software can detect and report many bitstream conformance violations.
NOTE The lack of the detection of any conformance violation by the reference decoder software is
not definitive proof that the bitstream conforms to all constraints specified for bitstream conformance in
ISO/IEC 23090-30.
Some examples of uses that can be appropriate for the reference encoder software are as follows:
— As an illustration of how to perform an encoding process that produces bitstreams that conform to the
constraints specified for bitstream conformance in ISO/IEC 23090-30.
— As the starting basis for the implementation of an encoder that conforms to ISO/IEC 23090-30.
— As a means of generating bitstreams for testing the conformance of a decoder implementation with the
decoding process specified in ISO/IEC 23090-30.
— As a means of evaluating and demonstrating examples of the quality that can be achieved by an encoding
process that conforms to ISO/IEC 23090-30.
NOTE No guarantee of the quality that will be achieved by an encoder is provided by its conformance to
ISO/IEC 23090-30, as the conformance of an encoder to ISO/IEC 23090-30 is defined only in terms of format
constraints imposed on the bitstream syntax. The reference encoder software provides some illustrative
examples of what quality can be achieved in conformance to ISO/IEC 23090-30, it doesn’t define minimum
encoding quality or maximum encoding quality.

© ISO/IEC 2026 – All rights reserved
v
FINAL DRAFT International Standard ISO/IEC FDIS 23090-35:2026(en)
Information technology — Coded representation of
immersive media —
Part 35:
Conformance and reference software for low latency, low
complexity LiDAR coding
1 Scope
This document provides accompanying reference software for ISO/IEC 23090-30. The software is an integral
part of this document.
The use of this reference software is not required to make an implementation of an encoder or decoder in
conformance to ISO/IEC 23090-30. Requirements established in ISO/IEC 23090-30 take precedence over the
behaviour of the reference software.
This document also specifies a set of tests and procedures designed to indicate whether encoders or
decoders meet the normative requirements specified in ISO/IEC 23090-30.
2 Normative reference
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 23090-30, Information technology — Coded representation of immersive media — Part 30: Low latency,
low complexity light detection and ranging (LiDAR) coding
3 Terms and definitions
For the purposes of this document, the terms and definitions in ISO/IEC 23090-30 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
bitstream
sequence of bits representing compressed point cloud data structured according to the syntax of a specific
coding specification
3.2
decoder
process or device that reconstructs point cloud data from a structured bitstream conforming to a specific
coding specification
Note 1 to entry: Decoder does not include the point cloud rendering process, which is outside the scope of this
document
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
3.3
encoder
embodiment of a process that produces a bitstream
3.4
reference software decoder
software implementation of the decoding process that reconstructs point cloud data from a structured
bitstream conforming to a specific coding specification
3.5
reference software encoder
software implementation that compresses point cloud data into a structured bitstream conforming to a
specific coding specification
4 Abbreviated terms
The abbreviated terms in Clause 4 of ISO/IEC 23090-30:2026 apply.
5 Conventions
The conventions specified in Clause 5 of ISO/IEC 23090-30:2026 apply.
6 Reference software for ISO/IEC 23090-30
Reference software is useful in aiding users of a compression standard to establish and test conformance
and interoperability, and to educate users and demonstrate the capabilities of ISO/IEC 23090-30:2026. The
reference software for ISO/IEC 23090-30:2026 is available at: https:// standards .iso .org/ iso -iec/ 23090/ -35/
ed -1/ en/ .
The software package contains one part:
— mpeg-pcc-tml software: Support for Simple and Main profiles.
The reference software manual is mpeg-pcc-tml-sw-manual.pdf. This manual can be used to install and use
the reference software.
7 Conformance testing for ISO/IEC 23090-30
7.1 General
The following clauses specify normative tests for verifying conformance of bitstreams as well as decoders.
Those normative tests make use of test data (bitstream test suites) provided are available at: https://
standards .iso .org/ iso -iec/ 23090/ -35/ ed -1/ en/ and the reference software decoder specified in Clause 6.
7.2 Bitstream conformance
Bitstream conformance follows the specification text in ISO/IEC 23090-30.
7.3 Decoder conformance
Decoder conformance for ISO/IEC 23090-30, such as conformance point, etc., is specified by clause 6.5.1 of
ISO/IEC 23090-30:2026.
7.4 Procedure to test bitstreams
A bitstream that claims conformance with ISO/IEC 23090-30 shall pass the following normative test.

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
The bitstream shall be decoded by processing it with the reference software decoder. When processed by
the reference software decoder, the bitstream shall not cause any error or non-conformance messages to be
reported by the reference software decoder. This test should not be applied to bitstreams that are known to
contain errors introduced by transmission, as such errors are highly likely to result in bitstreams that lack
conformance to ISO/IEC 23090-30.
Successfully passing the reference software decoder test provides only a strong presumption that the
bitstream under test does indeed meet all the requirements specified in ISO/IEC 23090-30 that are tested by
the reference software decoder.
ISO/IEC 23090-30 contains several informative recommendations that are not an integral part of
International Standard. When testing a bitstream for conformance, it may also be useful to test whether or
not the bitstream follows those recommendations.
To check correctness of a bitstream, it is necessary to parse the entire bitstream and to extract all the
syntax elements and other values derived from those syntactic elements and used by the decoding process
specified in ISO/IEC 23090-30.
A verifier may not necessarily perform all stages of the decoding process specified in ISO/IEC 23090-30 in
order to verify bitstream correctness. Many tests can be performed on syntax elements in a state prior to
their use in some processing stages.
7.5 Procedure to test decoder conformance
7.5.1 Conformance bitstreams
A bitstream has values of main_profile_compatibility_flag and level_idc corresponding to a set of specified
constraints on a bitstream for which a decoder conforming to a specified profile, and level is required in
Annex A of ISO/IEC 23090-30:2026 to properly perform the decoding process.
7.5.2 Contents of the bitstream file
The conformance bitstreams are included in this document and are available at: https:// standards .iso
.org/ iso -iec/ 23090/ -35/ ed -1/ en/ . The following information is included in a single zipped file for each such
bitstream.
— *.bit – bitstream as described in subclause 7.6.2
— readme.md – description
— *.cfg – config file used to generate bitstream with TML encoder SW (not applicable if TML encoder release
version not used)
— *.md5 – MD5sum of the bitstream file
— *_dec.ply – unordered decoded point cloud frames
— *_dec.ply.md5 – MD5 checksum for decoded point cloud frame
7.5.3 Requirements on output of the decoding process
The output of the decoding process is specified in Clause 8 of ISO/IEC 23090-30:2026.
The rendering process, which may follow the output of the decoding process, is outside the scope of this
document.
7.5.4 Recommendations
In addition to the requirements, it is desirable that conforming decoders implement various informative
recommendations specified in ISO/IEC 23090-30 that are not an integral part of ISO/IEC 23090-30. This
clause discusses some of these recommendations.

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
It is recommended that a conforming decoder be able to resume the decoding process as soon as possible
after the loss or corruption of part of a bitstream.
7.6 Specification of the test bitstreams
7.6.1 General
The test bitstreams are part of the mechanism to verify decoder conformance according to the
ISO/IEC 23090-30 specification. The bitstreams used for the decoder conformance testing specified in this
document shall be those listed in Table 1. They are available at: https:// standards .iso .org/ iso -iec/ 23090/
-35/ ed -1/ en/ .
Table 1 — List of reference bitstreams.
Categories Feature Name Features tested
Common functionality EBS Entropy bypass stream
EC Entropy continuation
ST Slice/Tile
GPS GPS (Geometry Parameter Set)
APS APS (Attribute Parameter Set)
ACO Axis coding order
Geometry coding GS Geometry scaling
OGC Onechain geometry coding
PLCS Preserve laser coding state
DPOC Duplicate points in onechain geometry coding
UNEOC Use NSensing estimation in onechain coding
UCN Use Coarse neighbours
UVP Use Vertical prediction
LLA Low latency attributes coding
UPOC Unordered points in onechain coding
SCS Sensing coverage signalling
Attribute coding GATT Generic attribute
QuantATT Quantization
LodRAHT Level of Details (LoD) and Region Adaptive Hierarchical Transform (RAHT)
SLOD Single LoD
NumLOD Number of LoDs
DecLOD LoD method: Decimation
DisLOD LoD method: Distance
CentLOD LoD method: Block-based
SL Scalable Lifting
PSInterLOD Predictor search: inter LoD
PSIntraLOD Predictor search: intra LoD
NumPRED Number of predictors
DirectPRED Direct predictors (Pred)
NB Neighbour bias
LCP Last component pred
ICP Predicting Transform: Inter component pred

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
TTabablele 1 1 ((ccoonnttiinnueuedd))
Categories Feature Name Features tested
RahtPRED RAHT prediction
SDC Spherical domain coding
ANBF Attribute neighbour blending filtering
7.6.2 Test bitstreams
7.6.2.1 Entropy bypass stream (EBS)
7.6.2.1.1 Test bitstream EBS_A_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— bypass_stream_enabled flag equal to 0.
— lowLatencyAttributesCoding equal to 1 (low latency attribute).
— attr_coding_type is equal to 4 (onechain).
Functional stage: Entropy bypass stream disabled and low latency attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.1.2 Test bitstream EBS_B_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— bypass_stream_enabled flag equal to 1
— lowLatencyAttributesCoding equal to 1 (low latency attribute)
— attr_coding_type is equal to 4 (onechain)
Functional stage: Entropy bypass stream enabled and low latency attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.3 Test bitstream EBS_C_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— bypass_stream_enabled flag equal to 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 0 (RAHT)
Functional stage: Entropy bypass stream enabled and RAHT attribute coding on Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.4 Test bitstream EBS_D_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— bypass_stream_enabled flag equal to 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 1 (Predicting)

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Functional stage: Entropy bypass stream enabled and Predicting attribute coding on Simple and Main
profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.5 Test bitstream EBS_E_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— bypass_stream_enabled flag equal to 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 2 (Lifting)
Functional stage: Entropy bypass stream enabled and Lifting attribute coding on Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.6 Test bitstream EBS_F_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— bypass_stream_enabled flag equal to 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 3 (raw)
Functional stage: Entropy bypass stream enabled and raw attribute coding on Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.7 Test bitstream EBS_G_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— bypass_stream_enabled flag equal to 0
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 0 (RAHT)
Functional stage: Entropy bypass stream disabled and RAHT attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.1.8 Test bitstream EBS_H_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— bypass_stream_enabled flag equal to 0
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 1 (Predicting)
Functional stage: Entropy bypass stream disabled and Predicting attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.1.9 Test bitstream EBS_I_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— bypass_stream_enabled flag equal to 0
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 2 (Lifting)
Functional stage: Entropy bypass stream disabled and Lifting attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.1.10 Test bitstream EBS_J_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— bypass_stream_enabled flag equal to 0
— lowLatencyAttributesCoding equal to 0
— attr_coding_type is equal to 3 (raw)
Functional stage: Entropy bypass stream disabled and raw attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.2 Entropy continuation (EC)
7.6.2.2.1 Test bitstream EC_A_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— gbh_entropy_continuation_flag: 1
— lowLatencyAttributesCoding equal to 1 (low latency attribute)
— attr_coding_type: 4 (onechain)
— sliceMaxPoints: 25000
— sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and low latency attribute coding on
Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.2 Test bitstream EC_B_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— gbh_entropy_continuation_flag: 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type: 1 (predicting)
— sliceMaxPoints: 25000
— sliceMinPoints: 5000
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Functional stage: Entropy continuation on Onechain Geometry Coding and predicting attribute coding on
Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.3 Test bitstream EC_C_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— gbh_entropy_continuation_flag: 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type: 0 (RAHT)
— sliceMaxPoints: 25000
— sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and RAHT attribute coding on Simple
and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.4 Test bitstream EC_D_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— gbh_entropy_continuation_flag: 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type: 2 (lifting)
— sliceMaxPoints: 25000
— sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and lifting attribute coding on Simple
and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.5 Test bitstream EC_E_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— gbh_entropy_continuation_flag: 1
— lowLatencyAttributesCoding equal to 0
— attr_coding_type: 3 (raw)
— sliceMaxPoints: 25000
— sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and raw attribute coding on Simple
and Main profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.6 Test bitstream EC_F_X
Specification: The bitstream exercises the entropy continuation functionality enabled/disabled on different
slices.
— gbh_entropy_continuation_flag: 0, 1, 0, 1
— lowLatencyAttributesCoding equal to 1 (low latency attribute)
— attr_coding_type: 4 (onechain)
— sliceMaxPoints: 25000
— sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and low latency attribute coding on
Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled/disabled on different slices.
7.6.2.3 Slice/Tile (ST)
7.6.2.3.1 Test bitstream ST_A_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize: 0
— partitionMethod: 0
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.2 Test bitstream ST_B_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize:0
— partitionMethod: 0
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.3 Test bitstream ST_C_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize:0
— partitionMethod: 4
Functional stage: Common functionality in Simple profile.

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.4 Test bitstream ST_D_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize:0
— partitionMethod: 4
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.5 Test bitstream ST_E_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize: 400000
— partitionMethod: 0
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.6 Test bitstream ST_F_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize: 400000
— partitionMethod: 0
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.7 Test bitstream ST_G_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize: 400000
— partitionMethod: 4
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.8 Test bitstream ST_H_X
Specification: The bitstream consists of zero tile and one slice.
— tileSize: 400000
— partitionMethod: 4
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Functional stage: Main profile.
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.9 Test bitstream ST_I_X
Specification: The bitstream consists of three tiles and three slices.
— tileSize: 200000
— partitionMethod: 4
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which three tiles and three slices are
present in Simple profile.
7.6.2.3.10 Test bitstream ST_J_X
Specification: The bitstream consists of three tiles and three slices.
— tileSize: 200000
— partitionMethod: 4
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which three tiles and three slices are
present in Main profile.
7.6.2.4 GPS (GPS)
7.6.2.4.1 Test bitstream GPS_A_X
Specification: The bitstream includes one geometry parameter sets (GPS), which is sharing among 3 frames.
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which one GPS is sharing among multiple
frames.
7.6.2.4.2 Test bitstream GPS_B_X
Specification: The bitstream includes one GPS, which is repeating for each frame.
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which one GPS repeats for each frame.
7.6.2.4.3 Test bitstream GPS_C_X
Specification: The bitstream includes one GPS, which is repeating for each frame.
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which one GPS repeats for each frame.

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.5 APS (APS)
7.6.2.5.1 Test bitstream APS_A_X
Specification: The bitstream includes one APS, which is sharing among 3 frames.
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which one APS is sharing among multiple
frames.
7.6.2.5.2 Test bitstream APS_B_X
Specification: The bitstream includes one APS, which is sharing among 3 frames.
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which one APS is sharing among multiple
frames.
7.6.2.6 axis_coding_order (ACO)
7.6.2.6.1 Test bitstream ACO_A_X
Specification: The bitstream tests on geometry axis coding order (set as zyx) of the coded point cloud.
— geometry_axis_order: 0 (zyx)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.2 Test bitstream ACO_B_X
Specification: The bitstream tests on geometry axis coding order (set as xyz) of the coded point cloud.
— geometry_axis_order: 1 (xyz)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.3 Test bitstream ACO_C_X
Specification: The bitstream tests on geometry axis coding order (set as xzy) of the coded point cloud.
— geometry_axis_order: 2 (xzy)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.4 Test bitstream ACO_D_X
Specification: The bitstream tests on geometry axis coding order (set as yzx) of the coded point cloud.
— geometry_axis_order: 3 (yzx)

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.5 Test bitstream ACO_E_X
Specification: The bitstream tests on geometry axis coding order (set as zyx) of the coded point cloud.
— geometry_axis_order: 4 (zyx)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.6 Test bitstream ACO_F_X
Specification: T The bitstream tests on geometry axis coding order (set as zxy) of the coded point cloud.
— geometry_axis_order: 5 (zxy)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.7 Test bitstream ACO_G_X
Specification: The bitstream tests on geometry axis coding order (set as yxz) of the coded point cloud.
— geometry_axis_order: 6 (yxz)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.8 Test bitstream ACO_H_X
Specification: The bitstream tests on geometry axis coding order (set as xyz) of the coded point cloud.
— geometry_axis_order: 7 (xyz)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.7 Geometry scaling (GS)
7.6.2.7.1 Test bitstream GS_A_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— positionQuantizationScale: 0.25
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.7.2 Test bitstream GS_B_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— positionQuantizationScale: 0.015625
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
7.6.2.7.3 Test bitstream GS_C_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— positionQuantizationScale: 0.125
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
7.6.2.7.4 Test bitstream GS_D_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— positionQuantizationScale: 0.03125
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
7.6.2.7.5 Test bitstream GS_E_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— positionQuantizationScale: 0.03125
Functional stage: Geometry coding in Simple profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Simple profile.
7.6.2.8 Onechain geometry coding (OGC)
7.6.2.8.1 Test bitstream OGC_A_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has two points.
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code point cloud with two points in Main profile.

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.8.2 Test bitstream OGC_B_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has two points.
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code point cloud with two points in Simple profile.
7.6.2.8.3 Test bitstream OGC_C_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use Ford data).
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code a point cloud with 18 bits depth in Main profile.
7.6.2.8.4 Test bitstream OGC_D_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use Ford data).
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code a point cloud with 18 bits depth in Simple profile.
7.6.2.8.5 Test bitstream OGC_E_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has one point.
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code point cloud with one point in Main profile.
7.6.2.8.6 Test bitstream OGC_F_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has one point.
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code point cloud with one point in Simple profile.
7.6.2.8.7 Test bitstream OGC_G_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use QNX data).
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code a point cloud with 18 bits depth in Main profile.

© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.8.8 Test bitstream OGC_H_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use QNX data).
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is
used to code a point cloud with 18 bits depth in Simple profile.
7.6.2.9 Preserve laser coding state (PLCS)
7.6.2.9.1 Test bitstream PLCS_A_X
Specification: The bitstream exercises the functionality to preserve laser coding state between slices.
— entropyContinuationEnabled: 1
— perLaserCodingStatePreserved: 1
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which preserve laser coding state
functionality is enabled in Main profile.
7.6.2.9.2 Test bitstream PLCS_B_X
Specification: The bitstream exercises the functionality to preserve laser coding state between slices.
— entropyContinuationEnabled: 1
— perLaserCodingStatePreserved: 1
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which preserve laser coding state
functionality is enabled in Simple profile.
7.6.2.9.3 Test bitstream PLCS_C_X
Specification: The bitstream exercises the functionality to preserve laser coding state between slices.
— entropyContinuationEnabled: 1
— perLaserCodingStatePreserved: 0
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode b
...

ISO/IEC FDIS 23090-35:2026(en)
ISO/IEC JTC 1/SC 29/WG 07
Secretariat: JISC
Date: 2026-02-1205-28
Information technology — Coded representation of immersive
media —
Part 35:
Conformance and reference software for low latency, low complexity
LiDAR coding
FDIS stage
ISO/IEC FDIS 23090-35:2026(en)
© ISO/IEC 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO
at the address below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
EmailE-mail: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2026 – All rights reserved
ii
ISO/IEC FDIS 23090-35:2026(en)
Contents
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative reference . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Conventions . 2
6 Reference software for ISO/IEC 23090-30 . 2
7 Conformance testing for ISO/IEC 23090-30 . 2
7.1 General. 2
7.2 Bitstream conformance . 2
7.3 Decoder conformance . 2
7.4 Procedure to test bitstreams . 3
7.5 Procedure to test decoder conformance . 3
7.6 Specification of the test bitstreams . 4

© ISO/IEC 2026 – All rights reserved
iii
ISO/IEC FDIS 23090-35:2026(en)
Foreword
I
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.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC
Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not received
notice of (a) patent(s) which may be required to implement this document. However, implementers are
cautioned that this may not represent the latest information, which may be obtained from the patent database
available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO’sISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
A list of all parts in the ISO/IEC 23090 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-
committees.
© ISO/IEC 2026 – All rights reserved
iv
ISO/IEC FDIS 23090-35:2026(en)
Introduction
0.1 0.1 General
This document specifies reference software and conformance testing for ISO/IEC 23090-30 low latency, low
complexity LiDAR coding (L3C2).
0.2 0.2 Purpose
The purpose of this document is to provide the following:
— — Reference decoder software for decoding ISO/IEC 23090-30 compliant bitstreams.
— — Reference encoder software for generating ISO/IEC 23090-30 compliant bitstreams.
— — Procedures to test bitstream and decoder conformance.
— — A set of reference bitstreams conforming to ISO/IEC 23090-30.
0.3 0.3 Examples of use
Some examples of uses that may be appropriate for the reference decoder software are as follows:
— — As an illustration of how to perform the decoding process specified in ISO/IEC 23090-30.
— — As the starting basis for the implementation of a decoder that conforms to ISO/IEC 23090-30.
— — For testing the conformance of a decoder implementation with the decoding process specified in
ISO/IEC 23090-30.
— — For testing the conformance of a bitstream to the constraints specified for bitstream conformance in
ISO/IEC 23090-30, as the software can detect and report many bitstream conformance violations.
NOTE —The lack of the detection of any conformance violation by the reference decoder software is not
definitive proof that the bitstream conforms to all constraints specified for bitstream conformance in ISO/IEC
23090-30.
Some examples of uses that maycan be appropriate for the reference encoder software are as follows:
— — As an illustration of how to perform an encoding process that produces bitstreams that conform to the
constraints specified for bitstream conformance in ISO/IEC 23090-30.
— — As the starting basis for the implementation of an encoder that conforms to ISO/IEC 23090-30.
— — As a means of generating bitstreams for testing the conformance of a decoder implementation with
the decoding process specified in ISO/IEC 23090-30.
— — As a means of evaluating and demonstrating examples of the quality that can be achieved by an
encoding process that conforms to ISO/IEC 23090-30.
NOTE — No guarantee of the quality that will be achieved by an encoder is provided by its conformance to
ISO/IEC 23090-30, as the conformance of an encoder to ISO/IEC 23090-30 is defined only in terms of format
constraints imposed on the bitstream syntax. The reference encoder software provides some illustrative examples
of what quality can be achieved in conformance to ISO/IEC 23090-30, it doesn’t define minimum encoding quality
or maximum encoding quality.
© ISO/IEC 2026 – All rights reserved
v
ISO/IEC FDIS 23090-35:2026(en)
Information technology — Coded representation of immersive media
— —
Part 35:
Conformance and reference software for low latency, low complexity
LiDAR coding
1 Scope
This document provides accompanying reference software for ISO/IEC 23090-30. The software is an integral
part of this document.
The use of this reference software is not required to make an implementation of an encoder or decoder in
conformance to ISO/IEC 23090-30. Requirements established in ISO/IEC 23090-30 take precedence over the
behaviour of the reference software.
This document also specifies a set of tests and procedures designed to indicate whether encoders or decoders
meet the normative requirements specified in ISO/IEC 23090-30.
2 Normative reference
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 23090--30, Information technology — Coded representation of immersive media — Part 30: Low
latency, low complexity light detection and ranging (LiDAR) coding.
3 Terms and definitions
For the purposes of this document, the terms and definitions in ISO/IEC 23090-30 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— — ISO Online browsing platform: available at https://www.iso.org/obp
— — IEC Electropedia: available at https://www.electropedia.org/
3.1 3.1
bitstream
sequence of bits representing compressed point cloud data structured according to the syntax of a specific
coding specification
3.2 3.2
decoder
process or device that reconstructs point cloud data from a structured bitstream conforming to a specific
coding specification
Note 1 to entry: Decoder does not include the point cloud rendering process, which is outside the scope of this document
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
3.3 3.3
encoder
embodiment of a process that produces a bitstream
3.4 3.4
reference software decoder
software implementation of the decoding process that reconstructs point cloud data from a structured
bitstream conforming to a specific coding specification
3.5 3.5
reference software encoder
software implementation that compresses point cloud data into a structured bitstream conforming to a
specific coding specification
4 Abbreviated terms
The abbreviated terms in Clause 4 of ISO/IEC 23090-30:2026 apply.
5 Conventions
The conventions specified in Clause 5 of ISO/IEC 23090-30:2026 apply.
6 Reference software for ISO/IEC 23090-30
Reference software is useful in aiding users of a compression standard to establish and test conformance and
interoperability, and to educate users and demonstrate the capabilities of ISO/IEC 23090-30:2026. The
reference software for ISO/IEC 23090-30:2026 is available at: https://standards.iso.org/iso-iec/23090/-
35/ed-1/en/.
The software package contains one part:
— — mpeg-pcc-tml software: Support for Simple and Main profiles.
The reference software manual is mpeg-pcc-tml-sw-manual.pdf. This manual can be used to install and use
the reference software.
7 Conformance testing for ISO/IEC 23090-30
7.1 General
The following clauses specify normative tests for verifying conformance of bitstreams as well as decoders.
Those normative tests make use of test data (bitstream test suites) provided are available at:
https://standards.iso.org/iso-iec/23090/-35/ed-1/en/ and the reference software decoder specified in
Clause 6Clause 6.
7.2 Bitstream conformance
Bitstream conformance follows the specification text in ISO/IEC 23090-30.
7.3 Decoder conformance
Decoder conformance for ISO/IEC 23090-30, such as conformance point, etc., is specified by clause 6.5.1 of
ISO/IEC 23090-30:2026.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.4 Procedure to test bitstreams
A bitstream that claims conformance with ISO/IEC 23090-30 shall pass the following normative test.
The bitstream shall be decoded by processing it with the reference software decoder. When processed by the
reference software decoder, the bitstream shall not cause any error or non-conformance messages to be
reported by the reference software decoder. This test should not be applied to bitstreams that are known to
contain errors introduced by transmission, as such errors are highly likely to result in bitstreams that lack
conformance to ISO/IEC 23090-30.
Successfully passing the reference software decoder test provides only a strong presumption that the
bitstream under test does indeed meet all the requirements specified in ISO/IEC 23090-30 that are tested by
the reference software decoder.
ISO/IEC 23090-30 contains several informative recommendations that are not an integral part of
International Standard. When testing a bitstream for conformance, it may also be useful to test whether or not
the bitstream follows those recommendations.
To check correctness of a bitstream, it is necessary to parse the entire bitstream and to extract all the syntax
elements and other values derived from those syntactic elements and used by the decoding process specified
in ISO/IEC 23090-30.
A verifier may not necessarily perform all stages of the decoding process specified in ISO/IEC 23090-30 in
order to verify bitstream correctness. Many tests can be performed on syntax elements in a state prior to their
use in some processing stages.
7.5 Procedure to test decoder conformance
7.5.1 Conformance bitstreams
A bitstream has values of main_profile_compatibility_flag and level_idc corresponding to a set of specified
constraints on a bitstream for which a decoder conforming to a specified profile, and level is required in
Annex A of ISO/IEC 23090-30:2026 to properly perform the decoding process.
7.5.2 Contents of the bitstream file
The conformance bitstreams are included in this document and are available at: https://standards.iso.org/iso-
iec/23090/-35/ed-1/en/. The following information is included in a single zipped file for each such bitstream.
— — *.bit – bitstream as described in subclause 7.6.2subclause 7.6.2
— — readme.md – description
— — *.cfg – config file used to generate bitstream with TML encoder SW (not applicable if TML encoder
release version not used)
— — *.md5 – MD5sum of the bitstream file
— — *_dec.ply – unordered decoded point cloud frames
— — *_dec.ply.md5 – MD5 checksum for decoded point cloud frame
7.5.3 Requirements on output of the decoding process
The output of the decoding process is specified in Clause 8 of ISO/IEC 23090-30:2026.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
The rendering process, which may follow the output of the decoding process, is outside the scope of this
document.
7.5.4 Recommendations
In addition to the requirements, it is desirable that conforming decoders implement various informative
recommendations specified in ISO/IEC 23090-30 that are not an integral part of ISO/IEC 23090-30. This
clause discusses some of these recommendations.
It is recommended that a conforming decoder be able to resume the decoding process as soon as possible after
the loss or corruption of part of a bitstream.
7.6 Specification of the test bitstreams
7.6.1 General
The test bitstreams are part of the mechanism to verify decoder conformance according to the ISO/IEC 23090-
30 specification. The bitstreams used for the decoder conformance testing specified in this document shall be
those listed in Table 1Table 1. They are available at: https://standards.iso.org/iso-iec/23090/-35/ed-1/en/.
Table 1 — List of reference bitstreams.
Categories Feature Features tested
Name
Common functionality EBS Entropy bypass stream
EC Entropy continuation
ST Slice/Tile
GPS GPS (Geometry Parameter Set)
APS APS (Attribute Parameter Set)
ACO Axis coding order
Geometry coding GS Geometry scaling
OGC Onechain geometry coding
PLCS Preserve laser coding state
DPOC Duplicate points in onechain geometry coding
UNEOC Use NSensing estimation in onechain coding
UCN Use Coarse neighbours
UVP Use Vertical prediction
LLA Low latency attributes coding
UPOC Unordered points in onechain coding
SCS Sensing coverage signalling
Attribute coding GATT Generic attribute
QuantATT Quantization
LodRAHT Level of Details (LoD) and Region Adaptive Hierarchical Transform
(RAHT)
SLOD Single LoD
NumLOD Number of LoDs
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Categories Feature Features tested
Name
DecLOD LoD method: Decimation
DisLOD LoD method: Distance
CentLOD LoD method: Block-based
SL Scalable Lifting
PSInterLOD Predictor search: inter LoD
PSIntraLOD Predictor search: intra LoD
NumPRED Number of predictors
DirectPRED Direct predictors (Pred)
NB Neighbour bias
LCP Last component pred
ICP Predicting Transform: Inter component pred
RahtPRED RAHT prediction
SDC Spherical domain coding
ANBF Attribute neighbour blending filtering
7.6.2 Test bitstreams
7.6.2.1 Entropy bypass stream (EBS)
7.6.2.1.1 Test bitstream EBS_A_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— — bypass_stream_enabled flag equal to 0.
— — lowLatencyAttributesCoding equal to 1 (low latency attribute).
— — attr_coding_type is equal to 4 (onechain).
Functional stage: Entropy bypass stream disabled and low latency attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.1.2 Test bitstream EBS_B_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— — bypass_stream_enabled flag equal to 1
— — lowLatencyAttributesCoding equal to 1 (low latency attribute)
— — attr_coding_type is equal to 4 (onechain)
Functional stage: Entropy bypass stream enabled and low latency attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.1.3 Test bitstream EBS_C_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— — bypass_stream_enabled flag equal to 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 0 (RAHT)
Functional stage: Entropy bypass stream enabled and RAHT attribute coding on Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.4 Test bitstream EBS_D_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— — bypass_stream_enabled flag equal to 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 1 (Predicting)
Functional stage: Entropy bypass stream enabled and Predicting attribute coding on Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.5 Test bitstream EBS_E_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— — bypass_stream_enabled flag equal to 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 2 (Lifting)
Functional stage: Entropy bypass stream enabled and Lifting attribute coding on Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
7.6.2.1.6 Test bitstream EBS_F_X
Specification: The bitstream exercises the entropy bypass stream On functionality.
— — bypass_stream_enabled flag equal to 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 3 (raw)
Functional stage: Entropy bypass stream enabled and raw attribute coding on Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream enabled.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.1.7 Test bitstream EBS_G_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— — bypass_stream_enabled flag equal to 0
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 0 (RAHT)
Functional stage: Entropy bypass stream disabled and RAHT attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.1.8 Test bitstream EBS_H_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— — bypass_stream_enabled flag equal to 0
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 1 (Predicting)
Functional stage: Entropy bypass stream disabled and Predicting attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.1.9 Test bitstream EBS_I_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— — bypass_stream_enabled flag equal to 0
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 2 (Lifting)
Functional stage: Entropy bypass stream disabled and Lifting attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
7.6.2.1.10 Test bitstream EBS_J_X
Specification: The bitstream exercises the entropy bypass stream Off functionality.
— — bypass_stream_enabled flag equal to 0
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type is equal to 3 (raw)
Functional stage: Entropy bypass stream disabled and raw attribute coding on Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy stream disabled.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.2 Entropy continuation (EC)
7.6.2.2.1 Test bitstream EC_A_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— — gbh_entropy_continuation_flag: 1
— — lowLatencyAttributesCoding equal to 1 (low latency attribute)
— — attr_coding_type: 4 (onechain)
— — sliceMaxPoints: 25000
— — sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and low latency attribute coding on
Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.2 Test bitstream EC_B_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— — gbh_entropy_continuation_flag: 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type: 1 (predicting)
— — sliceMaxPoints: 25000
— — sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and predicting attribute coding on
Simple and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.3 Test bitstream EC_C_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— — gbh_entropy_continuation_flag: 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type: 0 (RAHT)
— — sliceMaxPoints: 25000
— — sliceMinPoints: 5000
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Functional stage: Entropy continuation on Onechain Geometry Coding and RAHT attribute coding on Simple
and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.4 Test bitstream EC_D_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— — gbh_entropy_continuation_flag: 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type: 2 (lifting)
— — sliceMaxPoints: 25000
— — sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and lifting attribute coding on Simple
and Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.5 Test bitstream EC_E_X
Specification: The bitstream exercises the entropy continuation functionality enabled.
— — gbh_entropy_continuation_flag: 1
— — lowLatencyAttributesCoding equal to 0
— — attr_coding_type: 3 (raw)
— — sliceMaxPoints: 25000
— — sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and raw attribute coding on Simple and
Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled.
7.6.2.2.6 Test bitstream EC_F_X
Specification: The bitstream exercises the entropy continuation functionality enabled/disabled on different
slices.
— — gbh_entropy_continuation_flag: 0, 1, 0, 1
— — lowLatencyAttributesCoding equal to 1 (low latency attribute)
— — attr_coding_type: 4 (onechain)
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
— — sliceMaxPoints: 25000
— — sliceMinPoints: 5000
Functional stage: Entropy continuation on Onechain Geometry Coding and low latency attribute coding on
Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which entropy continuation function is
enabled/disabled on different slices.
7.6.2.3 Slice/Tile (ST)
7.6.2.3.1 Test bitstream ST_A_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize: 0
— — partitionMethod: 0
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.2 Test bitstream ST_B_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize:0
— — partitionMethod: 0
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.3 Test bitstream ST_C_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize:0
— — partitionMethod: 4
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.4 Test bitstream ST_D_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize:0
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
— — partitionMethod: 4
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.5 Test bitstream ST_E_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize:400000
— — partitionMethod: 0
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.6 Test bitstream ST_F_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize:400000
— — partitionMethod: 0
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.7 Test bitstream ST_G_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize:400000
— — partitionMethod: 4
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Simple profile.
7.6.2.3.8 Test bitstream ST_H_X
Specification: The bitstream consists of zero tile and one slice.
— — tileSize:400000
— — partitionMethod: 4
Functional stage: Main profile.
Functional stage: Common functionality in Main profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Purpose: Check that the decoder can properly decode bitstreams in which zero tile and one slice are present
in Main profile.
7.6.2.3.9 Test bitstream ST_I_X
Specification: The bitstream consists of three tiles and three slices.
— — tileSize:200000
— — partitionMethod: 4
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which three tiles and three slices are
present in Simple profile.
7.6.2.3.10 Test bitstream ST_J_X
Specification: The bitstream consists of three tiles and three slices.
— — tileSize:200000
— — partitionMethod: 4
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which three tiles and three slices are
present in Main profile.
7.6.2.4 GPS (GPS)
7.6.2.4.1 Test bitstream GPS_A_X
Specification: The bitstream includes one geometry parameter sets (GPS), which is sharing among 3 frames.
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which one GPS is sharing among multiple
frames.
7.6.2.4.2 Test bitstream GPS_B_X
Specification: The bitstream includes one GPS, which is repeating for each frame.
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which one GPS repeats for each frame.
7.6.2.4.3 Test bitstream GPS_C_X
Specification: The bitstream includes one GPS, which is repeating for each frame.
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which one GPS repeats for each frame.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.5 APS (APS)
7.6.2.5.1 Test bitstream APS_A_X
Specification: The bitstream includes one APS, which is sharing among 3 frames.
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which one APS is sharing among multiple
frames.
7.6.2.5.2 Test bitstream APS_B_X
Specification: The bitstream includes one APS, which is sharing among 3 frames.
Functional stage: Common functionality in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which one APS is sharing among multiple
frames.
7.6.2.6 axis_coding_order (ACO)
7.6.2.6.1 Test bitstream ACO_A_X
Specification: The bitstream tests on geometry axis coding order (set as zyx) of the coded point cloud.
— — geometry_axis_order: 0 (zyx)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.2 Test bitstream ACO_B_X
Specification: The bitstream tests on geometry axis coding order (set as xyz) of the coded point cloud.
— — geometry_axis_order: 1 (xyz)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.3 Test bitstream ACO_C_X
Specification: The bitstream tests on geometry axis coding order (set as xzy) of the coded point cloud.
— — geometry_axis_order: 2 (xzy)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.6.4 Test bitstream ACO_D_X
Specification: The bitstream tests on geometry axis coding order (set as yzx) of the coded point cloud.
— — geometry_axis_order: 3 (yzx)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.5 Test bitstream ACO_E_X
Specification: The bitstream tests on geometry axis coding order (set as zyx) of the coded point cloud.
— — geometry_axis_order: 4 (zyx)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.6 Test bitstream ACO_F_X
Specification: T The bitstream tests on geometry axis coding order (set as zxy) of the coded point cloud.
— — geometry_axis_order: 5 (zxy)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.7 Test bitstream ACO_G_X
Specification: The bitstream tests on geometry axis coding order (set as yxz) of the coded point cloud.
— — geometry_axis_order: 6 (yxz)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
7.6.2.6.8 Test bitstream ACO_H_X
Specification: The bitstream tests on geometry axis coding order (set as xyz) of the coded point cloud.
— — geometry_axis_order: 7 (xyz)
Functional stage: Common functionality in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which axis coding order is set in Main
profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.7 Geometry scaling (GS)
7.6.2.7.1 Test bitstream GS_A_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— — positionQuantizationScale: 0.25
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
7.6.2.7.2 Test bitstream GS_B_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— — positionQuantizationScale: 0.015625
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
7.6.2.7.3 Test bitstream GS_C_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— — positionQuantizationScale: 0.125
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
7.6.2.7.4 Test bitstream GS_D_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— — positionQuantizationScale: 0.03125
Functional stage: Geometry coding in Main profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Main profile.
7.6.2.7.5 Test bitstream GS_E_X
Specification: Geometry scaling in onechain geometry coding is turned on and it uses geometry global scale
factor.
— — positionQuantizationScale: 0.03125
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
Functional stage: Geometry coding in Simple profile.
Purpose: Check if the decoder can properly decode bitstreams in which geometry global scale factor is
configured in Simple profile.
7.6.2.8 Onechain geometry coding (OGC)
7.6.2.8.1 Test bitstream OGC_A_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has two points.
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code point cloud with two points in Main profile.
7.6.2.8.2 Test bitstream OGC_B_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has two points.
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code point cloud with two points in Simple profile.
7.6.2.8.3 Test bitstream OGC_C_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use Ford data).
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code a point cloud with 18 bits depth in Main profile.
7.6.2.8.4 Test bitstream OGC_D_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use Ford data).
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code a point cloud with 18 bits depth in Simple profile.
7.6.2.8.5 Test bitstream OGC_E_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has one point.
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code point cloud with one point in Main profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.8.6 Test bitstream OGC_F_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has one point.
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code point cloud with one point in Simple profile.
7.6.2.8.7 Test bitstream OGC_G_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use QNX data).
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code a point cloud with 18 bits depth in Main profile.
7.6.2.8.8 Test bitstream OGC_H_X
Specification: Onechain geometry coding is the only geometry coding method in L3C2. The bitstream tests
onechain geometry coding with a point cloud which has 18 bits depth (use QNX data).
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which Onechain geometry coding is used
to code a point cloud with 18 bits depth in Simple profile.
7.6.2.9 Preserve laser coding state (PLCS)
7.6.2.9.1 Test bitstream PLCS_A_X
Specification: The bitstream exercises the functionality to preserve laser coding state between slices.
— — entropyContinuationEnabled: 1
— — perLaserCodingStatePreserved: 1
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which preserve laser coding state
functionality is enabled in Main profile.
7.6.2.9.2 Test bitstream PLCS_B_X
Specification: The bitstream exercises the functionality to preserve laser coding state between slices.
— — entropyContinuationEnabled: 1
— — perLaserCodingStatePreserved: 1
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which preserve laser coding state
functionality is enabled in Simple profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.9.3 Test bitstream PLCS_C_X
Specification: The bitstream exercises the functionality to preserve laser coding state between slices.
— — entropyContinuationEnabled: 1
— — perLaserCodingStatePreserved: 0
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which preserve laser coding state
functionality is disabled in Main profile.
7.6.2.9.4 Test bitstream PLCS_D_X
Specification: The bitstream exercises the functionality to preserve laser coding state between slices.
— — entropyContinuationEnabled: 1
— — perLaserCodingStatePreserved: 0
Functional stage: Geometry coding in Simple profile.
Purpose: Check that the decoder can properly decode bitstreams in which preserve laser coding state
functionality is disabled in Simple profile.
7.6.2.10 Duplicate points in onechain geometry coding (DPOC)
7.6.2.10.1 Test bitstream DPOC_A_X
Specification: The bitstream exercises the functionality to enable removal of duplicated points.
— — mergeDuplicatedPoints: 1
— — lowLatencyAttributesCoding: 1 (low latency attribute)
— — attr_coding_type: 4 (onechain)
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which removal of duplicated points
functionality is enabled on low latency attribute coding in Main profile.
7.6.2.10.2 Test bitstream DPOC_B_X
Specification: The bitstream exercises the functionality to disable removal of duplicated points.
— — mergeDuplicatedPoints: 0
— — lowLatencyAttributesCoding: 1 (low latency attribute)
— — attr_coding_type: 4 (onechain)
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which removal of duplicated points
functionality is disabled on low latency attribute coding in Main profile.
© ISO/IEC 2026 – All rights reserved
ISO/IEC FDIS 23090-35:2026(en)
7.6.2.10.3 Test bitstream DPOC_C_X
Specification: The bitstream exercises the functionality to enable removal of duplicated points.
— — mergeDuplicatedPoints: 1
— — lowLatencyAttributesCoding: 0
— — attr_coding_type: 1 (predicting)
Functional stage: Geometry coding in Main profile.
Purpose: Check that the decoder can properly decode bitstreams in which removal of duplicated points
functionality is enabled on predicting attribute coding in Main profile.
7.6.2.10.4 Test bitstream DPOC_D_X
Specification: The bitstream exercises the functionality to disable removal of duplicated points.
— — mergeDuplicatedPoints: 0
— — lowLatencyAttributesCoding: 0
— — attr_coding_type: 1 (predicting)
Functional stage: Geometry coding in Simple profile.
Purpose:
...