Latest Contributions by DarrenWiens2

I believe your most direct change may be to insert the 'dir' in between 'root' and 'fc' (which should result in the full path): Dict[fc].append(os.path.join(root,dir,fc)) ... View more

Your options for rotating point symbols are like below, neither of which follow your example. The script Dan references uses the Arithmetic option (or at least, I think it does) If there is a problem with the script, please respond in that thread. As I'm not exactly familiar with the possible types of bearing, can you provide a complete example of which type of bearing you're looking for? I'm finding examples where direction is also incorporated (e.g. 10.5 degrees N of E vs. 10.5 degrees E of N), which won't be described by a number alone. ... View more

Because all of the values are all less than 1, I also found I cannot use the Reclassify tool. This doesn't seem true to me. I just ran Reclassify with rasters all negative, and decimals between zero and one. What is the error, or problem, with running Reclassify? ... View more

Make sure you use == in Raster Calculator. For example, "YourRaster" == 1 ... View more

I would use your known observation points (the places you don't want to see your path from), not your unknown proposed path, for the viewshed analysis. Find the visible areas, or most often visible, and then place your line. After you've invested the time to calculate all (or a sample of) visibility from observation points, you are set up to use the resulting rasters as a cost surface (i.e. calculate the least cost path, where cost = number of times visible). ... View more

I have seen this before. I think it's acceptable as long as it's made perfectly clear that these are overlapping polygons, because that is not the usual way to treat polygons. It can be extremely annoying to find out that there were overlapping polygons, after you've done any sort of processing (area summaries, for example). edit: it really depends on how you want to use the polygons. If overlapping polygons work for your application, great. If not, try something else (symbology, flatten the whole structure, etc.). ... View more

I think it is like: SetNull(if this condition is false, use these cell values) ...so: SetNull("Lakes","YourOtherRaster") ... View more

Use Con. Con(IsNull("LakesRaster"),"YourOtherRaster") edit: ...or SetNull​ edit: ...or this extremely convoluted method​ ... View more

There are many ways to do this: 1.) Extract by Mask​ using either raster or polygon 2.) Clip via Image Analysis Window​ using polygon 3.) Con using raster ... View more

Thanks, Curtis Price​. Interesting complexity intrinsic in the simplified (my words) product. ... View more

I might be missing the fine details, but it seems to me you can use in_memory as the workspace environment in ArcMap (although you bring up valid reasons why not to do so): >>> arcpy.env.workspace = 'in_memory' >>> arcpy.CopyFeatures_management("Flood200yr_0cm",'copy') <Result 'in_memory\\copy'> ... View more

Dan, I think the issue is that even though the Copy Management output is pointing to 'in_memory' it is being saved to a physical GDB. Or, perhaps I'm misunderstanding the Result object - I assume the response to getOutput would be the layer held in that GDB, not 'in_memory' where it should be. Daryl, is the GDB set as your default GDB, or otherwise, why is this the location? Have you set it as some other type of environment? I'm not on Pro, so can't test anything, but you're right, something fishy is going on - your code works as expected (saving to 'in_memory') in ArcGIS 10.2. ... View more

1.) Do your interpolation between the points. Don't worry that it will interpolate for areas far away from your line as well as on it. 2.) Buffer your line by some distance to make a line-shaped polygon. 3.) Extract the cells of your interpolation raster that overlap your buffer. 4.) Symbolize. ... View more

There's a 10 year old thread here that has lots of ideas, especially: Here is the solution that I came up with... First close all of your esri windows to make sure the file in question is not in use. Then delete the lock file in Windows Explorer. Change the name of the original file (put an "a" after it or something similar), this is because if you have recently worked with the file then ArcCatalog will try to go directly to the corrupt geodatabase, but if it has a changed name then the error won't come up. Anyway I am getting ahead of myself. With all the ESRI windows still closed. open the copied version in MS Access. It will tell you that the file you are trying to open is either not a database or it has become corrupt and it will ask if you want to fix it. Say yes. Then open that file up in ArcCatalog and things should work. I hope this helps. ... View more

Can you open it in Access? ... View more