This is just a very minor issue that may not need fixing, but I noticed that the OSM File Loader does not check for the existence of the Scratch workspace (and probably also the Default workspace), while being depended on especially the Scratch workspace for intermediate storage.
I only discovered this when I removed a 180GB external SSD to make room for a larger 2TB version. The original drive was set as F-drive, while the new one got assigned I. This caused the not so nicely catched IO error you see in the screenshot, as the F-drive was set as "Scratch" workspace in my Geoprocessing Environment settings.
It is not a big deal, since the first error line is quite clear or explicit about the underlying issue, but the extended error logging below it with more intimidating references to cryptic "IO Errors" is not the most user friendly for non-developer ArcGIS users.
Of course, this is rare corner case, so a won't fix is probably not a big deal, but catching it probably isn't either.
Hi @ThomasEmge,
This is just a very minor issue that may not need fixing, but I noticed that the OSM File Loader does not check for the existence of the Scratch workspace (and probably also the Default workspace), while being depended on especially the Scratch workspace for intermediate storage.
I only discovered this when I removed a 180GB external SSD to make room for a larger 2TB version. The original drive was set as F-drive, while the new one got assigned I. This caused the not so nicely catched IO error you see in the screenshot, as the F-drive was set as "Scratch" workspace in my Geoprocessing Environment settings.
It is not a big deal, since the first error line is quite clear or explicit about the underlying issue, but the extended error logging below it with more intimidating references to cryptic "IO Errors" is not the most user friendly for non-developer ArcGIS users.
Of course, this is rare corner case, so a won't fix is probably not a big deal, but catching it probably isn't either.