In the latest test build, the load process of the Load OSM File tool leads to warnings about non-existing spatial indexes, both HRESULT E-FAIL warnings at a step where it attempts to run the "RemoveSpatialIndex" tool.
The loading process does seem to finish properly though, including the final creation of the spatial indexes. Is the RemoveSpatialIndex step actually necessary? If it is necessary in some special case, it would be good if the tool actually first checked for the existence of a spatial index, before trying to remove it.
Anyway, it doesn't seem to harm the process as it continues and seems to succeed, only the HRESULT E-FAIL message might a bit confusing and intimidating to users...
In the latest test build, the load process of the Load OSM File tool leads to warnings about non-existing spatial indexes, both HRESULT E-FAIL warnings at a step where it attempts to run the "RemoveSpatialIndex" tool.
The loading process does seem to finish properly though, including the final creation of the spatial indexes. Is the RemoveSpatialIndex step actually necessary? If it is necessary in some special case, it would be good if the tool actually first checked for the existence of a spatial index, before trying to remove it.
Anyway, it doesn't seem to harm the process as it continues and seems to succeed, only the HRESULT E-FAIL message might a bit confusing and intimidating to users...