1 / 9

Design Printing and Scanning Working Group Web3D 2019

Design Printing and Scanning Working Group Web3D 2019. Opportunities in application of Digital Twin Presentations by Dr. Han and Dr. Mouton of ISO/IEC WG-16 CMM example. 2. X3D Model Exchange for Navy and Marine Makers https://modelexchange.nps.edu. 3. X3D and point clouds

edwalton
Download Presentation

Design Printing and Scanning Working Group Web3D 2019

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design Printing and Scanning Working GroupWeb3D 2019

  2. Opportunities in application of Digital Twin • Presentations by Dr. Han and Dr. Mouton of ISO/IEC WG-16 • CMM example

  3. 2. X3D Model Exchange for Navy and Marine Makers https://modelexchange.nps.edu

  4. 3. X3D and point clouds • The Design Printing and Scanning Group has drafted a specification for the PointProperties nodes giving content authors more control over the rendering of ‘points’ in their scenes. As of July 2019 there is one implementation of this node, in the Xj3D (desktop application) browser. • Challenge for the WG and Consortium is to encourage implementation by the X3D viewer developers • Understand limits of current implementation, and whats possible now • Evaluation of point cloud visualization for a 3D Scan • Pointset and PointProperties rendering comparison

  5. 5 Report from Navy workshop on scanning

  6. 7. Exploiting the capabilities of the Metadata nodes “Metadata is just data” Contribution to WG-16 STEP Geometry Services TR

  7. Vigoulet-Auzil Core metadata Original geometry Design intent Original ID & Version Created by, creation date, software Check OAIS terms Modification of the design Source ID for n transform Modified by (p&o), date, geom format, software, LOD • Name • ID • URI ? or SHA-1 ? • Created by • Modified by • Modified date • Modification type (format transformation, modification, properties addition) • Geometry format • software • Level of detail • Original ID • Source ID These metadata managed by a tree in a repo or blockchain ? Derived : Representation Change No change in the intended shape Format change (ie: ative to STEP native to native, STEP to XYZ,) gemetry representaion change : CSG to BREP BREP to tesselated , level of detail chang ) Source ID Original ID & Version for 1st transform Derived geometry Modification of the geometry for/by downstream process Add PMI, slicing, idealisation, meshing modified geometry  input from Nathan : original author= created by, latest author=modified by,feature construction history (too complex ? ) , file name (URI), authoring tool specs (software), workflow steps ((too complex ?) Source ID for n transform Modified by, date, geom format, modification type, software Proposal that in STEP this could be attached to the « shape representation » In other format, we shall identify where to store it , header or metadata fields Geometry on my system Need to ensure the pedigree of the file on my system ID URI Original ID & Version (URI ?) Source ID STEP Geometry Services @ Webconf

  8. X3D Metadata example submitted to “STEP Geometry Services” TR 23301 WD <MetadataSet name="ISO TS 23301" reference=’ISO/TC 184/SC 04/JWG 16’> <MetadataString name='name' value='" nist_ctc_01_asme1_ap203 "'/> <MetadataString name='id' value='"http://spri.kshell.com/xt/shape/2m4w9w39ad9n/shape_23323838.x3d"'/> <MetadataString name='source-id' value='"http://spri.kshell.com/xt/shape/2m4w9w39ad9n/shape_23323838.x3d"'/> <MetadataString name='source-URI' value='"http://spri.kshell.com/xt/shape/2m4w9w39ad9n/shape_23323838.x3d"'/> <MetadataString name='original-id' value='"nist_ctc_01_asme1_ap203"'/> <MetadataString name='original-URI' value='" nist_ctc_01_asme1_ap203.x3d"'/> <MetadataString name='modification-type' value='"conversion"'/> <MetadataString name='modification-comments' value='"conv to X3D with tesselation of STEP face entities"'/> <MetadataString name='created-by' value='"NIST"'/> <MetadataString name='creation-date' value='"2014-12-19"'/> <MetadataString name='format' value='"ISO/IEC 19776-1:2015”’ reference='http://www.web3d.org/documents/specifications/19776-1/V3.3/index.html'/> <MetadataString name='modified-by' value='"KShell Analysis"'/> <MetadataString name='modified-date' value='"2018-05-25"'/> <MetadataString name='software' value='" https://kshell.sourcerepo.com/kshell/kshell/step_x3d rev 5063"'/> <MetadataString name='level-of-detail' value=''/> <MetadataString name='SHA-1' value='"a88869625725f1b3df9b2351e723aa1a228554a6"'/> </MetadataSet>

  9. Opportunities for coming year • Extend coverage of the NIST Conformance Suite • Improvement of STEP  X3D workflow • Opportunities in BIM • Develop a BIM (IFC)  X3D workflow • Workflows to prepare X3D scenegraphs from • STEP • STL, AMF, 3MF • PDF – which supports 3D content • JT (ISO ….) • Proprietary formats

More Related