Latest Contributions by EricRice

Give Zonal Geometry as Table a try. Or convert your viewshed raster into polygons and calculate area as you normally would. Best, Eric ... View more

Nicole, If you follow the second link in Carrie's post it will take you to Mosaic to New Raster.  This tool runs even on a basic license.  There is zero restrictions for using it.  Creating a Mosaic Dataset does have licensing restrictions noted also in Carrie's post.  Spatial Analyst is not related/required to create a mosaic of two or more raster datasets. Since there are at least 4 or 5 ways to mosaic data together, which tool are you clicking that is giving the error? Best, Eric ... View more

I just want to add that you can pretty much do anything you want with an .ecw file in ArcGIS.  It is fully supported by the core product.  Yes, there are restrictions on "serving" them without extra licensing, and we also do not "write" this format, but other than that you should be able to do want you want in terms of conversion/geoprocessing/etc...assuming you have enough disk space. 😄 Best, Eric ... View more

Even if you have just the basic license you can create a raster catalog to get the footprints.  They will be the extent of each image and do not have options like calculating by radiometry which the mosaic dataset has, but it can get you mostly what you want.  Best, Eric ... View more

Unfortunately the ECW .dlls that are provided with ArcGIS Desktop do not allow you to extract from or convert ECW images over 2GB. This is a licensing restriction on the publicly available ECW sdk. However there is a work around to this. There is no such restriction on ECW files in ArcGIS.  I just ran Split Raster on a 4.5GB ECW file and created 100 Tiff files totaling ~110GB of data in 3 hours of processing time. Best, Eric ... View more

Ben, Go to the raster layer properties > Source tab and check the uncompressed size.  The size on disk is the compressed size. Best, Eric ... View more

You sir are correct.  It's the Raster to Polygon and Raster to Polyline that are strictly integer/string input.  Thanks for catching my mistake! So, just run Raster to Point... Best, Eric ... View more

Raster to Point is the tool to use, but you will find that it doesn't allow floating point input.  It is required that an integer raster be input.  You can run the Int tool to truncate the decimals, or if you need to retain the decimals then multiply the raster (Times tool) by 10, 100, 1000 etc... depending on how many digits to the right of the decimal you wish to maintain.  After multiplying, run Int, then convert to points.  In the point attribute table you should see the Value field (sometimes called GRID_CODE) that stores the raster value.  You can use the field calculator to divide by 10, 100, 1000 to get your decimals back. The other tools you mention require you have existing points and you sample the DEM using those points.  So if you don't want to fuss with multiplying and field calculations, you can run Int tool, then convert to points, then use those points to sample the original 32 bit floating point DEM.  i.e. Extact Values to Points, Sample, etc.. Best, Eric ... View more

Actually please ignore me I just read you comment further up. How about using the 'Build Boundary' tool on your mosaic dataset? http://resources.arcgis.com/en/help/main/10.1/index.html#/Build_Boundary/001700000086000000/ The boundary merges all the footprint polygons to create a single boundary  representing the extent of the valid pixels.  So, you have to fix the footprint polygons first, since the boundary layer is basically a  'merge' and 'dissolve' of the footprints. You can get the footprints very close to how you want them, then build the boundary, and if some minor edits are still required then manually editing shouldn't be all that bad by this point. I would hold off on optimizing the mosaic dataset (building overviews) until the footprint/coverage is sorted out. Best, Eric ... View more

Its a pity the Raster to polygon doesn't work as it should. The Raster to Polygon tool isn't really meant for imagery.  The tool is primarily designed for single band integer raster datasets.  If you input a multi-band "image", the tool operates only on the first band.  It will essentially create a polygon for every cell in the input unless of course two or more adjacent pixels share the same value.  If you give it a small raster that is 10k x 10k you'll potentially end up with 100,000,000 polygons.  Raster to Polygon does not and is not intended to create a radiometrically correct footprint feature class. See Recalculating footprints radiometrically which basically takes you to the Build Footprints tool previously mentioned.  Note, it usually takes playing around with the values, shrink distance, and vertice counts a couple times before you get the desired output. Best Regards, Eric ... View more

Hopefully when you're clipping you're using the Image Analysis Window > Clip function so that you're not having to do a data export and actually save that clipped raster to disk.  I think most people draw a graphic to clip to, but I just verified that if all you do is zoom in and hit the clip function it clips to the view extent.  Then I used the function raster (a temporary layer) that is created to make a profile.  Basically I think your user can simply add one more mouse click to his/her workflow (clip function) and keep moving forward.  I also wanted to point out that in 10.1 there is a GP tool called Stack Profile which might be helpful in automating this workflow and maybe even help in getting them to upgrade.  i.e. analyze multiple lines at once. Best, Eric ... View more

No problem. 🙂  It's actually a very common question. Best, Eric ... View more

Go to ArcMap's Main menu at the top... Customize > Extensions.  Turn on the extension.  It should work now. Best, Eric ... View more

Interesting...  Did you try a smaller cellsize just to test to see if you get more records?  Did you try Steve's suggestion to check and repair geometry?  You could also try converting the feature class into another feature class before attempting to convert to raster.  The issue isn't with the zonal tool at this point.  It's either some bad data or something with the conversion tool.  However, the conversion to raster has pretty much always worked for me in 10.1.  Do you have sp1 installed?  If not, try installing it and test again. Can you creat a support ticket? Best, Eric ... View more