Latest Contributions by JeffreySwain

The tool will work within the application as described above. In terms of creating inputs via model builder without the application, I am not sure that it is even possible to complete this without the application.  You may try to use the Interpolate Polygon to Multipatch tool, but it will require a TIN to generate the height of the building.  You may also consider the Feature to 3D by Attribute tool to make the polygon for the building 3D at the base of the building prior to using in this tool. ... View more

The Layer to 3d Feature applies 3D effects added to the layer in ArcScene/ArcGlobe to the feature.  Per the help, the tool exports feature layers that have 3D properties defined. So by altering the settings on the properties of the feature in those applications you can create a new feature. Without adding it to the display or adding it to layer there isn't a '3D layer' that can be used to create new data.  So when you utilize extrusion or base heights your custom look to the data can be turned into a multipatch. I am not sure if there is a way to work around this as the tool is designed to take information that can only be added in the display to the feature to create a new feature.  Without the 3D properties altered, the output would be a 3D version of the same feature at 0 elevation. ... View more

The cell size you are looking at Kania is in decimal degrees since the projection is WGS 1984.  The Wikipedia page for decimal degrees has a chart that gives you an idea of the conversion, but also remember that the conversion from decimal degrees to meters is different depending on what latitude you are. For the kind of analysis you are looking to do, I would consider converting the WGS 1984 into a projected coordinate system with meters and then resample to more logical units. ... View more

I would also look into the CON tool to simply select all but the value you are looking for.  Since you said elevation, this may be more appropriate. ... View more

I would check to see if the point totals are close between the LAS Dataset and the multipoints. Generally speaking I would not perform the action you are as the LAS data is incredibly large. You may also be having an issue with displaying that number of points.  Most of the time the redraw will pause if the mouse is moved. What are you looking to achieve by converting all of the LAS files to multipoints?  Convert it to a Terrain? ... View more

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