<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:18.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<style type="text/css">.style1 {font-family: "Times New Roman";}</style></head><body lang="EN-AU" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<h2>Final Call for Evidence on JPEG Pleno Point Cloud Coding<o:p></o:p></h2>
<h2>August 12, 2020<o:p></o:p></h2>
<p><a href="https://jpeg.org/jpegpleno">JPEG Pleno</a> will merge various modalities of plenoptic content under a single framework and in a seamless manner. Efficient and powerful point cloud representation is a key feature of this vision. In this context a
point cloud refers to a set of data items representing positions of points in space, expressed in a given coordinate system, usually three-dimensional. This geometrical data can be accompanied with per-point attributes of varying nature (e.g. color or temperature).
Combined with other types of data (like light field data), point clouds open a wide range of new opportunities for immersive browsing and virtual reality applications.<o:p></o:p></p>
<p>In the context of the JPEG Pleno standardization project, which aims at developing a next generation visual information coding standard that moves beyond coding of 2D planar content by taking advantage of plenoptic representations, JPEG issued a
<a href="http://ds.jpeg.org/documents/jpegpleno/wg1n88014-REQ-Final_CfE_JPEG_Pleno_PCC.pdf">
Final Call for Evidence (CfE) on JPEG Pleno Point Cloud Coding</a>. This call differs from the First Call for Evidence on JPEG Pleno Point Cloud Coding by including an updated timeline for the activity in response to the 2020 COVID-19 Pandemic.<o:p></o:p></p>
<p>This call addresses in particular coding technologies for static point cloud content that enable scalable decoding of the bitstream and random access to subsets of the point cloud and contains information on the submission process, requirements for submission,
material available to submitters, and the timeline of the call.<o:p></o:p></p>
<p>Associated with this call are the <a href="http://ds.jpeg.org/documents/jpegpleno/wg1n86012-REQ-JPEG_Pleno_Point_Cloud_Use_Cases_and_Requirements_v1_3.pdf">
JPEG Pleno Point Cloud – Use Cases and Requirements (v1.3)</a> document and the <a href="http://ds.jpeg.org/documents/jpegpleno/wg1n88044-CTQ-JPEG_Pleno_PCC_Common_Test_Conditions_3_3.pdf">
JPEG Pleno Point Cloud Coding Common Test Conditions (v3.3)</a> document.<o:p></o:p></p>
<p>To keep informed and get involved in the discussion, interested parties are invited to register to the
<a href="http://listregistration.jpeg.org">ad hoc group’s mailing list</a>.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
<br><p style="font-family: Verdana; font-size:8pt; color:#666666;">UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email.</p></body></html>