Currently if there is a datatype mismatch, then the data is still inserted into TileDB, but it's effectively junk.
If an Attribute like ReturnNumber is initialized in TileDB as a uint8, but it is ingested into SilviMetric as a float64, then the data is still inserted into TileDB, but with the wrong stride size, and we end up with 8x more values for ReturnNumber than something that isn't messed up.
Currently if there is a datatype mismatch, then the data is still inserted into TileDB, but it's effectively junk.
If an Attribute like ReturnNumber is initialized in TileDB as a
uint8
, but it is ingested into SilviMetric as afloat64
, then the data is still inserted into TileDB, but with the wrong stride size, and we end up with 8x more values for ReturnNumber than something that isn't messed up.