Latest Contributions by JeffreySwain

I would consider the coordinate system you are using. If it is not projected and in the same units, you will have values like that.  So if it is a geographic coordinate system, then you would be doing a conversion of meters in elevation change/decimal degree. That is where I would start. ... View more

The error message received is a memory error. Is there any other reason that the system would run out of memory?  Have you tried the tools outside the script to see if you can determine where it may be hanging up?  It seems you moved forward, but if you still want to use the script created some further testing is required. ... View more

You would be probably better off simply adding the shots you want to achieve and then let the animation process 'move along the path.'  So if you would like the animation to 'look around' simply choose the views you want it to take.  The animation process will smooth out the turning and the path based on the order of the shots you select. ... View more

As a shot in the dark, I would consider removing the '-' and '+' from the names of your output and input files.  The tools at 9.3 did not like special characters. Since your output looks to be an Esri GRID, then that would be where I would start.  If the script used to work, then the code is probably fine, the two flex points would be your inputs including the names and the version of python you may have installed on that machine.  If you have another application that may have updated past what 9.3 is expecting, that may also cause issues. ... View more

I would only use the 'Hard Clip', if you have made your constraining polygon 3D.  If you have a normal boundary, then use the soft clip so that the TIN will constrain, but the values on the edge of the TIN will not take that of the constraining boundary.  Take a look at this help documentation for more information. I would also urge you to consider terrains to model your area. ... View more

Based on the size of the terrain, I would consider limiting the area of analysis via a boundary then processing the lidar.  Perhaps using a polygon as a soft clip will allow you to generate for the desired area.  Simply running the Surface Contour tool on the entire terrain dataset may cause problems. ... View more

I am pretty confident since you mentioned the word 'country' that the raster was created piecemeal rather than in one step.  Since you can determine the cell size of the img, I would recommend creating an LAS Dataset of only a few of the las files or limiting the las dataset with boundary.  Create the pieces of the raster and then you can consider creating the raster with the mosaic tool or perhaps within a mosaic dataset for speed.  Just out of curiosity how large is the raster you have in size and the cell size? Per the help, including a study area boundary as a clip constraint in the definition of the input LAS dataset is highly recommended. One reason is to prevent interpolation from occurring outside the real data extent of the survey. Secondly, there can be a severe performance penalty when using natural neighbor options if the data area is not properly defined. ... View more

Also just to double tap this, when running any Geoprocessing tool, be sure to check the Help documentation to see which environment settings are being recognized by the tool.  Not all tools recognize the same settings, so while you may be setting the snap raster for every tool in Spatial Analyst, not every tool will respect it.  You can set every environment setting, but only a few are recognized bycertain geoprocessing tools. ... View more

If you have already purchased a license for bing maps then ignore, but otherwise you will have to. Here is a blog that describes the changes. ... View more

From the look of the original screenshot that issue had to do with not generating overviews and limiting the number of visible rasters to 20 or so.  To see all the rasters, you have to increase the number of rasters visible or generate overviews. Maximum Number Of Rasters Per Mosaic�??Prevents the server from mosaicking an unreasonably large number of rasters if, for example, the client zooms in to an overview scale in a nonoptimized image service dataset that has no overview tiles generated. The default is 20. Help documentation ... View more

Is the lidar imported into a multipoint feature class?  If so then the straight conversion would have to include converting the multipoint features into individual points. Once the individual points are created then perhaps the values could be read like this.  I am wondering if you have used the RGB symbology of the LAS files within ArcMap through a LAS Dataset and then try to export that into a raster. You can also export the LAS Dataset with the LAS Dataset to Raster tool and select RGB.  This might actually be more time efficient, since depending on the LAS file, you may be creating millions of points from the multipoint feature class.  I have never tried this workflow, but perhaps this may get you closer to your desired output. ... View more

You might get a better result by making the Raster Resolution of the raster you are draping match the original raster resolution.  By default, the raster resolution will be more coarse than the original to save processing time.  However, the best option may be to use the bare earth DEM and then add 3d Symbology or multipatches of the trees to get the best effect. ... View more

This blog can help expose the fields with the BLOB characterization within them. I am more familiar with the Intensity field, but I suppose within your data that information can also be exposed.  Have you tried looking at the fields in ArcCatalog? ... View more

Have you tried the Raster to Point tool?  That may work better than that workflow from 9.0. ... View more

I would recommend trying to look at the added rasters to be sure none of them are corrupt or somehow different(ie undefined projection).  If they are fine, then try to create a mosaic dataset in a file geodatabase and add the data that you just added.  If that succeeds then I would call into create a Support incident as something is not correct.  Usually that error would appear when there is an issue with the extent of the added rasters.  In this case, it may be the extent is not correct, corrupt or the projection it is in will not fit in the coordinate system of the existing mosaic dataset. You can also try to add the new imagery a little at a time and see if you can determine which raster may be causing the issue. ... View more