Latest Contributions by JeffreySwain

The usual step to maintain data would be to multiple the float values by a constant like 1,000 or more depending on how many decimals you want to maintain. Then once you are done processing then you can divide to get back down to the float values. From your description you may not need to see the values. I am curious about your workflow for data. Is your original data single band integer data?  If so how are you performing the NDVI on less than four band imagery?  Which NDVI calculation are you recreating, like this one to get values between  -1.0 and 1.0?  If that is the case, short of trying to convert the data to a vector format and then spatially joining them, I am not sure if what you are looking to achieve is possible for each area. If you had polygons originally and then wanted to add the data based on the NDVI raster you create then you could do that with the Zonal Statistics or if you had point you could harvest the NDVI values for the individual points via the Add Surface information or Extract Values to Point. ... View more

For Zonal Statistics the omitting of the zones can be a problem depending on the size of the zone and the cell size.  If you do not have a raster cell that will fit in the rasterized version of the polygon. So based on your testing, I would consider making the raster a finer resolution prior to processing and see if this solves the issue.  There is a reference to this in the help documentation. If the zone input is a feature dataset with relatively small features, keep in mind that the resolution of the information needs to be appropriate relative to the resolution of the value raster. If the areas of single features are similar to or smaller than the area of single cells in the value raster, in the feature-to-raster conversion some of these zones may not be represented. To demonstrate this, try converting the feature dataset to a raster with the appropriate feature-to-raster conversion tool and specify the resolution to be that of the Value raster. The result from this conversion will give an indication about what the default output of the zonal operation will be. If you have fewer results in the output than you may have expected, you need to determine an appropriate raster resolution that will represent the detail of your feature input, and use this resolution as the Cell Size of the Raster Analysis Settings of the Environment. ... View more

James, What you described, creating the mosaic dataset based service and then you can cache that image service without having to add to a map document and then caching as a map service. In terms of what Larry mentioned, the SDE mosaic dataset works, I but I agree in terms of logistics and then cleaning up the intermediate processes. Since the overviews are not visible via ArcCatalog for SDE mosaic datasets, if you want to remove them or see them directly, you will need to access them directly via the database management software.  Also changing the paths of the overviews do not work as expected with the GUI process as the path is inherent in the geoprocessing tools as the path will not be visible and have to be adjusted other ways.  There are reasons for using SDE mosaic datasets, but I would recommend trying a smaller section rather than simply go forward to see if it matches your needs. ... View more

The issue does seem to be the format.  For datasets like this, I recommend exporting the color map to an external file (.clr) and then deleting the four columns (Red, Green, Blue, Opacity).  This allows the raster to be treated as relatively normal. There is an existing bug report for the behavior, but it is not published. Please contact Support to be added to the bug report. The rejection of the bug states that the data must be 'cleaned' and those columns removed to be used in analysis. Once you have the color map exported, you can reapply it like normal colormap based rasters. ... View more

The reclassify that Robert suggested is the correct to develop a sort of 'cost' raster.  This could then be incorporated into the Least Cost Path or Weighted Overlay tool depending on how many criteria you had. ... View more

After you create the LAS dataset, you should add the toolbar and then be sure to zoom until the points are visible.  There will be a % visible on top of the LAS dataset in the Table of Contents. The toolbar tools should light up. It is not possible to specifically answer the question on the scale without specific data, but you should be able to zoom in and see the point cloud.  If you have exceeded the max number of points you can adjust that figure, but it may be necessary to export the las dataset as a raster or put in a terrain to see certain las datasets. ... View more

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