![arcmap intersect arcmap intersect](https://www.dvginteractive.com/wp-content/uploads/2021/02/image-2.png)
You can disable background geoprocessing by going to the Geoprocessing menu in ArcMap, then Geoprocessing Options and unchecking the box next to Enable in the Background Geoprocessing section. Disable Background Geoprocessingīackground geoprocessing sends your data to another process on your computer, freeing up ArcGIS to let you do more work while it’s running – occasionally, it has side effects that don’t occur when running “in the foreground” (where a window pops up and blocks you from doing anything else while it runs). If you do not need those values, simply remove the joins or relates and try running the operation again.
![arcmap intersect arcmap intersect](https://media.cheggcdn.com/study/6b6/6b6bd0e5-825e-4469-b434-07653ca328f5/image.png)
If you need those values attached, one option is to export a copy of that dataset, which permanently writes those values to the attribute table, and then try running your geoprocessing operation again. If one of the layers involved in your geoprocessing operation has an active join on it to attach values in the attribute table, that could be the cause of the error. Here are some naming rules for rasters in Spatial Analyst. It’s worth checking the naming rules of whatever workspace you’re reading from and writing to in order to ensure you don’t have any other invalid characters or names. Another common naming problem in the past was any file path that had spaces – this is less of a problem today than it had been, but it’s often still good to avoid spaces. This isn’t allowed in a name, but it doesn’t have a specific error message to tell you that, so you just have to know. One thing that occasionally creates error 999999 for me is starting a feature class or raster name with a number – this most often happens when I try to start the name with the year the data represents (2016_imagery, for example). Check the names of your inputs and outputs For many years, certain raster operations wanted to use folder workspaces rather than geodatabases, though this has also improved. Finally, check the workspace environment settings. The same rules can apply for outputs – try writing out the results as a different format to see if it resolves the issue. You can try copying the data to a new version of the same workspace – so if it’s already in a file geodatabase, try copying it to a brand new file geodatabase as the only item – or you can try converting it to a different format (export a GeoTIFF, GRID, etc). While ArcGIS has become much more consistent in the last 5-10 years, occasionally a tool may have trouble working with file geodatabase rasters when an Esri GRID format raster works just fine (for example). To put this another way, check the formats of the data you’re providing as inputs or choosing for outputs, as well as the locations they are stored. Map documents can occasionally accumulate problems or small issues related to environment settings you’ve changed, and attempting the operation in a new map document can help rule out these issues. If you’ve been working with the data in ArcMap, try running it in ArcCatalog instead, or try running it in a new, blank map document. Try the operation in a blank map document or in ArcCatalog The easiest way is to often reboot your whole computer.
Arcmap intersect software#
Turning it off and back on again can work! If you want to just reboot the software and not your computer, make sure to kill all ArcGIS programs – you can open your task manager and find ArcROT, ArcGIS Connection Manager, and ArcGIS Cache Manager – make sure to kill each of those processes if they are running. Troubleshooting 101, but we all need a reminder sometimes. Look for any tool specific settings that could create problems – try simplifying your options until the tool runs, which will help you ID the problem.Check your environment settings for anything unusual.Check your projections/coordinate systems.Check the names of your inputs and outputs.Try the operation in a blank map document or in ArcCatalog.Here’s the summary of steps (followed by detailed explanations for each one), in an approximate order of how I try them – though circumstances will vary and you may have a hunch that one of these will work. In this article, I’ll lay out some places to look for the most common solutions to this problem. It is usually accompanied by misleading messages such as “ the table was not found” or something else.
Arcmap intersect code#
But one error message, with error code 999999, is painful to get because it means something went wrong, and even the software isn’t sure what it is. If you’ve worked with ArcGIS, you’ve certainly had your fair share of errors while running geoprocessing tools – many of them are quite descriptive and tell you exactly what’s wrong, while some are specific but cryptic.