Latest Contributions by EricRice

A little late on this thread, but thought I'd throw this out there for anyone looking at this in the future.  I personally only use the Calculator function for this type of stuff.  Below will return elevation values for all values above 1400 and return 0's if false. ... View more

Can you post some screen shots?  If you use Clip_Management you don't need to set the extent environment because the extent control is already in the tool interface.  The extent in the tool will override the environment for extent.  In all cases where an environment setting is exposed as a parameter in a tool, the tool parameter takes precedent over environment settings. "How can I make it "finer" so that It only draws polygons where there is actually a relevant pixel?"      - This sentence is throwing me for a loop.  Are you trying to clip raster 1 with specific (relevant) values from raster 2? Eric ... View more

Ditlev, You can most certainly clip a raster using another raster.  Converting to polygon is not the way to go.  The clip tool inside Data Management Tools > Raster > Raster Processing is probably the one I'd suggest since it doesn't require any extensions.  If you have Spatial Analyst then Extract by Mask is a viable alternative. Best, Eric ... View more

Hi Stefanie, It's most likely related to the zone size.  From the help system: If  the zone input is a feature dataset with relatively small features,  keep in mind that the resolution of the information needs to be  appropriate relative to the resolution of the value raster. If the areas  of single features are similar to or smaller than the area of single  cells in the value raster, in the feature-to-raster conversion some of  these zones may not be represented. To  demonstrate this, try converting the feature dataset to a raster with  the appropriate feature-to-raster conversion tool and specify the  resolution to be that of the Value raster. The result from this  conversion will give an indication about what the default output of the  zonal operation will be. If  you have fewer results in the output than you may have expected, you  need to determine an appropriate raster resolution that will represent  the detail of your feature input, and use this resolution as the Cell Size of the Raster Analysis Settings of the Environment. Best, Eric ... View more

Hi Florian, I suspect your raster data is 32 bit floating point.  I get the same message if I put floating point raster data into Raster to Polygon.  The tool only takes integer raster data as input. Best, Eric ... View more

Support for Landsat 8 is now available. ArcGIS 10.2 for (Desktop, Engine, Server) Landsat 8 Patch Best, Eric ... View more

The tifs can be displayed but it is not suitable for data converting by using ESRI geoprocessing tools. Tiff format is the default format for file based rasters in many geoprocessing tools (when workspace is set to folder rather than gdb).  Tiff is certainly a valid input to ALL geoprocessing tools that take raster input. Best, Eric ... View more

Larry, The title of the thread is "Simple Raster Addition" which led me to conclude that the user posting has a stack of suitability layers that need to be "combined" together.  Adding them together - extent and resolution come into play.  I would argue that simply adding suitability stacks together isn't necessarily a great approach.  Often, if any suitability in the stack of pixels is unsuitable, then the entire stack is unsuitable.  There are many approaches one could take though and their approach of adding them together indicates the opposite of what I'm saying.  This user hasn't clarified what they really want for output.  The user should look into the Cell Statistics tool.  Now if they have adjacent suitability rasters, sure load them into a MD and be done with it.  Set your settings for areas of overlap (probably min or max in the 0,1 case).  Or even in the case of a stack of binary suitability layers, you can load them into the MD and use the Local Function - Cell Statistics to work out the same as what the GP tool would give you except on the fly. Best, Eric ... View more

The key information missing is... Is this a stack of raster datasets (same extents/resolution), or a series of adjacent raster datasets that need to be turned into a mosaic of the series? Best, Eric ... View more

Hi Charles, If you have overviews built and it doesn't display at 20000, 25000, 30000, etc... but does display at 19000, 15000 and larger map scales (remember smaller #'s = larger map scale) then the issue is related to the values in the MaxPS field of the footprint layer. For example, I have a mosaic dataset of elevation for the whole lower 48 (10m source).  After optimizing it with overviews I can do a zoom to layer on the image sublayer of the of the MD and it will display.  Zoom to Layer takes me to a map scale of 1:29,524,719.  As I zoom out it continues to display (overviews), but at a certain scale (~1:52,590,000) the image sublayer will turn off.  This is the expected behavior.  The behavior is controlled by the MaxPS field in the footprint table.  To continue my example above, my top overviews have a MaxPS of 13914.93635.  Per the product documentation  (Scale = Cell Size * 96 / 0.0254) we find that Scale = 13914.93635*96 / 0.0254.  The equation results in a scale of 52,591,885.41.  That is precisely when the image sublayer will stop drawing.  My data is in Meters, so it's really straight forward.  The link below has the formulas needed for other units as well as a full explanation of the MinPS/MaxPS fields and their roles. Cell size ranges in a mosaic dataset You need to determine the map scale you want the image to draw at (or stop drawing at) and then calculate the MaxPS value that will make it draw at that scale.  You essentially override the existing MaxPS value with your own cell size to force it to draw at your desired scale. Best, Eric ... View more

Hi Charles, Based on your description it sounds like you need to run Build Overviews.  You are seeing just the wireframe/footprints right? See Mosaic dataset overviews. Blogs: http://blogs.esri.com/esri/arcgis/2010/10/05/mosaic-dataset-wireframe-not-image-huh/ http://blogs.esri.com/esri/arcgis/2011/10/26/overviews-and-pyramids-part-1-of-2-what-are-they-and-why-do-i-need-them/ http://blogs.esri.com/esri/arcgis/2011/11/01/overviews-and-pyramids-part-2-of-2-doesnt-my-mosaic-dataset-use-both/ http://blogs.esri.com/esri/arcgis/2012/11/14/should-i-build-pyramids-or-overviews/ Best, Eric ... View more

I'm not an expert in either, but Cokriging with Geostatistical Analyst (ArcGIS extension) can do this.  You can also probably use Geographically Weighted Regression (GWR) using Spatial Statistics (not an extension -Advanced license though). Best Regards, Eric ... View more

Thanks for the extra feedback, Mark.  I can see how it would be useful. Best, Eric ... View more