Description
Report the two-dimensional half-open cross-section bounds and explicit emptiness of one integer fixed-axis voxel-box slice; no cell enumeration or interpolation.
A voxel is a cell on a three-dimensional integer lattice. Coordinates use [x, y, z] order; a box uses an inclusive low corner and exclusive high corner, so its dimensions count cells rather than physical distance. Occupancy records can repeat the same cell without creating extra occupied space.
Report the two-dimensional half-open cross-section bounds and explicit emptiness of one integer fixed-axis voxel-box slice; no cell enumeration or interpolation.
When to use this tool
Use this tool to report the two-dimensional half-open cross-section bounds and explicit emptiness of one integer fixed-axis voxel-box slice; no cell enumeration or interpolation.
How to use the tool and how it works
- Enter low, high, axis, coordinate using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.empty, result.axes, result.low, result.high. Use the ordering, boundary rules and absence conditions described below.
Compare the fixed coordinate with low inclusive and high exclusive on the selected axis. Return empty plus the two remaining axes and bounds.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| low | Inclusive low [x, y, z] integer corner of the named half-open box. | Dense list of at most 128 finite numbers; integer/shape constraints above also apply. |
| high | Exclusive high [x, y, z] integer corner of the named half-open box. | Dense list of at most 128 finite numbers; integer/shape constraints above also apply. |
| axis | Axis index: 0 = x, 1 = y, 2 = z. | A finite safe integer within the operation’s stated bounds. |
| coordinate | A single [x, y, z] integer cell coordinate; a slice instead uses one integer axis coordinate. | A finite safe integer within the operation’s stated bounds. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.empty | Whether the requested fixed coordinate lies outside the selected axis interval. |
| result.axes | The two original axis indexes remaining in the slice. |
| result.low | Inclusive low corner projected onto the remaining axes. |
| result.high | Exclusive high corner projected onto the remaining axes. |
{
"input": {
"low": [
0,
0,
0
],
"high": [
2,
3,
4
],
"axis": 1,
"coordinate": 3
},
"output": {
"result": {
"empty": true,
"axes": [
0,
2
],
"low": [
0,
0
],
"high": [
2,
4
]
}
}
}Limitations and assumptions
- The remaining bounds are returned even for an empty slice; check empty first.
- Voxel components are integers from −1,000,000,000 through 1,000,000,000; dimensions are three integers from 1 through 1,000,000. Counts or strides returned as decimal text use exact integer arithmetic. No physical voxel size is assumed.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Keep cell coordinates, storage order and physical scale separate. Use coordinate conversion for a different memory layout and a separate meshing or geometric model for rendered surfaces.
References
Similar or alternative tools
- Voxel Axis Order Stride Record
Compute exact per-axis voxel strides for an explicit fastest-to-slowest axis permutation; distinguish physical axis order from a fixed row-major convention.
- Voxel Box Boundary Cell Count
Count distinct boundary voxel cells of a positive-size integer cuboid as total minus strictly interior; edges/corners count once.