Skip to main content
Version: v5.0

SGPK file structure

SGPK file has following file structure:

  • SGPK
    • manifest.json
    • thumbnail.png
    • occ
      • :occurenceId
        • scenegraph.json
        • graphics.scz
        • hoops_node_mapping.json

Notes of files in SGPK#

Thumbnail file, thumbnail.png, is for entire Navisowork model, and is in root folder directly.

One Navisworks model may contain multiple source models, and each source model has independent portion in Scene-Graph data. We split Scene-Graph data by source models, and generate one scenegraph.json file per source model.

As to exporting model geometry, there are two options. One is to generate HOOPs stream file(graphics.scz) for entire Navisworks model, and put it into the first Occurrence folder. The other is to split model geometry by source models, and for each source model, generate its own graphics.scz and put it into the corresponding Occurence folder. This option is useful to improve the performance of model rendering in platform viewer, especially when it is very big model.

Along with each graphics.scz file, there is always one accompanied HOOPs node mapping file, hoops_node_mapping.json, in the same directory.

hoops_node_mapping.json#

Each model element in scenegraph.json has unique ID, which is also known as Package ID of model element. To help Platform viewer efficiently and quickly find nodes in HOOPs file by model element's ID, plugin exports HOOPs node mapping file, hoops_node_mapping.json.

HOOPs node mapping file contains two-way mappings, one is from HOOPs node id to model element's ID, and the other is from model element's ID to HOOPs node id.

Its format is as below:

[{  "<node_id>" : "<package_id>"},
 { "<package_id>" : "<node_id>" }]