Closed 1lutz closed 2 years ago
I noticed that using the small demo dataset a workflow with Point in Polygon does not fail even if "EMPTY_STRING_AS_NULL=YES" is not set. The option seems to be only needed for the larger dataset Amphi_env.csv I got from NFDI (The text field "Method/Device" is sufficient to cause the error).
Is the problem that is stores a null bit in the bitmap or that it stores some empty string in the data buffer?
Maybe NullableText
just behaves wrong. I guess we just have to check that we either store a null and return a null or store an empty string an return one (and don't claim that this is null).
cllosed by #486
Consider the following csv file: lonlat_empty_field.csv
This file will be loaded using a standard OgrSource. The
FeatureDataRef
returned by thedata
-method identifies the string in the scond row as NULL. This can be seen in the following test:But at the same time the
MultiPointCollection
itself stores an empty string:This discrepancy could lead to the problem that the Point in Polygon-Operator throws an error.
Possible solution
The GDAL OpenOption "EMPTY_STRING_AS_NULL=YES" can be set (which is done in #486). In that case the MultiPointCollection will store the second string cell as NULL and the Operator functions properly:
I do not know the exact reason why the data inside the
FeatureDataRef
and the internal data inMultiPointCollection
happens to be different yet.