Fixing omniscape error “The import file was not found: …”

[sarah-chisholm]

In omniscape, the error “The import file was not found: … omniscape_outputSpatial\cum_currmap.tif” is a general error message that suggests that there is something off with the input files and/or parameters.

There are several built-in validation steps in place for different possible input and parameter inconsistencies, which we continue to extend. So, make sure you are always using the latest package version. Nevertheless, there might still be steps we missed and reporting issues helps us improve.

To help with troubleshooting, here’s a list of common mistakes when parametrizing an omniscape run:

• The file paths must not contain any spaces or special characters
• The input raster layers must have a CRS
• The input raster layers must have the same extent, resolution, and CRS
• The resolution for the input raster layers should be an integer value
• The data type for the input raster layers should be an integer type
• The input raster layers must have “No data” values set as NA
• The “Resistance file” must not contain 0 or negative values
• If providing a land cover raster as the “Resistance file”, make sure the datasheet Optional > Resistance Reclassification > Option has “Reclassify resistance” set to “Yes”, and the > Reclass table datasheet specifies the reclassification values for converting each land cover class into resistance values
• If configuring the “Reclass table”, land cover classes can be converted to NA resistance by setting them to -9999

For tutorials on the omniscape SyncroSim package, visit https://apexrms.github.io/omniscape/tutorials. For additional information about the Omniscape algorithm, please visit the Omniscape.jl documentation.

[Author]

Posts