Latest Contributions by EricRice

ArcMap doesn't support .las directly for display.  You have to create a LAS Dataset, then load the .las files into it (using references), then add the LAS Dataset (.lasd file) to ArcMap.  Optionally, you can load the .las files into a Mosaic Dataset and add it to ArcMap.  See Using lidar in ArcGIS, What is a LAS Dataset, and Adding lidar data to a mosaic dataset Best, Eric ... View more

The Clip tool can clip a raster to a polygon and doesn't require spatial analyst. Best, Eric ... View more

Yes I also still have the same issue even though I was told it would be solved in SP1. Come on ESRI!! Hi Mark, I had a look at the NIM and I don't see your name connnected to it in any manner. Did you have an incident with Esri Support that was supposed to be linked to this NIM? I'm curious who told you it would be solved in SP1. That wasn't even remotely possible. The NIM was submitted to Dev on 9/26/12, roughly 4 weeks before SP1 shipped to the public. SP1 was basically done before the NIM was submitted. It was being tested, certified, and a whole slew of other processes involved in getting it out the door. We don't just finish writing code, install it, then ship it to you guys without it being tested thoroughly. There can be two months from the time we finish a service pack, till the time you can download it. I'm not on the team responsible for this NIM, but I know they are aware of the problem. In addition, the User Advocacy Group has flagged this NIM as High Priority (only a couple days after it was submitted) and they are requesting a fix at the next available SP (SP2). We know this NIM is impacting certain ATI card users, and that it needs a speedy resolution. We thank you for your patience. Temporarily, you could convert your TIN to a raster and use the raster in ArcScene. I know it doesn't look the same, but typically you would be draping imagery/features on the surface anyway and not actually visualizing the TIN. Technically, you don't need any elevation layer in the scene; you can still set other layers to use the TIN/raster for baseheights. Best Regards, Eric ... View more

COASTLINE 1: Extent: Top: 45.180969 m Bottom: 24.501657 m Right: -66.849304 m Left: -97.570702 m Data Type: Shapefile Feature Class Shapefile: C:\NAHU_Surge_2011\CatResponse\Sandy\Coastline_shapefile\Coastline2ndpass_Full_Mar18_polyline.shp Geometry Type: Line Projected Coordinate System: NAD_1983_UTM_Zone_16N Projection: Transverse_Mercator False_Easting: 500000.00000000 False_Northing: 0.00000000 Central_Meridian: -87.00000000 Scale_Factor: 0.99960000 Latitude_Of_Origin: 0.00000000 Linear Unit: Meter Geographic Coordinate System: GCS_North_American_1983 Datum: D_North_American_1983 Prime Meridian: Greenwich Angular Unit: Degree Kimberly, Coastline 1 is your problem dataset.  The extent is in decimal degrees.  You simply cannot have data in UTM and have an extent like that.  My guess is someone "defined" the coordinate system to be UTM, rather than actually "projecting" the data into UTM.  You will find that if you start a blank map and add one of our basemaps to it, then add Coastline 1 data, the coastline data will not be in the right spot on the planet.  You need to clear the current projection info, then redefine the projection to be something in geographic - probably NAD83 or WGS48.  Then check with our basemaps again to see if it is in the correct place.  Having different extents is common and it is not a requirement that two datasets have the same extent to be displayed together.  Its ok to add one dataset in UTM and another dataset in Geographic.  The key is that they must be defined correctly, and for sure, one of yours is not defined correctly.  If you want to have Coastline 1 be in UTM, you have to define it first to be in what it was collected in, then you can project it into UTM.  Defining the coordinate system is different than actually projecting data. Best Regards, Eric ... View more

Run the reclassify tool on the raster data prior to converting it to polygons to get the right ranges.  You may still need to dissolve the polygons after the fact depending on your needs.  Best, Eric ... View more

Greetings, I would suggest reviewing this short video. Performing Proper Density Analyis: http://resources.arcgis.com/en/communities/analysis/video401.htm Best Regards, Eric ... View more

Greetings, You can mitigate schema differences by using the "No Test" option in the Append tool. However, the model is not set up correctly as-is. You're missing Collect Values - a model only tool. Also, Append or Merge should be in another model since you only want to run it once, after you've 'collected' all the iterations. This means that everything from the iterator through zonal tools and finally collect values needs to be a submodel inserted into the main model containing Append or Merge. See: Integrating a model within a model subsection, "Advanced use of model iterators" I would use Merge rather than Append here. Best, Eric ... View more

Neala, What version are you using?  Post 10.0, you have to run the Lookup tool on the two fields to create two new rasters, then you can add them together.  The Lookup tool creates a new raster based on values in a field. Best, Eric ... View more

I am assuming your imagery and polygon are both pulling heights from the same DEM Just going to add that ONLY THE VERTICES of polygons pull their heights from the layer set to obtain base heights from. The interiors are not surface conforming, which results in the same types of display issues Marie's screenshots show. You can normally resolve the issue by converting the polygon to multipatch using Interpolate Polygon to Multipatch. Specifically, the product documentation says: "Consider converting polygons to multipatches if you experience display problems with three-dimensional rendering of polygons draped on a surface." Best, Eric ... View more

Greetings, There are two reasons why Open Attribute Table is not available for raster datasets. 1. There is no table built.  In this case, run Build Raster Attribute Table. 2. The raster is 32 bit floating point, which does not support raster attribute tables. My guess is you have 32 bit floating point data.  You can check this in the layer properties > Source Tab > Pixel Type and Pixel Depth properties. Best, Eric ... View more