Currently, GeoWave's usage of the uzaygezen library expects the resultant beginning and end of range to be inclusive, but after further inspection the end of the range is exclusive. This will result in one extra row ID potentially which will be filtered out by the fine-grained constraints filtering, but should still be fixed for accurate usage.