Latest Contributions by GabrielUpchurch1

If Dan's suggestion does not work, you might try a repair of the ArcGIS installation.  Your colleague will need to have access to the installation files to accomplish this.  Here is the procedure: 1. Go to the Add/Remove Programs dialog of the Control Panel (May be called "Uninstall or change a program"). 2. Right-click on the ArcGIS for Desktop program in the list and select "Uninstall/Change." 3. When the Desktop Setup dialog opens, select the option to "Repair." 4. Follow the remaining prompts to execute the repair. ... View more

Is the field the proper data type? ... View more

To answer your last question first, the 64-bit Background Geoprocessing applies only to geoprocessing tools being executed in the background.  It can be used whether the tools are executed directly or in ModelBuilder or python.  ArcGIS for Desktop is a 32-bit application but when you install the patch and execute the tools in the background, they run in 64-bit. When you run the model, is the progress dialog opening?  If so, then the model is still running in the foreground.  How are you executing the model?  If you are executing it from the ModelBuilder dialog, I think it always runs in the foreground so you need to execute it as you would any geoprocessing tool.  If the model is running in the foreground, then do the following: 1. Right-click on the model and open the "Properties" dialog. 2. Under the "General" tab, uncheck the setting to "Always run in the foreground" and apply the change. 3. Now execute the model by double-clicking on it (not by opening the ModelBuilder window). If the model is already running in the background and you are still getting "out of memory" errors, then you have two main choices: 1. Process the data in smaller subsets (this should be straightforward since you already have the model); or 2. Try to get Vince's suggested approach to work. ... View more

Glad it went well.  It may be more than you want to get into but you might also consider raster functions which are available in all 10.x versions:  What are the functions used by a raster or mosaic dataset?—Help | ArcGIS for Desktop The Shaded Relief function may be of interest: Shaded Relief function—Help | ArcGIS for Desktop Or if you want to go more advanced, check out this blog for a really cool approach using a function chain:   Learn a New Method for Displaying Hillshades and Elevation Tints | ArcWatch Note: The above help documents are from the 10.3 help because I cannot get the 10.1/10.2 URLs to work for some reason.  Just search the document title in 10.1/10.2 to find the relevant resource for your version. ... View more

The Buffer 3D tool also works for polylines.  Assuming the pipeline does not run truly horizontal, you would want to incorporate Z values prior to doing the buffering.  You can use a DEM with the Interpolate Shape tool to add Z values to your polyline or use Feature To 3D By Attribute if you have elevation/depth values for pipe segments stored as a attribute. Help Documents: Interpolate Shape—Help | ArcGIS for Desktop Feature To 3D By Attribute—Help | ArcGIS for Desktop ... View more

Since you are already using ModelBuilder, I would just insert a "Feature Selection" iterator prior to the Make Feature Layer step and use the 9 cell grid feature class as the input.  The output from the iterator is then used as input to the Make Feature Layer tool. Some documentation on iterators:  A quick tour of using iterators—Help | ArcGIS for Desktop You will also need to use "inline variable substitution" to properly name the outputs from each iteration.  Here is some documentation:  A quick tour of using inline variable substitution—Help | ArcGIS for Desktop ... View more

To build on what Darren said, it would be easiest if you choose a projected coordinate system with the same linear units as the units used for elevation in the DEM.  If this is not an option, here is what the tool help states about using the "Z factor" parameter: "Number of ground x,y units in one surface z unit. The z-factor adjusts the units of measure for the z units when they are different from the x,y units of the input surface. The z-values of the input surface are multiplied by the z-factor when calculating the final output surface. If the x,y units and z units are in the same units of measure, the z-factor is 1. This is the default. If the x,y units and z units are in different units of measure, the z-factor must be set to the appropriate factor, or the results will be incorrect. For example, if your z units are feet and your x,y units are meters, you would use a z-factor of 0.3048 to convert your z units from feet to meters (1 foot = 0.3048 meter)." ... View more

To check to see if the 64-bit patch is installed, go to the Help dropdown menu in ArcMap (or ArcCatalog) and select "About ArcMap."  If it is installed, you should see something listed similar to "Background Geoprocessing (64-bit)...". ... View more

It appears to be using Nearest Neighbor resampling. I did some testing with data I specifically fabricated for this purpose and that is what my results indicate.  It is grabbing the cell value from the input rasters that is closest to the cell center of the output raster. ... View more

You might also consider a map package.  This will essentially create a compressed file of the map document and all the data.  You send the map package file (.mpk) to the client and they can simply double-click the file to unpack it.  The map document opens exactly the way you have set it up. Here is a help resource on map packages:  Creating a map package—Help | ArcGIS for Desktop ... View more

Hi Manuel, To verify, do you have the 64-bit background geoprocessing patch installed?  If you don't, you are still running in 32-bit and will have limited access to RAM (4 GB max I think). Theoretically, you should be able to use all 23 GB RAM when processing in 64-bit (at least what isn't being used by other processes).  Of course, theory and reality are two different things and even with access to huge amounts of RAM, it doesn't necessarily mean that a process will succeed or be any faster.  Other factors related to the processor, software, etc. will contribute to performance and the ability of a process to be completed successfully.  I am being intentionally vague here because even after assisting many users with geoprocessing performance issues and questions, I still don't fully understand everything that occurs behind the scenes when a process is executed. If you can run the process on a sample of the data but not on the entire dataset, I usually suggest subsetting the dataset, running the process on each subset, and then merging the results back together.  In your case, you could subset the grid into manageable pieces and probably leave the lines alone.  Many users will use ModelBuilder or Python to semi-automate the procedure.  It isn't ideal but as long is it won't somehow influence the final results, you know it will get the job done and is a lot safer than waiting 4 days.  I once experienced a power outage on the third day of a geoprocessing operation and didn't have any type of battery backup to keep my machine alive. ... View more

One thing I failed to explicitly mention in my last post, only in a previous post, is that if you add the new rasters with the "Update Cell Size Ranges" option disabled, you will need to go into the Footprint attribute table and manually add MinPS and MaxPS values for the new rasters.  It's really up to you whether you disable or enable this particular setting when adding rasters.  I am just cautious about allowing the software to recalculate the MinPS and MaxPS values for all the primary rasters and overviews after I have configured the mosaic dataset the way I need it to be. ... View more