Latest Contributions by JeffreySwain

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

I am not sure what a FIT file is, but in ArcScene you can control the quality of the raster as described in this blog.  Remember that ArcScene loads everything into memory, so that larger rasters can cause other display and performance issues if the quality is raised. I recommend testing out different sizes and qualities to see what works best for you. ... View more

I am not sure what to say about your testing. What was the overview factor you chose?  What did the Analyze Mosaic Dataset reveal?  I am also not sure what you did with rebuilding the footprints, most of the time the reason to rebuild the footprints has to do with the presence of NoData in the rasters. The footprints will remove that information from being displayed. If the source rasters are beings referenced too much then it would not be an accurate comparison.  I would pay attention to the spread in the Min/Max PS with the mosaic dataset.  If you have a large range then that may be the issue.  Ideally with the overview only raster this should happen really quickly.  So the Max PS of the source rasters should be much lower than with the pyramids. In testing here, the mosaic dataset has always performed faster when designed correctly. Also with the more data you add, the more the performance difference will be revealed.  The larger the mosaicked raster dataset gets, the more unwieldy it will become. I am including the help documentation on the recommended mosaic dataset building and a discussion of overviews vs pyramids.  Another consideration should also be the time it will take to produce the raster dataset.  The mosaic dataset creation process is much faster than creating the raster dataset.  For further performance once you have the image service created, caching will push the image service to even better performance.  I would further recommend contacting Support to demonstrate the performance issue that you are seeing. ... View more

Remember the speed of the mosaic dataset comes from having optimized source rasters and the use of the overviews.  In terms of your questions, I think that you could try it each way.  For instance, when adding the rasters to the mosaic dataset, you can choose in the options to set the max pyramid level to zero.  Then generate overviews normally.  This will force the mosaic dataset to ignore your pyramids and generate more overviews.  In some circumstances, this is preferable. However, I would still create a similar test mosaic dataset with the pyramids added to see how that performs.  The hardest part of making recommendations like this is that while there are recommendations that work in some situations, each raster dataset might be slightly different.  Finally, I would leave off the option to generate pyramids as you already have them and I would think there is not as much difference with regard to performance between the versions of geodatabase. What will be different is the functionality that is only available at 10.2 will be lost.  Also don't forget to Analyze your mosaic dataset for specific recommendations. ... View more

Esri GRIDs are 32 bit float by default. I am unsure what an ArcGrid is, but if you mean Esri GRID raster or an extensionless raster then it should be float already.  I would be sure to project your data from WGS 1984 if you desire to use the NED files directly. Be sure that you have the elevations in meters and then choose a coordinate system based on meters.  That will make your calculations come out correctly. ... View more

The exported multipatch should exhibit the same qualities as the extruded polygon.  If you are not getting the same effect, then I would consider what has changed.  Are you using a different coordinate system or switching units?  Something has changed and I would look into the creation of the multipatch as their isn't a mechanism in ArcGlobe/ArcScene to modify a multipatch. You could start from the polygon in City Engine and then drag/edit it there. ... View more