Latest Contributions by JeffreySwain

Do not forget that you will most likely have to generate statistics to change it from a 'black box' to looking like data is there.  The reason for this is that usually ascii files come in with the entire range of possible values.  When you apply the standard deviation stretch then the raster will display as expected. Also don't forget the Ascii to Raster tool. ... View more

You can vary the height that you extrude the buildings by adding a field in the building footprint file and then selecting the field as the height to extrude to.  If you are looking for more complicated roofs you will have to create the models in Sketchup or another modeling software and then import them in again. ... View more

You have to 'select' it with the Select button, unless you have changed it, the selection should be cyan blue.   Here is the documentation on how to select the polygon feature. ... View more

The image classification tools are looking at ranges of the pixels selected as the training, not necessarily the combination of one pixel next to another.  That would be object oriented classification, where the arrangement and the pixel values are considered. What is probably happening with your data is that based on the training samples created the shadows might fall into another class like rooftops or roads creating the confusion.  Since the algorithm is only looking at the pixel values, such an issue can and does occur.  The only way to improve the classification is to improve the quantity and quality of the training samples or masking out some of the raster in order to analyze again. Using the image classification toolbar and then looking at the histograms created by your training samples can help you understand what the computer is looking at when it classifies the pixels.  I hope this helps explain what is happening, it is an over simplified explanation, but the concept is that pixel values in band combination are what it is looking at.  There are many journals that discuss the difference between pixel based and object oriented, this is one. ... View more

The ortho rectification process requires RPCs in order to orthorectify.  Without the RPCs the ortho rectify process cannot be used.  What you may be describing is georeferencing not ortho rectification which can be done in both software platforms, but without camera information and RPCs the output might be georeferenced, but not orthorectified. ... View more

What could be happening is that the pixels that are appearing as nodata are being rejected by the reject fraction in the classification tool.  Per the help, reject fraction controls the "portion of cells that will remain unclassified due to the lowest possibility of correct assignments."  I would consider whether the training samples you are using would be applicable to those areas and then consider performing the classification again.  If you are applying a signature generated from another set of files, the pixel values could be different. ... View more

So you have a mosaic dataset in a map service, but do not want to cache it.  Is that correct?  Generally most people that have them cascaded are in order to create a map cache. How does the image service do on its own?  Cascading the image service in a map service will not be any faster than the image service.  If the image service is slow then test by publishing one overview directly and one of the source rasters directly. If those are fast then it is the way that you have configured the mosaic dataset.  If both the original raster and overview is just as slow then it is the network speed. At this point I would determine if you move the source rasters to the Server and they perform better or work with your network professionals to determine why the network is causing the problem.  I would recommend creating more overviews on the original mosaic dataset, which will take advantage reducing the threshold at which the source rasters are being utilized, which may speed up the performance as the overviews are quicker to display.   Depending on the original raster format, some rasters are just slower performing.  Generally the more highly compressed then the worse the performance.  There was information generated by testing the original Image Server, but in tests here the same holds true in testing here.  JP2s and Sids perform slower than the fastest performer, tiled tifs. ... View more

There is also this tool, the Feature to 3d by Attribute, also bear in mind you can pull any of the geoprocessing tools in ArcToolbox, back into your Toolbar.  This option was the other half of the 'Convert to 3d' button in the 3d Analyst toolbar. ... View more

When you add the rasters to the raster catalog are you choosing to create a managed raster catalog or unmanaged.  Unmanaged should continue to work, since you are not importing the rasters.  If you are choosing managed, then perhaps you are exceeding the limit of the geodatabase if you are choosing a personal or the total file size for a file geodatabase.  Bear in mind, if you are choosing to import .sids or other highly compressed files, then they will be uncompressed and create files that are much larger than the original based on the compression.  Perhaps you are either running out of room on the disk or within the personal geodatabase.  That is the most likely reason, otherwise, perhaps one of the rasters is not defined and the chosen projection will not accommodate all of the rasters. ... View more

When you say 'merge' did you use the Merge tool or how did you combine the two?  Also I am not sure what you mean, 'partially interpolated' because you are using a resampling technique, not necessarily an interpolation.  My recommendation would be to combine the two rasters with the CON statement and then choose the finer pixels over the resampled Aster values.  This technique will avoid resampling and maintain the original values of the finer resolution data.  You must be sure that your pixels line up with the Snap Raster environment setting.  That way you can have the best of both rasters.  Be advised if the values at the edge are way off, you will still see a 'stair step action' unless you choose to blend/merge.  If you are getting artifacts, it may be due to the resampling/merging that is occurring when the pixels do not line up and the values are very different.  I am including a blog post on adding two rasters together that discusses this technique. ... View more

That explains the issue then.  The only supported .grd files at 10 are the .grd from Golden Software per the Supported Raster Formats document.  Golden Software Grid (.grd) There are 3 types of Golden Software Grids that are supported: Golden Software ASCII GRID (GSAG), Golden Software Binary Grid (GSBG), and Golden Software Surfer 7 Binary Grid (GS7BG). Single file�??extension *.grd Read-only (Write�??developer only for GSAG and GSBG) If you are using 10.1, then MapInfo .grd files are now supported as well, but likely the GeoSoft .grds are being read incorrectly as they are not supported. ... View more

Import 3d Files is the tool that you will need to create either a shapefile multipatch or feature class multipatch in a geodatabase. ... View more

Ok then it is simple, choose the option in ArcScene to display this raster using the elevation levels provided by the TIN.  Then you do not need to have the TIN in ArcScene altogether.  You can path to it in the menu.  This should create the look of the raster draped on top in 3d. ... View more