Latest Contributions by JeffreySwain

I would consider creating training samples of the shadows and try to collect them as a separate feature.  If you are still having issues distinguishing between the two, perhaps clipping those portions out of the raster and then processing them independently to determine the difference and merging the results.  There are other blogs discussing the image classification toolbar or this one about land cover. ... View more

I would create the raster as an .img or .tif and be sure to specify the bit depth.  If you are using ESRI GRIDs then they are always 32 bit float, per the help.  Here is the information on the supported raster formats. ... View more

Mike, The functions that Eric is mentioning are functions after you create a Mosaic Dataset.  They are not in ArcToolbox, but are available under the Function Tab when viewing the properties of Mosaic Datasets in ArcCatalog or the ArcCatalog Window. ... View more

Can you use the classified renderer on the clipped raster dataset in ArcMap?  I would try adding it to ArcMap and then go to Properties > Symbology and try to click on the Classified Renderer.  I have seen situations where even if there are statistics, the reclassify will fail if there is not a histogram. If you are prompted by the symbology properties to generate the histogram, then do so.  Now retry the reclassify.  If that does not solve the issue, then please call in and create a Support incident. ... View more

Per the information on the USGS website, the 'artifact' effect is due to the manner in which they sample the data. Products that are projected or created from the DEM will expose the effect you are seeing.  Per their help, Q. Will the striping, evident in level 1 DEM's, be eliminated in the NED processing? A. The striping is in the original source DEM's that were processed as Level 1 using the GPMII or Manual Profile methods. Any DEMs that are produced by photogrammatic methods are considered to be Level 1. Level 1 Methods are:     Manual Profiling--- Operator used stereoplotters to create orthophotos in the 1970's and 1980's while simultaneously creating digital profile information for DEMs.     This method produced the "stripping" seen in some level 1 DEMs.     GPM2 (Gestalt Photo Mapper Model 2)--- This was an instrument that was semi automated to produce orthophotos and DEMs at the same time from photography.     GPM2 DEMs can have an appearance of a grid pattern when a shaded relief graphic is produced from the DEM. The filtering process used for NED production does not filter out all of these areas. As new DEM's (Level 2 or 3) are produced for these areas, they will replace the Level 1 source. The only way to eliminate the striping has been to follow the technique described here with the fourier transformation.  Using FocalStatistics can also be used in some areas, but the tradeoff is the generalization of the data.  The information described is how to minimize the look of the striping, not a fix per se.  There is also more information on the USGS site recommending the same resampling techniques, which the previous posters reference.  Q. When resampling NED, should I use Cubic Convolution, Bilinear interpolation or Nearest Neighbor? A. Cubic Convolution and Bilinear Interpolation are the preferred methods of resampling digital elevation data, and will result in a smoother appearance. Nearest Neighbor has a tendency to leave artifacts such as stairstepping and periodic striping in the data which may not be apparent when viewing the elevation data but might affect the derivatives, such as shaded relief or slope. To recap, basically it is in your data if you are changing the resampling and it is still apparent.   The transformation is the only way and you have remove from base data. ... View more

Have you performed any generalization to clean up the raster prior to converting it to polygons?  Many of the outputs from the conversion are not what is intended if the raster is too variable, you create a lot of small polygons, which end up being more problematic than the original raster.  Be sure to create a feature class instead of a shapefile to avoid the size limitation of a shapefile.  I would recommend trying a subset of the raster and also trying some of the generalization tools to clean up the edges or perhaps reclass the raster into definitive areas prior to conversion. ... View more

As long as the NoData area is homogenous(same value) then I would consider georeferencing all of the rasters, assembling a mosaic dataset and then use the Build Footprints to clean up the NoData area.  Then you can use the mosaic dataset or export it as one raster as necessary. I would not worry about the borders until you have the rasters in place, provided the Nodata area is as described above.  There is not a quick way that I can think of to simply click a button and ArcMap will figure it out. Once you have the rasters georeferenced will be the biggest hurdle.  Plus the rasters will display faster in the Mosaic Dataset provided you build the overviews. ... View more

Be advised that at 10, with the Python interface, there are different tools to replace the older ones.  I recommend trying to break it down in pieces with the specific geoprocessing tool in ArcToolbox and then copy it to the Python Window to see the syntax.  Once you have the pieces in place, then assembling them in Raster Calculator will be not problem.  Con(IsNull('mosaic'), FocalStatistics('mosaic', NbrRectangle(4,4, CELL), 'MEAN', 'DATA'),"mosaic") Also in the Raster Calculator syntax, I do not think you need the "Filled_DEM = " part. ... View more

After talking up this incident with a colleague, I also wanted to make a few recommendations. 1.Increase the number of unique values that can exist for a raster under the Customize > ArcMap Options > Raster > Raster Dataset > Unique Values 2. Change the output format to an ESRI GRID (instead of a file geodatabase) 3. Be sure each of the rasters have an attribute table to them, by running the Build Raster Attribute Table. ... View more

Just be advised that the cut/fill requires the TINs to be converted to rasters and be mindful of the cell size when exporting.  Otherwise it should create the desired output.  Let me know how it works. ... View more

Perhaps trying a smaller section (smaller extent) would allow the process to complete.  Because the error message indicates you are exceeding the hard coded maximum for unique values you must find a way to limit it.  I would try to clip your 'equal area' rasters down to a smaller size to see if the process completes then.  As per your requesting an Esri Employee, the quickest way to get a response is to create a Support Incident, as always. ... View more

Zoom into 100 % and be sure to have selected the triangulated display and then it should work.  Per Help, The 3D Analyst toolbar tools are not always enabled when a LAS dataset is active. This is because the LAS dataset can be displayed as a point set. Analysis on thinned points is turned off, and the tools will only be enabled when the LAS dataset is displayed as a full resolution triangulated surface. To learn more about how to obtain a full resolution triangulated surface see: LAS dataset scalability. ... View more

If the toe lines describe what it should be then you should create a TIN or interpolated raster surface based on the lines.  You should make the lines 3d with the 3d Analyst toolbar or as described here. Once the lines are 3d, then you should be able to compare the TIN to the new surface with the TIN Difference tool.  You can also visualize the difference when comparing the two TINs and the polygon of the channel with the Extrude Between Tool.   The Cut/Fill tool or TIN Difference tool can both be used, for your analysis I would think the Cut/Fill would be more appropriate. ... View more

The reason that the bug report was 'declined' was that it is no longer reproducible in the latest version. So to answer your question, it is fixed in the new release. ... View more