io
Wrapper for LayerQuery that binds it to some function that is able to produce a resulting value.
Base trait for layer headers that store location information for a saved layer
Accumulation of LayerFilters that will be asked to filter layer KeyBounds
Accumulation of LayerFilters that will be asked to filter layer KeyBounds
Type of key for the RDD being filtered
Type of metadata used for filtering
Type class to read a raster either fully or partially from a ByteReader.
Type class to read a raster either fully or partially from a ByteReader. This abstracts over the different ways to represent a GeoTiff values and different ways to key it.
Option object is a type parameter such that novel ways of GeoTiff parsing can be provided by the user.
Options type that is used to configure the raster reading
Result of reading the raster bytes either fully or as a pixel window
A key-value reader producer to read a layer one value at a time.
A key-value reader producer to read a layer one value at a time. This interface abstracts over various construction requirements for constructing a storage back-end specific reader.
LayoutScheme Format
LayoutScheme Format
Avro serialization doesn't support Float.NaN or Double.NaN.
Avro serialization doesn't support Float.NaN or Double.NaN. Whereas a union of number and null is sufficient in cases where the nodata value for some domain is can be serialized (Int.MinValue is just another integer and, therefore, serializable without difficulty), we are in need of an alternative strategy for floating point serialization.
To this end, we've serialized with a union of boolean and floating point values. noDataValue can either be: 1. true (and, therefore, ConstantNoData) 2. false (NoNoData) - OR - 3. a floating point value (which is a UserDefinedNoDataValue's value)
Avro serialization doesn't support Float.NaN or Double.NaN.
Avro serialization doesn't support Float.NaN or Double.NaN. Whereas a union of number and null is sufficient in cases where the nodata value for some domain is can be serialized (Int.MinValue is just another integer and, therefore, serializable without difficulty), we are in need of an alternative strategy for floating point serialization.
To this end, we've serialized with a union of boolean and floating point values. noDataValue can either be: 1. true (and, therefore, ConstantNoData) 2. false (NoNoData) - OR - 3. a floating point value (which is a UserDefinedNoDataValue's value)
Avro serialization doesn't support Float.NaN or Double.NaN.
Avro serialization doesn't support Float.NaN or Double.NaN. Whereas a union of number and null is sufficient in cases where the nodata value for some domain is can be serialized (Int.MinValue is just another integer and, therefore, serializable without difficulty), we are in need of an alternative strategy for floating point serialization.
To this end, we've serialized with a union of boolean and floating point values. noDataValue can either be: 1. true (and, therefore, ConstantNoData) 2. false (NoNoData) - OR - 3. a floating point value (which is a UserDefinedNoDataValue's value)
Avro serialization doesn't support Float.NaN or Double.NaN.
Avro serialization doesn't support Float.NaN or Double.NaN. Whereas a union of number and null is sufficient in cases where the nodata value for some domain is can be serialized (Int.MinValue is just another integer and, therefore, serializable without difficulty), we are in need of an alternative strategy for floating point serialization.
To this end, we've serialized with a union of boolean and floating point values. noDataValue can either be: 1. true (and, therefore, ConstantNoData) 2. false (NoNoData) - OR - 3. a floating point value (which is a UserDefinedNoDataValue's value)