writers.gltf

GLTF is a file format specification for 3D graphics data. If a mesh has been generated for a PDAL point view, the GLTF Writer will produce simple output in the GLTF format. PDAL does not currently support many of the attributes that can be found in a GLTF file. This writer creates a binary GLTF (extension ‘.glb’).

Default Embedded Stage

This stage is enabled by default

Example

[
    "infile.las",
    {
        "type": "filters.poisson",
        "depth": 12
    },
    {
        "type":"writers.gltf",
        "filename":"output.glb",
        "red": 0.8,
        "metallic": 0.5
    }
]

Options

filename

Name of the GLTF (.glb) file to be written. [Required]

metallic

The metallic factor of the faces. [Default: 0]

roughness

The roughness factor of the faces. [Default: 0]

red

The base red component of the color applied to the faces. [Default: 0]

green

The base green component of the color applied to the faces. [Default: 0]

blue

The base blue component of the color applied to the faces. [Default: 0]

alpha

The alpha component to be applied to the faces. [Default: 1.0]

double_sided

Whether the faces are colored on both sides, or just the side visible from the initial observation point (positive normal vector). [Default: false]

colors

Write color data for each vertex. Red, Green and Blue dimensions must exist. Note that most renderers will “interpolate the color of each vertex across a face, so this may look odd.” [Default: false]

normals

Write vertex normals. NormalX, NormalY and NormalZ dimensions must exist. [Default: false]

where

An expression that limits points passed to a writer. Points that don’t pass the expression skip the stage but are available to subsequent stages in a pipeline. [Default: no filtering]

where_merge

A strategy for merging points skipped by a ‘where’ option when running in standard mode. If true, the skipped points are added to the first point view returned by the skipped filter. If false, skipped points are placed in their own point view. If auto, skipped points are merged into the returned point view provided that only one point view is returned and it has the same point count as it did when the writer was run. [Default: auto]