Latest Contributions by JeffreySwain

Did you convert the contours to 3d in ArcMap prior to exporting them to CAD/Microstation?  I would use the tool Feature to 3d by Attribute to convert the 2d contours to a 3d line.  Then export to CAD/Microstation. ... View more

You also might consider the LAS Tools and specifically the txt2las tool.  There is also the option to convert to an LAS with ArcMap using Data Interoperability. ... View more

File System rasters, would that be Esri GRIDs?  If so can you indicate if the path has spaces or special characters in them?  Or if you maintain the same location, but change the format of the rasters to a .tif or .img with the Copy Raster tool, will the process work. My assumption is that the tool fails due to the path of your data. ... View more

You have added a single band raster with a different spatial extent to another raster with a separate spatial extent and not gotten partial or incomplete output?  You can add the bands with the same spatial extent like I described with the Combine bands tool. That is a normal workflow.  Simply using a mosaic dataset to store data in a regionally similar area regardless of the number of bands is not necessarily a good idea.  When I use Erdas Imagine to add a raster with one band to one with 3 bands, I am confronted with an error message and the process halts. I am not sure how you were able to successfully complete the task.  [ATTACH=CONFIG]19450[/ATTACH] However, I would still recommend using the mosaic datasets, but be mindful of the number of bands for good output. ... View more

I would not consider adding a 1 band raster to a multiband mosaic 'basic' raster functionality and not being possible. If you try the same process with Imagine or Envi you will likewise get bad output.  The mosaic dataset is built to handle varying spatial resolutions, but you set the bit depth and band combination when you create it.  The rasters you add have to have those minimum requirements. If you created a 1 band mosaic and then added 3 band data, then it will succeed, but you will probably not like the results. You could use 4 band rasters in a 3 band mosaic dataset as well, but will lose access to the 4th band.  The only workaround would be to create one mosaic with all your single band data and then one with your 3 band data in the same geodatabase if you desire, but not the same mosaic dataset.  If you are trying to create a way to store the data then having the two mosaic datasets in a geodatabase will work. ... View more

There is documentation on how to create a group animation and one of the options is to turn the layers on and off.  Per the help, you can create tracks that successively turn visibility on and off for each layer within the group. ... View more

I would consider upgrading your computer/video card. The unmanaged raster catalog maintains the links, so unless the network path is being altered after you create the mxd, which is highly unlikely.  It appears that during the load of the mxd, your computer makes the decision of what to display each time due to available memory.  Have you run the tool here to see if your system meets the minimum requirements? ... View more

It is not an Esri Tool.  It was an ArcScript and the last published one looks like 9.3. I would recommend using the Interpolate Shape tool within 3d Analyst and then use the profile graph toolbar button. You can then export the values to a table that way. ... View more

If you add a single band raster to a multiband raster, then you will get bad results as you have seen.  Perhaps you could use the Composite Bands tool and then repeat the 1st band two more times to generate a '3 band' raster, but I think you would have lost what you are looking for in that scenario.  So based on your description, you have a single band classified raster and want to maintain that classification?  Is that your desire?  The mosaic dataset will not necessarily do that.  The attribute table created will have information about the mosaic dataset, but not your custom attribute table.  I would consider other alternatives to transfer the information, because you see your current result will not work. Perhaps you could use a map service and attempt to overlay the two. ... View more

The mosaic dataset and unmanaged raster catalog are similar in structure (both reside in geodatabase and maintain links to source data) the only difference would be the presence of the overviews, which speed up the display of your new mosaic.  Best of luck with the raster catalog, be advised that you may have to alter the display properties to get all of your rasters to display. ... View more

The workflow that I described will only be as good as your input data.  From what you have there, you should probably create a model in City Engine or other modeling tool if you need that type of precision.  From there you can then convert the building footprint polygons to points and then use your model to replace the point. ... View more

I would consider using a mosaic dataset and then setting the drawing order with the mosaic by attribute setting or perhaps an unmanaged raster catalog.  With that number of rasters, you are asking for problems on certain systems due to memory, which you have appeared to demonstrate by showing it is the number of rasters, not the specific rasters that are an issue. ... View more

I would consider altering your file structure and not using so many '.'s.  I am not sure if that is what is generating the error, but my first recommendation would b to re write the names of your files.  Lab3_3 and the name of the geodatabase to Lab3_3.  Depending on the system, I have seen naming conventions like this causing problems. ... View more

It looks to be a discrepancy between the ground elevation used for the points and the one used in ArcGlobe.  For the best results, I would recommend if you are using custom zs for the points to also use the custom DEM in ArcGlobe to display. ... View more