Latest Contributions by JAMIESOMMA

Thanks Juan, I see the issue and that workaround works for me for now. I appreciate your prompt attention my issue.  Take care! ... View more

OK, I was able to get the rasters extracted as separate TIF files from the NibbleTroubleshooting2.gbd I prepared and tested.  Attaching now. When I run Nibble using these TIF file rasters, I still get the same result: an empty raster with only 0 on the legend. ... View more

Yes, I see what you mean.  The copy/paste of the rasters from my Scratch.gdb to that empty NibbleTroubleshooting.gdb I created didn't work very well as I wasn't able to render them in a new MXD.  So, I copied the Scratch.gdb, deleted everything else and loaded them into a fresh MXD to make sure they worked.  I've included the Nibble Test model with the settings that I used and the NibbleOutput raster showing the same output I've been getting.  I had tried extracting the rasters as TIF format, but ran into errors using the Export menu item from the Catalog view, as well as the Copy Raster geoprocessing tool.  Keep getting 999999 error saying "No spatial reference exists" even though I see this set on the rasters (NAD_1983_Albers).  If you know a better way, please advise! Thanks much! ... View more

Resulting raster size is only 2495 x 883 ... View more

Yes, understood.  What I'm simply noting is the difference between the raster used for the Cell Size parameter in the Tool.  When I use an integer-based raster for this, it works just fine.  When I was using a floating point raster for this, it hangs.  I tested using a 10 meter integer raster instead of the 30 meter integer raster, and it worked as well.  So, it doesn't seem to be the cell size but rather the pixel type of the referenced raster in the Cell Size parameter that seems to be causing the issue. ... View more

The raster settings are based on a 10m DEM of the watershed that matches the extend of the polygon feature being converted.  When I just run Feature to Raster from the Toolbox, I get the same result.  I tried an integer-based 30 meter raster of the same extent just now and it completed in 2.8 seconds.  I guess the issue may be the 32-bit floating point raster at 10 meter resolution that is causing an issue.  I'll try an integer-based raster @ 10 m in the morning and see what happens to that.  Thanks for the reply! ... View more

In case this helps someone else who sees this thread, I'm in the middle of doing this too and I'm taking the following approach: Method: Rational Runoff Method - I am determining the runoff coefficient from a published Rational Runoff Lookup table based on the following characteristics: Soil Hydrologic Group: A, B, C, D (I'm treating the A/D, B/D and C/D groups as D for purposes of the Runoff Coeff since I'm looking at peak flow on a watershed basis).  I'm getting this from USDA's Soil Survey data in the muaggattr table and hydgrpdcd column and converting the soil unit polygons in the Watershed context to a 10 m raster with values for each Soil Hydrologic Group. Slope Class: less than 2 percent, 2-6 percent, and greater than 6 percent. I'm getting this from the USGS 1/3 arc second DEM (~10 m resolution), calculating Slope, and then reclassifying the slope raster into a Slope Class raster in the above specified ranges. Land Cover Class: I've translated these values in terms of the National Vegetation Class System Class code that is used with the USGS Land Cover raster data sets (30 m resolution).  I've taken their text file that maps all raster values to the NVCS Attributes (including the Class code that approximates the land cover types in the Rational Runoff Method table) and imported it to a table and joined this to the Land Cover raster table. I'm taking each of the 3 rasters specified above and then will calculate a new Runoff Coefficient Raster based on looking up the Runoff Coefficient from a Runoff_Coeff table based on the raster values of the 3 input rasters.  [This is the part I'm currently researching how best to do-I think the Combine tool will work for this but I not yet done a Join Field operation with multiple join fields] This Runoff Coefficient Raster will then serve as the Input Weight Raster for the Flow Accumulation Tool. I'll Extract from Points the Flow Accumulation at each Pour Point and then calculate the effective area of rain harvesting based on the area of each cell in the Flow Accumulation raster.  So if 200,000 cells pour in without weighting for Runoff Coefficient, then something less than this would be the count using the Input Weight Raster based on the runoff coefficient for each cell and this would be the effective rainwater harvesting area for the peak flow calculation. ... View more

Original post was under ArcMap v10.6.1.  I've upgraded to 10.7.1 but still seeing the same issue. ... View more

I've got the same question.  I'm looking to run it both ways, but when I'm running Snap Pour Points tool for a set of 15 points on a flow accumulation raster, it's hanging.  I'm needing to do this because though 13 points which were generated from places along the stream line feature still coincide with the stream line raster cells in the flow accumulation raster, 2 of the points are just off of the stream raster cells and need to be snapped over just a little bit.  I'm using ArcMap 10.6 and the Snap Pour Point tool repeated hangs, even when just running it against a single point.  Thanks in advance! ... View more

Same issue. Using ArcMap version 10.6. ... View more