Latest Contributions by JeffreySwain

The information is still valid at 10.2.  Image Server is an extension for server that grants the ability to publish mosaic datasets.  Here is a functionality matrix that may help some more of the details. The gist is still the same.  Mosaic datasets replace ISDEFs and to publish them (even in an mxd as a map service.. this includes you raster catalog) you need the Image Server Extension.  This workflow replaces the older (slower and file storage dependent process) of using SDE databases to store the raster imagery. The mosaic dataset is much more forgiving of raster differences and does not require the separate toolbar that the ISDEF did. So to recap your question.  The Image Server is an extension on ArcGIS Server and it creates an image service.  You can also create an image service with ArcGIS Server, but it must be of a singular raster.  So you can publish your tif, img or Esri GRID, but not a collection of them.  Hope that helps. ... View more

Check out the help document here for more assistance to add the raster files to an mxd. ... View more

The Pyramid level shouldn't be a factor. I was trying to point out if your raster was a gray scale, single band raster with simply the values indicated then it should work, but if you have more than one band in it, there will not be an attribute table.  For an attribute table to be created, you must have a single band raster with integer values.  So that there will be a 'Grid_code' or value field that can be populated with an integer value.  Then the attribute table can have values added based on that.  The original poster indicated that they had a raster with 32 bit values, which would not be possible to add an attribute due to the extremely high number of unique values.  Take a look at the help documentation for more information about raster attribute tables. ... View more

Raster attribute tables cannot be built on floating point rasters to answer the first poster.  In terms of your 8 bit raster, is it single band? Or multiband.  If multiband then it will not take the values.  If you are using single band then what is the format? ... View more

It sounds as if there are NoData pixels being considered as real pixels and your NoData value is indicated as something else.  I would consider trying the Reclassify or something to reclassify the values back to NoData.  Or perhaps a Extract by Attribute process to strip out the erroneous pixel values that are skewing the statistics. ... View more

Upon further review, I was able to re create the issue and found a work around.  What I did was instead of using the Create Raster Dataset to create an empty dataset, I used the Copy Raster tool to create a copy in the file geodatabase.  Once the copy was created, I was able to use the mosaic tool to merge in the remaining 4 band 16 bit imgs.  Hope this helps. ... View more

Can you please indicate more about your input data. I see you mentioned 3 band, but not bit depth or anything else about the input rasters?  Usually 3 band rasters are either 8 bit or 16 bit.  Based on your experience, I am guessing that they are 16 bit, because they are usually usually the more problematic.  Can you indicate if the issue is with 16 bit inputs or 8 bit? Also can you indicate what bit depth you are setting on the input raster?  I tested here with some imgs that I had that were 8 bit and they are fine. ... View more

You could iterate through the feature classes and clip each one and apply the name that way.  I would recommend looking at the information on iterators and in line variables in model builder or consider scripting it in python.  The name of the feature being used could be used in the naming that way. ... View more

It runs fine for me with multiplying each of them.  Can you indicate if you have any other python modules installed or if you have a different version of python that may have been installed? I would also consider putting a file extension such as .tif or .img to your output and see if that allows the process to complete. ... View more

To create the mosaic dataset, you will need the Standard or better license from an ArcMap perspective, but in terms of Server, to publish the mosaic dataset you have to have the image server extension.  This document describes some of the licensing and publishing options for image services. ... View more

If the image server cache and the map server cache and indicating that those rasters are missing, have you checked to see if they have been moved?  I would recommend logging into the server as the account being used to publish the image service and then attempt to access those rasters from that machine through the designated path. If they exist and are not accessible or if they do not exist you also have your answer.  Are you creating a mosaic dataset using the Landsat raster type? ... View more

Any time you publish a mosaic dataset, you need the image server extension. To publish a basemap otherwise, you will need to mosaick the entire mosaic dataset together and fuse it into one file.   This is the old way of publishing image services - merge in SDE and publish from SDE with server.  The advantage of the mosaic dataset and image server is that you do not have to spend the processing time and file space to create the image service.  Without the image server extension, you are forced to utilize a large chunk of file space on your database to merge all the tiles and then can publish.  Please refer to this document to explain some of the differences with regard to capabilities and licenses. ... View more

Elevation from features will remain greyed out as it applies to features.  The default setting for rasters is 'No elevation values from surface' so that should already be selected.  To assign an elevation, put that value at the bottom under 'Layer offset.'  Once this is applied the raster should maintain the constant elevation. ... View more

The process is still the same, follow the blog and adjust the look of the rasters in ArcScene.  The procedure described in the blog are raster format independent. ... View more

No is the short answer.  By making the raster catalog managed, you are importing the ECW into the geodatabase. This will expand the ECW to its full size before the ECW compression. You can try cranking the compression on the raster catalog down, but you will most likely not like the result visually to maintain the file size savings. If you want another ECW based on the 6000 rasters, then I suggest investing in ER Mapper and then merge the ECWs there and export as another ECW. Mosaic datasets would be a much better option for this workflow, but as your client is probably using a non Esri product to utilize the ECWs this will not work. ... View more