IFClite TypeScript API
    Preparing search index...

    Interface ParseStreamOptions

    interface ParseStreamOptions {
        dataModelEntities?: "all" | "rooted";
        skipCacheProbe?: boolean;
        tessellationQuality?: "lowest" | "low" | "medium" | "high" | "highest";
    }

    Hierarchy (View Summary)

    Index
    dataModelEntities?: "all" | "rooted"

    Which rows the data model's entities table carries (#6034). Omitted = 'all': every STEP instance in the file, as before.

    'rooted' keeps only the objects (IfcRoot subtypes, the rows with a GlobalId) plus every non-rooted instance another data-model table references by id (materials, material sets, classification and document references), so no relation dangles. The geometry-and-property plumbing nothing points at (IfcCartesianPoint, IfcFace, IfcPropertySingleValue, ...) is left out; on large models that is most of the table. Property values, quantities, materials and the spatial tree are unaffected.

    The two variants are separate server cache entries, so pass the SAME value to the parse call and to IfcServerClient.fetchDataModel: a rooted parse writes only the rooted table, and fetching without the option asks for the full one.

    skipCacheProbe?: boolean

    Skip the hash-only cache probe and upload straight away (#3901).

    The probe costs one round trip plus a local SHA-256 of the file, and saves the entire upload when the server already has the model. Turn it off when you know the server is cold, or when hashing locally is the expensive part (a very large file behind a fast link).

    tessellationQuality?: "lowest" | "low" | "medium" | "high" | "highest"

    Tessellation detail level (#976). Omitted = 'medium', which is byte-identical to the historical output — and to what the wasm path produces without setTessellationQuality, so client-side and server-side meshes stay in parity. Non-default levels get distinct server cache entries.