@cityjson/flatcitybuf
    Preparing search index...

    Interface Int64Policy

    How a Long/ULong attribute -- a bigint after decoding -- is spelled in the emitted, JSON-serializable document. See emitInt64.

    interface Int64Policy {
        int64?: "lossy-number" | "decimal-string" | "error";
    }
    Index
    int64?
    int64?: "lossy-number" | "decimal-string" | "error"

    'lossy-number' (the default) emits a JS number, rounding beyond Number.MAX_SAFE_INTEGER; it is what makes whole-line comparison against the conformance oracle meaningful. 'decimal-string' keeps every digit at the cost of changing the JSON type from number to string. 'error' throws InvalidAttributeValue rather than lose a digit silently. No policy ever leaks a bigint into the emitted object.

    Settings
    Member Visibility

    On This Page
    Properties