Latest Contributions by RyanDeBruyn

This post might be of some help for reference.   See the CalcZonalMeanAspect sample. Calculate mean aspect for polygons ... View more

Hi Kimberly.  Thank you for your post.  This might point to an underlying issue not necessarily related to Extract.  Would you be able to zip up and attach your data here (assuming it is not too large) so I can test it on my side. In the mean time as a workaround are you able to convert the feature mask to raster  (Use FeaturetoRaster conversion tool) first then use the extract by mask tool with the raster input?  Make sure to set environments  (coordinate system, cell size,  snap raster) to be consistent with underlying raster. ... View more

Thank you Caiti, that is helpful. So for one case you have a raster dataset with 242 bands.   Adding them all at one time the validation in the tool is taking a long time, because there are so many layers, with each change it has to validate all of them again.  That is a big pain and I can understand your frustrations.  Please contact customer support and log a bug for this issue when loading many layers into the tool.  My suggestion at this point, 1) Use a file geodatabase point feature instead of the shapefile.  The field issues will improve as there is no field name length limiations as in shape fie. Also it supports <NULL> (nodata). 2) How savy are you with python?  Best bet would be to loop through the raster bands one by one and extract the value. This would mimic running the tool if mutlibands was working correctly for you.   I created a sample scipt tool.  See the attached .zip file.  Run the tool and specify the full path to your input (fgdb feature, input multiband raster dataset).  Give it a whirl. Feel free to modify it as needed. Good luck. -Ryan ... View more

I have the same problem with the first value being written across all fields (v.10.2). The link above does not seem to link to 10.2.1. Unless I'm missing something? As for the workaround, I have 242 fields in each raster file and 10 rasters to extract points from. files. Entering 2420 layers individually as a workaround is not a welcoming idea.  Any other ideas? Or is there an alternative link to 10.2.1? The link references the defect (NIMBUS change request) that was resolved. You would need to sign into arcgis with your global account to view the details. This may or may not be of any help to you. This particular issue is with multiband raster as input.  The workaround suggested would be to specify each of the indivual rasters bands as input rather than the single multiband raster dataset.  This result of this tool will only extract the value of each input raster specified.  So if you have 10 input rasters(or bands), you get 10new fields (the VALUE for each). What is your ultimate goal or requirment?  Can you provide the steps you are following to produce your issue? If possible I would recommend to contact customer support for assistance, there we can get your issues resolved in a timely manner. Regards, -Ryan ... View more

Now we're talking! Thanks Steve, this looks great. Any advice on using the toolbox? I downloaded it, and change the python scripts per the txt file, but whenever I try to open a tool it says "Invalid Tool. Unable to execute the selected tool." Scott what version of ArcGIS are you using? Are you refering to changes in the ReleaseNotes.txt needed for the tools to work with 10.1 rather than 10.1 service pack 1 as required? ... View more

Yes, those tools are cool...however, you may need the Spatial Analyst and a higher ArcGIS Desktop license to run any or all of the associated tools.  The requirements for the supplemental tools are: ArcGIS 10.1 Service Pack 1 and Spatial Analyst Extension Only the Filled Contours tool requires ArcGIS for Desktop Advanced or ArcGIS for Server Advanced and Spatial Analyst Extension. ... View more

I have installed ArcGIS10.1 and SP1 but when I use the Extract Multi Values to Points with a multi-layer tiff I want to get the values from, the program writes the same first value into all columns of the file. I desperately need to use the tool. Any ideas what is wrong???? This issue was resolved in the next release of 10.2.1 http://support.esri.com/en/bugs/nimbus/role/beta10_1/TklNMDg1MTI4 Sorry for the inconveinence.  The work around solution for this is to add each of the individual bands of the raster as input, rather than one parent raster dataset. ... View more

Hi Ryan, I use ArcGIS Desktop 10.0. Does the SP1 apply to ArcGIS 10.0 as well ? or only 10.1 ? I made a model using the solution provided in this thread, but even that is not as efficient as the tool used to be. I am still confused in regard to why a tool that worked fine before does not work anymore even though I am using the same datasets, same projections, same version of ArcGIS. best, Yvan The fix is only available in 10.1 SP1 and greater. Not sure as to your difference. Something must have changed, make sure your repro steps are exactly the same.  Perhaps the order of rasters has an effect in your case?  If only one of your datasets has nodata values, try to put that raster as the last raster in your input list. You would need to investigate your point locations and rasters to tell.  To trouble shoot... you can look at the result of indiviual rasters to verify if any points fall on a raster NOData (null) cell.  Keep in mind if format .shp  NoData will be 0, and NULL  in a file geodatabase. Goodluck. Regards, -Ryan ... View more

YVanGS, What version of the software are you using? Including this info, is helpful to narrow down any related issues. Regarding to the issue identified in this thread with respect to NULL values, there was an issue found when an input point fell on a cell that had a NoData value and multiple input rasters were provided.  This issue (http://support.esri.com/en/bugs/nimbus/role/beta10_1/TklNMDgxNDY2), was resolved in 10.1 SP1. If your input contains NoDATA, one workaround as mentioned a post, was to use a loop to iterate through each input raster individually. This can be done is a python script or Model Builder using a raster iterator. Any further issues you have it is best to contact technical support and submit an issue directly, that way we can work towards resolving the issue or providing the proper information for you to continue with your work. Regards, -R ... View more

jgrand, your issue is the use of the python boolean "or" instead of the map albegra operator "|". Please refer to the help topic for working with map algebra operators and their precedence: http://resources.arcgis.com/en/help/main/10.1/index.html#//00p600000008000000 Regarding the ambiguos error.... This exception has to do with the overloading of operators. The bitwise operators (like '&') are used in arcpy.sa to overload the Spatial Analyst boolean operators (unfortunately, we cannot overload the boolean operators). But we don't control the operator precedence rules, so arcpy.sa's boolean 'and' has the precedense of Python's bitwise 'and'. Look here for Python's precedence rules: http://docs.python.org/2/reference/expressions.html#operator-precedence This error is always thrown when Python tries to coerce a raster to a single boolean value. The general Python rule is that class instances always evaluate to True. However we need to think of rasters as number-like objects, not as Raster class instances. While you can cast a single number to a single boolean value, you cannot do it for a collection of numbers like a numpy array and a raster. So, whatever values are in the raster, if we don't catch this situation like we do, a raster instance always evaluates to True. People would be writing code like this and be confused: if raster:   print "True!" else:   print "False!" False will never be printed, whatever the values in the raster are. By throwing an exception we want to guard people from assuming that we support spatial conditions. Here is another example: >>> out = raster1 == 1 & raster2 == 2 Traceback (most recent call last):   File "<interactive input>", line 1, in <module> ValueError: The truth value of a raster is ambiguous. Invalid use of raster with Boolean operator or function. Check the use of parentheses where applicable. From the precedence table it can be seen that the bitwise operators have a higher precedence than the comparison operators, so they will execute first: out = raster1 == (1 & raster2) == 2 This is equivalent to: tmpA = 1 & raster2 out = raster1 == tmpA and tmpA == 2 Using types out = rasterA and rasterB Now Python tries to coerce the raster operands to boolean values, which triggers the exception. Providing correct perenthesis the expression will execute successfully. >>> out = (raster1 == 1) & (raster2 == 2) ... View more

It is important to note for those of you finding this issue that the extra classes are a result of input values not being accounted for in the input reclassification table (remap). Whether entered manually, provided by default, or through the available tool classification methods. For the case defined in this post, the input raster is a floating point raster with many unique values. The method of creating the remap was based on an estimated histogram, which calculated a minumum and maximum not equivalent to the actual range of values in the input raster. Therefore, not all input values were correctly classified, and by default, missing values in the reclass table retain their input value (the option is to map them to NoData), hence the extra output values. To correctly classify your data your options are to, 1) manually edit your reclassifcation table range of values and provide the correct break values (including the actual maximum). 2) use Windows registry setting to calculate the histogram using all unique values (as mentioned in the KB article by Eric). Please note this may take extra time depending on the size of your dataset. 3) if the desired output is a sequential range of values (ie, 1-9) you can try the Slice tool. We will work to find a way to provide you with the most accurate reclassification table by default, in the mean time hope this helps you get your work done. Regards, -Ryan ... View more

Hi Marsha, Sometime we find there are issues with NonGrid formats so it might be worth it to compare to using GRID raster as input if you can. (However it should be fine with the .img and ideally there should be no difference. (It is just a suggestion as a workaround). It could be an issue when handling all the inputs together in one go. See if it is any different if using only a few raster compared to all 13. I would suggest that you contact esri support and provide them with the data so they can identify the issue and help provide you with a viable workaround or solution. Regards. -Ryan ... View more

Hello Marsha, What version of ArcGIS (service pack?) are you running? What are the formats of your data? (ie, file geodatabase raster, etc...). If FGDB raster  input can you try converting the rasters to GRID (if possible) and comparing the times. Thank you, -Ryan ... View more

Andy I think the issue is your table is not ordered. * The values to be mapped (individual or range of values) must be in ascending order, with the lowest value listed first.  # Example 1 # Remap of values. 100000 : 1 200500 : 1 201000 : 1 207000 : 99 208000 : 1 209000 : 5 It is mentioned in the help topic, sorry that you missed it and that you have lost time. Hope this works for you. Regards -Ryan ... View more