You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently no work around exists other than to fix/compile your code to get around this, or you just define the schema path inside the gml/xml to find the schema file.
One would expect they can give a file path to a schema with spaces using the XSD= option!
This is the latest release 4.2.1
I am running on a Windows 10 OS
The text was updated successfully, but these errors were encountered:
When calling driver_options_ = CSLAddString(driver_options_, "XSD=C:\path with space\gmltest_1.0.0.xsd");
with
OGRDataSource* poDS = (OGRDataSource*)GDALOpenEx(filenametouse.c_str(), GDAL_OF_READONLY | GDAL_OF_VECTOR | GDAL_OF_VERBOSE_ERROR | ((bUpdate) ? GDAL_OF_UPDATE: 0) | GDAL_OF_SHARED, allowed_drivers_, driver_options_, NULL);
Fails to find the schema. NOTE if you set the path with spaces in the XML/GML file, it works one would expect.
The reason this does not work is because of an assumption/bug when things get tokenized.
As when this gets called:
std::vector OGRGMLASDataSource::BuildXSDVector(
const CPLString& osXSDFilenames)
It splits the the file path up because of the spaces (flags are 0)
char** papszTokens = CSLTokenizeString2(osXSDFilenames," ,",0);
Currently no work around exists other than to fix/compile your code to get around this, or you just define the schema path inside the gml/xml to find the schema file.
One would expect they can give a file path to a schema with spaces using the XSD= option!
This is the latest release 4.2.1
I am running on a Windows 10 OS
The text was updated successfully, but these errors were encountered: