Skip to content

Commit ec43dd4

Browse files
committed
Refine the wording
1 parent 8dbe0da commit ec43dd4

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

Geospatial.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -104,10 +104,18 @@ crosses the antimeridian line. In geographic terminology, the concepts of `xmin`
104104
For `GEOGRAPHY` types, X and Y values are restricted to the canonical ranges of
105105
[-180, 180] for X and [-90, 90] for Y.
106106

107-
When `GeospatialStatistics` is present, a bounding box is omitted if and only if
108-
there are no X or Y values — that is, if either the X or Y column contains only
109-
NaNs. Similarly, Z and M statistics are omitted if and only if there are no Z or
110-
M values, respectively.
107+
When `GeospatialStatistics` is present, writers must omit zmin and zmax if and
108+
only if there are zero non-NaN Z values in the column chunk, and must omit mmin
109+
and mmax if and only if there are zero non-NaN M values. The bounding box must
110+
be omitted entirely if and only if there are zero non-NaN X values or zero
111+
non-NaN Y values in the column chunk. If Z or M values are missing, the writer
112+
may still include a bounding box using only the available dimensions.
113+
114+
Readers may interpret the absence of a bounding box, zmin/zmax, or mmin/mmax as
115+
an indication that all corresponding values are null, and may use this
116+
information to skip data during predicate evaluation. For example, a reader may
117+
skip a row group if the bounding box is absent, indicating that all X and Y
118+
coordinates are null.
111119

112120
```thrift
113121
struct BoundingBox {

0 commit comments

Comments
 (0)