ISO.CEILING in Collabora Office: Round Up on a Sign-Independent Grid
Use Collabora ISO.CEILING for fixed upward rounding, negative coordinates, translated grids and documented CEILING.PRECISE equivalence.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: ISO.CEILING rounds to the higher multiple with a sign-independent step. =ISO.CEILING(-2.3;0.5) is expected to return -2.
Availability and version history
- Introduced: original Collabora release and launch date are not established by the sources reviewed.
- Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
- Platform scope: support in every online or mobile deployment is not inferred from desktop documentation.
- Checked: October 14, 2026. Complete function-specific documentation and independent arithmetic controls; no native Collabora test was performed.
Syntax and documented equivalence
=ISO.CEILING(number[;significance])
Optional significance defaults to 1. Positive values round away from zero; negative values round toward zero. The sign of significance is ignored, and there is no mode argument.
Collabora explicitly states that ISO.CEILING calculates identical results to CEILING.PRECISE. Both names have dedicated sections in the 26.04 help. This guide does not infer retirement or an introduction date from the shared calculation rule.
Examples use English names and semicolon separators.
Example 1: round coordinates upward to half units
Enter -2.3, -2, -1.7, 1.7, 2 and 2.3 in A2:A7:
=ISO.CEILING(A2;0.5)
Expected outputs are -2, -2, -1.5, 2, 2 and 2.5. Every result is at least the original coordinate. Exact grid positions stay unchanged.
Using -0.5 as significance gives the same outputs. A negative step is not a request to move toward the lower coordinate.
Example 2: inspect the default one-unit grid
=ISO.CEILING(2.3)
=ISO.CEILING(-2.3)
Expected results are 3 and -2. The direction is upward on the number line, so “up” means away from zero for the positive input and toward zero for the negative one.
This differs from always rounding the absolute magnitude away from zero. Select a different, explicitly documented mode if that is the actual requirement.
Advanced example: move a rounding grid away from zero
Suppose allowable coordinates are spaced by 0.5 but start at an offset of 0.1: …, -0.4, 0.1, 0.6, 1.1, 1.6, … . For numeric input in D2, use:
=0.1+ISO.CEILING(D2-0.1;0.5)
For inputs 0.2, 0.8, 1.2 and -0.2, expected results are 0.6, 1.1, 1.6 and 0.1. First subtract the offset to work on a zero-based grid, round there, and then restore the offset.
These are finite decimal model expectations away from grid boundaries. Native binary representation near an exact boundary was not tested; retain explicit boundary controls for a production coordinate model.
Advanced check: compare the equivalent documented name
For the same six half-unit inputs in A2:A7, fill down:
=ISO.CEILING(A2;0.5)=CEILING.PRECISE(A2;0.5)
All six expected comparisons are TRUE, following the equivalence stated in Collabora’s own help. This is a documentation-derived consistency check, not evidence from executing both functions here.
Advanced example: round individual readings or their sum
Two positive readings are 0.6 and 0.6, with a step of 0.5:
=ISO.CEILING(0.6;0.5)+ISO.CEILING(0.6;0.5)
=ISO.CEILING(0.6+0.6;0.5)
Expected results are 2 and 1.5. Independent rounding raises each reading to 1; rounding the combined 1.2 raises only the total to 1.5. Record the required level of aggregation.
Limits and troubleshooting
The function name alone does not prove arbitrary-precision arithmetic or compliance with every external standard. The dedicated Collabora help supplies the behavior used here.
Zero significance, mixed-type conversion, exact native error codes, very large inputs and imported-file mappings remain unverified. For a lower bound instead, use a separately documented floor rule such as FLOOR.PRECISE.
References and verification
The complete function section was reviewed. Worked results are independently checked expectations; native execution and unlisted edge cases remain unverified.