Latest Contributions by EricRice

Nathan, Zonal Statistics as Table is a good starting point.  Your polygons will be the zone features, and run it on the greenness and wetness bands separately.  The tool only takes 1 band rasters, so you can't input your multiband dataset. One of the stats returned to you is Mean value per zone. Eric ... View more

Cory, I'm going to stop posting in the other thread (Desktop-General) and only continue in this one.  I just didn't want you to think I was ingoring your other posts... A reinstall might be in order...Can you contact Esri Support? Eric ... View more

No problem.  Good luck! Eric ... View more

Greetings, A couple things stand out in your post as possible culprits.  First, you should install service pack 2 for ArcGIS 10.0.  Second, because you said a brand new computer is being used, you might not have the Java runtime environment Version 6, or higher.  Spline with Barriers will not work without the Java runtime installed. The Java Runtime Environment can be downloaded for free from http://www.java.com/en/download. Hope that helps you out. Regards, Eric ... View more

Which field are you joining on?  I am not having any problems joining the table back to my example polylines.  I used ObjectID for my zone field, and that is the field I join with. Eric ... View more

Throughout this process I have made sure to assign projection and datum information of the LIDAR raster to match that of the NAIP image. It's unlikely that the raw LAS file was collected in the same coordinate system as NAIP imagery is collected in, unless you told your Lidar data provider to do that specifically.  I'd suggested contacting the data provider and asking them what coordinates were used in collection.  Then define the raster to be whatever they say. Regards, Eric ... View more

Hi Ryan, After reading your post and thinking a bit more about this, I don't think Extract by Mask is all that viable.  It would require you to summarize each raster created from selected polylines which is just more work.  This a.m. I ran Zonal Statistics as Table with many polylines (for the zone features) and it worked really well.  The only thing is that it doesn't extract the underlying raster values to form a new raster like the extraction tools do.  It will however, provide you with some meaningful statistics about the underlying pixels. Count, Min, Max, Range, Mean, etc...  All you have to do is join the output table back to your original polylines using the same field you specified in the Zone Field parameter of the tool.  Let me know if this works better for you. Also, do you polylines cross each other? This will be problematic unless managed properly.  What version are you using? Regards,  Eric ... View more

Hi Jo, I think you just need to rebuild the attribute table. Similarly, if you Clip a raster the count field in the result doesn't get updated automatically.  See Creating and deleting raster attribute tables with geoprocessing tools Regards, Eric ... View more

Ryan, Run Extract by Mask and use your polyline as the mask input.  It will pull the values from underneath the polyline and then you can open the attribute table and check the Count field to get the number of pixels.  This tool requires Spatial Analyst, and I'm also making an assumption you're working with an integer raster; Floating point rasters do not have attribute tables. Regards, Eric ... View more

Hi Samantha, We don't always automatically build raster attribute tables.  Try running Build Raster Attribute Table on the result to get the table. By default, the size of a raster attribute table is limited to 65,535 unique values. You can increase this number on the Options dialog box by clicking the Raster Attribute Table tab on the Raster tab. Regards, Eric ... View more

Greetings, You can check if features are inside the multipatch using Inside 3D.  Use the create Complex Output Table (optional) parameter to identify the relationship between the features and multipatches through the creation of a Contain_ID field, which could later be used to do a standard table join. Another workflow would be to run the MultiPatch Footprint tool to get 2d representations of the multipatches and use those polygons to do the spatial join. Then table join it back to the multipatch feature class. Regards, Eric ... View more

Greetings, Did you by chance check the option to Interpolate Vertices Only?  The tool normally densifies the output line to that of the raster cellsize or a TIN's natural densification.  Did you specify your own sampling distance?  You could try further densifying the line in areas where this happens and then rerun the tool. Only vertices store 3d information. Segments between vertices are not actually 3d aware. Can you send a screenshot of what you have so far? Regards, Eric ... View more

Hi Chris, All Spatial Analyst tools support native I/O. We enhanced the underlying Spatial Analyst Engine to support native read/write, which every SA tool relies on. Our development teams did substantial work to make FGDB comparable and sometimes even faster.  Our efforts continue into 10.1 and beyond.  The real benefit is for people who wanted to use FGDB or other formats all along.  i.e. Using FGDB in 10.0 is way faster than using FGDB in 9.3.1. Performance is gained simply by us not creating scratch GRID's behind the scenes.  Also, performance is not the only benefit to native I/O. See below. Any field name and path length limitations imposed by the ESRI GRID format are overcome. (Unless you still choose to use GRID.) The 2.1 GB shapefile size limit is avoided by writing outputs to file GDB or SDE. If supported by the specified input and output formats, time values in the date fields are preserved, and nulls are treated as such and no longer being converted to zeros. Our intention with the native I/O project was not to drive people away from using GRID.  If the field and file name limits never bothered you or hindered you in accomplishing something, please continue to use the GRID format.  It is still definitely one of the top two fastest formats to work with. ... View more

Greetings, It sounds like your data's coordinate system is in geographic coordinates.  Try projecting the data to a projected coordinate system that uses feet/meters.  Ideally, your x, y, and z unit should all be the same.  If you don't want to project the data you can visualize it in ArcScene by going to the Main Menu > View > Scene Properties.  In the vertical exaggeration box type a small number like 0.0003, or try hitting the Calculate From Extent button. Regards, Eric ... View more

Sara, You can run the Int tool from Spatial Analyst or 3D Analyst.   Regards, Eric ... View more