Closed pokulo closed 10 years ago
added a HACK to let the FeatureIterator call the connector()->loadBinaryData() in GdalFeatureTableConnector::loadBinaryData (only if FeatureCoverage is stored as Parent of the Table)
resolved by giving the dataobject the correct url and thus the correct connector is created. Note that this might yet solve the storing issue but that is a seperate thing and with this change probably easy to solve. The internalstate of the table is now correct ( with the correct connector)
Since load/storeBinaryDdata of GDAL Feature files is done solely by the GdalFeatureConnector the should be a proper connector or other mechanism that makes sure that binary data is loaded or stored even if only the FeatureCoverages AttributeTable is used. I could not figure out, how to call the coverages connector from the tables connector.