Latest Contributions by JeffreySwain

Primarily I suggest storing the mosaic datasets in SDE, when you are interested in database level security.  Otherwise the file geodatabase is more convenient to handle and the overviews can be easily accessed(they will be in a folder near the file geodatabase by default, within SDE stored in the raster column and not visible via ArcCatalog).  Since you are using Mosaic Datasets, you will not have to 'mosaick' the rasters together prior to adding them to the mosaic dataset and you can keep them in their native format.  Also since you are using 10.1, you can cache the image service directly if you so desire.  Image Service Patterns ... View more

Do you have a colormap in the raster attribute table or with an auxiliary file (.clr)?  I would recommend exporting the colormap if it is internal and then deleting the rows marked, "red", "green", "blue" and "opacity."  You can then also remove the entries for the other values if you prefer in the exported .clr file. ... View more

Ok so it looks like you have an incident in Support.  That would be my recommendation to look at it. The only caution that I will say is that sometimes due to the memory used in ArcScene, there can be odd display effects until you restart it and release the memory.  Also be advised you will have to insert the multipatch into a file geodatabase to preserve the textures. ... View more

I don't think that there is simply one answer.  Each of the interpolation techniques are valid and have their uses.  If you are just starting out or unsure of the math behind kriging or IDW, then I would stick with the spline. ... View more

You could convert the extruded points to a multipatch and then use the Intersect 3d tool to see where they intersect.  That might be the best technique. If they were true lines, then you could use the Intersect 3d Line to Multipatch. ... View more

All can be found in the tool Create TIN. You can modify it as before and if you would like drag the tools back into the toolbar for convenience.  The old Create TIN merely created the file, the new version allows the breaklines and mass points to be added to it in one easy step. ... View more

The only way that I have seen that tool fail was when you have an existing field for what it is looking to create.  I would consider renaming or removing the field with the same name it is looking to create.  The only other reason that tool fails is when you have one set of data, usually the raster, that has a coordinate system and the point file is unprojected.  I would consider the projection, the field names and if both are correct, then contact Esri Support.  If you are looking for the described functionality, they I recommend looking at the tool Create 3d Feature by Attribute, it should create the desired output without the 'multi-step.'  The Add Surface Information tool is usually used on 2d points and allows them to determine a z. ... View more

If all you are seeing is the outline or the 'red squares' you mentioned then I would encourage you to look at the % of visibility in the table of contents above your LAS dataset. If it says 0% then I would encourage you to zoom in on it until you start seeing data or adjust the settings.  You are correct that the size and the projection are important, but I would pay more attention to the % visibility under the rendering preferences. ... View more

When you installed the software, you might have selected a custom install and then not installed it.  Go to Add/Remove Programs and then 'modify' the ArcGIS Install.  When you look at the options be sure you check to see if it is installed and then add it at that time. Once you have it installed, it should appear in the Customize mode, no matter if you have the license or not. ... View more

The .3ds data would be imported into a file geodatabase as a multipatch with the Import 3d Files tool or added as a model to a multipatch feature class.  I am not sure if you are trying to symbolize another multipatch?  I am not sure how that would work, since most multipatches are textured not 'symbolized' in the classic sense. I would think you would be better off symbolizing the .3ds file in 3d Max or other program and then import it rather than try to import the symbology texture from one multipatch to another. ... View more

You can also use the Add Surface Information tool, which will interpolate the elevation at each point and add the field to your data. ... View more

Once you have the data in a format where the point name, x, y, z is there then you can import the txt file as an Event Layer and then convert to a point file.  With the points(be sure to put in a feature dataset), you can then create your terrain.  Generally the workflow is used with LAS/Lidar data and there is a point file spacing associated with that data.  You should measure several locations between your points and see if you can determine the average point file spacing. Then you can create the Terrain by right clicking in the feature dataset and then following the prompts after selecting a New > Terrain. ... View more

For you new data, can you confirm that the output is 8 bit?  I believe that is more than likely the issue, the promotion to 16 bit. ... View more

I am not sure if you want to proceed with this workflow given what that raster may look like.  Are you looking for the overlap or what would be the purpose of combining them?  I would consider the bit depths of each raster prior to combining them.  It sounds that since the bit depths vary so greatly between the different rasters and the resulting output is adjusting to account for the differing values.  This mosaicked raster is not able to properly display the results.  Or the Nodata overlap of the different rasters do not allow for any value.  So I would consider the bit depth and the presence of NoData before proceeding. Also I would consider what type of output you are looking to achieve. ... View more