Temporary raster - what if TEMP/TMP is readonly?

KeithOlson

I'm developing a tool in VB.Net that involves some raster processing using temporary datasets for the intermediate steps.  Typically, ArcMap does this by storing the temporary rasters in the folder specified by the system TEMP or TMP variables.  These temporary rasters go away automatically when they are no longer referenced or when I release the objects in code.  Everything works perfectly fine according to ArcObjects documentation.  That is, unless the value of TEMP/TMP points to a folder that is not writeable by the user. 

For example, I have a user with TEMP/TMP set to "C:\Program Files\ArcGIS\Bin" (which I'd advise against, but that's a different story).  When the user runs my tool, ArcMap cannot save the temp rasters to that location and the tool crashes.

Is there a better way to handle temporary rasters?  I've seen some sample code that uses a hardcoded "C:\temp" location, but I don't think that's the best practice either.

thanks for your help,
Keith

KeithOlson

Finally solved this one.  For anyone interested, we actually discovered that the problem was due to the user's regular temp space (C:\Users\<username>\AppData\Local\Temp) being filled up.  ArcGIS uses the same temp folder as many other applications, so if proper garbage collection is not performed or if apps using that temp space crash, etc. the temp files get left behind.  Over time the folder will fill up to its allocated limit.  When this happens, ArcMap detects that the folder is full and moves on to the next location it thinks might be good to store temp files, which in our case was in C:\Program Files... which the user is not allowed to write to. 

We had the user manually empty his temp folder and then the tool ran successfully. 

So, our solution then was to catch the exception and give the user a message that his temp folder is full and that they need to delete files there before proceeding.  We also noticed that ArcMap does not delete scratch workspaces upon exit like it does other temp data, so we went ahead and added code to delete all scratch workspace files when the tool is finished.