Struct CopcHierarchyVlr 

pub struct CopcHierarchyVlr { /* private fields */ }

The hierarchy VLR MUST exist.

Like EPT, COPC stores hierarchy information to allow a reader to locate points that are in a particular octree node. Also like EPT, the hierarchy MAY be arranged in a tree of pages, but SHALL always consist of at least ONE hierarchy page. The VLR data consists of one or more hierarchy pages. Each hierarchy data page is written as follows:

VoxelKey corresponds to the naming of EPT data files. octree hierarchy is arranged in pages. The COPC VLR provides information describing the location and size of root hierarchy page. The root hierarchy page can be used to traverse to child pages. Each entry in a hierarchy page either refers to a child hierarchy page, octree node data chunk, or an empty octree node. The size and file offset of each data chunk is provided in the hierarchy entries, allowing the chunks to be directly read for decoding.

Implementations

impl CopcHierarchyVlr

pub const RECORD_ID: u16 = 1000

The record id of the LasZip VLR header.

pub fn write_to<W: Write>(&self, dst: &mut W) -> Result<()>

Writes the Vlr data to the source.

This only writes the payload data the vlr header should be written before-hand.

pub fn read_from_with( vlr: &Vlr, copc_info: &CopcInfoVlr, ) -> Result<CopcHierarchyVlr>

Reads the CopcHierarchyVlr from the Vlr payload with specifications from copc_info.

pub fn iter_entries(&self) -> EntryIterator<'_>

iterates over all entries merging all referenced pages into root

Trait Implementations

impl Debug for CopcHierarchyVlr

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.