In the ArcMap 'geoprocessing options' window there is one of the options 'never delete' which seems the best one.
Why this is not default?
I noticed that my settings were set to 'delete after two weeks'. I changed it to 'never delete' so I was able to see what I was doing in the past. Does this setting have an influence on the speed or any other thing?
First thing is that this setting is not doing what you think. it does keep them forever. This just pertains to the results window.
No data will ever be deleted.
Each time you open ArcCatalog or a map document, the contents of the Result tab must be loaded. The more entries you have, the longer it will take to open the application.
To help you manage the number of results, you can choose a duration for keeping results, as shown below.
Keep results younger than option
When you close ArcCatalog or a map document, entries older then the duration you choose will be removed from the Results tab.
NOTE: No data will be deleted—just the entries in the Results tab are removed.
you must save your work in .mxd format. You need to open the saved file when you start your Arc map. It is just practice of using the software nothing else.
Keeping results is indeed useful for repeating operations you did before on other data. I also keep this setting on "keep forever" and I've not experienced slowdowns due to this yet.
I think Lars got the point. I know taht data won't be deleted and I understand how mxd file works. I was thinking on keeping step by step method (what did I do to get certain shape file, tif etc.).
I am going to turn it ot keep forever and I hope this won't slow down the processes..
thanks for all comments!
I must add that I have lots of RAM and a fast processor at the PC at work (32GB, and a Core i7), don't know how it looks on slower PCs. You can also chain certain processes you want to repeat using the Model Builder.
http://video.esri.com/watch/663/getting-started-with-modelbuilderhttp://www.gistutor.com/esri-arcgis/18-advanced-arcgis-tutorials/43-arcgis-model-builder.html
This way you're able to save workflows as custom tools you can apply on different data. It chains together tools from the toolbox basically (similar to scripting, I guess), and it's also possible somehow to add conditions etc.
Yeah, thanks for the tip. I use modeling a bit. Just sometimes it is great to see what happend with certain file and how (and when) it was processed or used as an input. That's why this results window is so interesting for me.
- Badges
- Science topic
- Similar topics
- Geoscience
- Geoinformatics
- Geographic Information System