Latest Contributions by EricRice

Kerri, The fact that you have an .ige and .rde file means your raster is over 2gb in size.  These files contain the overflow that exceeds the first 2gb's stored in the .img file.  You must move these files with the .img file or the data will no longer work.  I recommend moving raster data with ArcCatalog since the system knows which files to move and all you have to worry about it is picking which raster 'datasets' you want to move, rather than determining the right files in Windows Explorer to  move.  I'm sure you've noticed by now that raster data can have a plethora of associated files when viewed through Windows Explorer. Regards, Eric ... View more

Lisa, Overviews are generally faster than pyramids so you don't need both of them for optimal speed.  If your data comes to you with pyramids, great, we will use them (and write fewer overviews).  If you don't have them, we will simply build more overview levels.  There are specific use cases for building pyramids on the source rasters though.  I recommend reading Mosaic dataset overviews in our product documentation for more insight. Best Regards, Eric ... View more

Hi Marie, In the attached screenshot I placed the same 2d point layer into the TOC twice, once as draped and once as 3d vectors. Everything appears to be working normal for me.  I am using 10.0 sp2. What kind of data are you working with? Are you on SP2? What happens if you start a blank globe document and add the data? Is this the same Marie I met in DC a month or so ago?  I can just call you if it is... Cheers, Eric ... View more

Andrew, Those tools do not honor the Analysis Mask environment setting.  Each tool in ArcToolbox has corresponding documentation that will tell you which environments they will honor.  For example, the Polyline to Raster tool honors the following settings:  Compression, Current Workspace, Output Coordinate System, Extent, Pyramid, Scratch Workspace, Cell Size, Snap Raster.  You can Clip the resulting raster to your mask after the conversion. Regards, Eric ... View more

Greetings, Can you send a screenshot of what the problem is? Thanks, Eric ... View more

Dave, Are you outputting to Esri GRID format?  GRID's are always 32 bit.  We read ascii files as raster datasets these days, so the ASCII to Raster tool isn't really necessary.  You should be able to just add the ascii file to ArcMap and maybe have to calculate stats on it. These links might be useful. Technical specifications for raster dataset formats Supported raster dataset file formats Eric ... View more

Justin, There are a couple of approaches you can consider. Line of Sight analysis (LOS), or Intersect 3D Line with Multipatch tool.  I think LOS is easier but doesn't work well with vertical lines.  If you connect your points and the resulting line is vertical, consider option 2.  Both workflows are outlined below. LOS 1. Run Construct Sight Lines tool to create lines from your points.  You'll probably need a join field to ensure the right points get connected. 2. Run Line of Sight tool with raster surface and newly created lines.  Be sure to fill in the parameter for Output Obstruction Point Feature Class as this will be where the line actually hits the surface. 3. Take the obstruction points and run Add Z Information tool using the elevation raster as the surface.  You'll get an attribute of Z containing the surface height at that location. Intersect 3D Line with Multipatch 1. Construct your sight lines as per above. 2. Convert your raster to a TIN. 3. Create a polygon that is big enough to contain all your points.  Hopefully this polygon won't have to cover the full extent of the raster. 4. Run Interpolate Polygon to Multipatch.  This tool requires a TIN surface (Hence step 2). 5. Intersect your sight lines with the multipatch using Intersect 3D Line with Multipatch tool. 6. With resulting points, run Add Z Information tool. In the screenshots below, note that what appears to be a raster or TIN surface is actually the multipatch feature class I created.  Because I used a small example I was able to make my entire surface a multipatch.  I recommend minimizing your polygon to just the extent of the points if you have a large raster in terms of its extent. Regards, Eric ... View more

Kyle, If you have rectangular cells in your raster data, please be aware that any analysis done in ArcGIS will resample the data to be square. All the algorithms in Spatial Analyst are designed for square pixels. Using the very simplistic example in the pdf, I created a raster dataset that is 3 x 3 with the same values as your graphic described.  Using somewhat of a brute force technique I was able to solve this in ArcGIS.  It may not be elegant, but here is what I did.  This example is solving for Eyy (cell ID 5) 1. To obtain the value for cell ID 6, I shifted the raster to the left by 1 cell.  Now a value of 9 is on top of source raster value 7. 2. To obtain the value for cell ID 4, I shifted the raster to the right by 1 cell. Now a value of 8 is on top of source raster value 7. 3. Using the two newly created rasters, I used your formula in the raster calculator.  i.e. ("rightvalue" - "leftvalue") / 20.0 to obtain a new raster that has a value of 0.05 that now overlays the original source raster where the cell was equal to 7.  See screenshot where I identified all raster values located at cell ID 5. Using this logic of shifting data you can shift up and shift down to get the values to solve Exx at any cell.  The Shift tool is located in Data Management Tools > Projections and Transformations > Raster > Shift. A more elegant solution would be to run the function RasterToNumPyArray and use neighborhood notation to solve. Regards, Eric ... View more

Greetings, What kind of table are you outputting? -Eric ... View more

Larry, The hillshade effect shouldn't do anything if your surface appears too flat.  You may need to set an exaggeration (like you mentioned for GE) in ArcGlobe.  Go to View > Globe Properties and set it for the surface.  You may also want to go to Customize > ArcGlobe Options and turn up the Level of Detail for Elevation layers.  We don't show the full LOD to increase performance.  My screenshots below are from the coordinates you gave me.  I have no exaggeration applied, but high detail for elevation.  When I exaggerate to 1.5 I don't like the appearence, but that could be just me. ... View more

Larry, I have just tested a few things you mention and all are working for me.  The default layers in ArcGlobe should demonstrate where to place each dataset so the images are draped onto the DEM.  i.e. DEM in elevation layers, and images in draped layers category.  Are you sure you told the image layer to be used as an image source?  see screenshot drapeimage.jpg I also added an image service (from MD) to Globe into the draped layers section and it drapes essentially automatically.  You should also be able to use an elevation image service from MD to use as the elevation layer for publishing a Globe service.  If you can't get it working please send me more details about how your layers are setup along with screenshots from your side. Thanks, Eric ... View more

Hi Do Kim, I think you just accepted the defaults when adding your data to ArcGlobe, which means your point layer is being rasterized instead of displaying as 3d vectors.  Remove the layer and add it again, but choose, "Display features as 3D vectors".  See screenshot. Regards, Eric ... View more

Philippe, If all you have is observer and target points, you need to create lines between them to perform a line of sight analysis. You can use the Construct Sight Lines tool to generate the line features between target and observer.  Use the resulting lines as input into Line of Sight. Eric ... View more

Claire, You may have noticed by now that the limited set of functionality previously available on the Spatial Analyst toolbar is removed in ArcGIS 10.  The full functionality of Spatial Analyst has always been in ArcToolbox > Spatial Analyst Tools.  The tool you are looking for is called Cost Path located in the Distance toolset. Cost Path can be used to derive the path of least resistance down a digital elevation model (DEM). In this case, use the DEM for the Input cost distance raster and the output from the Flow Direction tool for the Input cost backlink raster. For those having problems using the interactive Steepest Path tool, I would suggest filling your DEM.  I think you may have sinks and that could be why the path created is so short.  Alternatively, use the Cost Path tool to do your analysis. Best Regards, Eric ... View more

Hi David, The zip file doesn't contain all the necessary files that make up a shapefile. In particular, you are missing the shapefiles .dbf file.  Without it, the file is invalid and I can't view the data. Can you resend that, and post some screenshots of the output you recieve as well as the parameters used to create it?  Please elaborate on what you mean by it doesn't display properly. Thanks, Eric ... View more