Latest Contributions by EricRice

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

Mark, Not that the idea is bad, especially if someone manually types in the extent and wants to "view" it... but if someone is choosing a layer, then we already provide tools/visualization of extent depending on if it is a feature or a raster.  For raster, just display NoData in addition to real values - that is the extent.  For features, there is a tool called Minimum Bounding Geometry.  Choose the Envelope option to get a polygon output that is the extent.  Best, Eric ... View more

If an area unit is selected, the calculated density for the cell is  multiplied by the appropriate factor before it is written to the output  raster. To see the effect of going to sq miles, set the area unit to SQUARE_MAP_UNITS (your original unit feet). Best, Eric ... View more

Did you check out How Kernel Density works for point features? Best, Eric ... View more

Hi Peter, I recommend some reading at this point.  It's long, but worth it.  For the Tiff comment it is simply faster to access than a FGDBR.  Here is an excerpt from Imagery: Data Management and patterns and recommendations. "Optimized image formats�??Some imagery can be slower to read than others  due to their storage format or compression, and it is recommended that  you convert these into more optimal formats. For example, an ASCII DEM  image format is slow to read; therefore, it is recommended that you  convert it to a format such as TIFF. Also, if the image is very large  and not tiled it is recommended that you convert this to a tiled TIFF  format to optimize disk access." Since you have to convert from ECW you might as well go to an optimized image format like Tiff.  Also, while in ArcMap go to Customize > Options > Raster tab, and make sure Created Tiled Tiff is checked on. It should be on since that is the default.  You can even compress the Tiff file, so you might consider Tiled Tiff with jpeg compression.  If you know Peter Becker and he is familiar with your data he can probably guide you on this quite well. For the format questions please see the following. Esri GRID format How raster data is stored and managed (this explains the FGDB parts including PGDB and Enterprise geodatabases) If you really want to know how a FGDBR is actually stored in the FGDB you can read all about it in the SDE section since they follow the same idea/storage. Raster datasets and raster catalogs in a geodatabase in SQL Server Best, Eric ... View more

Hi Peter, You should convert the data to Tiff. Peter Becker would agree with that and I would be surprised if that wasn't already advised.  Tiff should be faster than File Geodatabase rasters.  Please note that FGDB rasters and Esri GRID are two completely seperate formats.  It's impossible to store an Esri GRID in a File Geodatabase. Best, Eric ... View more

You can't just click 'add data' and browse to a .las file and display it.  It's not supported like that.  See Using lidar in ArcGIS as well as What is a LAS Dataset for good starting points. Best, Eric ... View more

On the main menu go to Geoprocessing > Geoprocessing options.  Uncheck "Enable" background processing.  🙂 I read a bit more... it should still work on PGDB.  The 2gb limit is on the .mdb file, and PGDB doesn't actually store the raster data.  It writes .img, jpg, jp2 files.  See  How raster data is stored and managed.  I would still personally use FGDB raster though.  Eric ... View more

Ryan, The display units are not actually connected to the coordinate system of the dataframe.  It's probably returning X,Y in A Hammer_Aitoff projection space.  To get X,Y in Decimal Degrees your coordinate system on the dataframe needs to be in a GCS.  To confirm, go to the General tab of the dataframe properties.  I bet your Map units are Meters, and your Display units are Decimal Degrees. Best, Eric ... View more

Jay, Try running it in the foreground.  That error is specific to background geoprocessing. I would also recommend NOT using a personal geodatabase due to its size limitations.  See Types of geodatabases for additional details. Best, Eric ... View more