Latest Contributions by JeffreySwain

‎10-30-2012

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.

‎10-30-2012

Unless you are creating an unmanaged raster catalog, it will probably take that long. Another aspect to consider is to look at the uncompressed size, which may be more than the size you see in Windows Explorer. So processing time of days to create a raster of `50 Gigs would be correct and may be more depending on network performance. What you are experiencing is the reason why the mosaic datasets were created, the finer the resolution, the more immense the dataset, the more the processing time with legacy processes. Since the mosaic dataset doesn't import the rasters and only generates overviews, the import time is shorter. The other caveat is to consider the performance of the newly created mosaic compared to a mosaic dataset. <stepping off soap box>

‎10-30-2012

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.

‎10-30-2012

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.

‎10-30-2012

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.

‎10-29-2012

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.

‎10-29-2012

Have you taken a look at the document that I attached? It clearly states that to activate the LAS Toolbar it requires the 3d Analyst Extension. Without it you can see see the data and use it for different calculations and in a mosaic dataset, however to utilize the toolbar you will need the 3d Analyst Extension. Please take a look at the document again.

‎10-29-2012

What error message are you receiving? What kinds of names are you using? Where is the data being output to? What version of ArcMap are you using?

‎10-25-2012

What type of raster are you classifying? What bit depth? How many training sites are you using? How many classes? Where is the input raster stored? What is the cell size of the input?

‎10-25-2012

Thanks for the update. Hopefully we will see these issues addressed soon. I am sorry that I was not able to come up with a more 'code' friendly workaround. If the environment setting is taken than it should not be a problem with your workflow any longer. I encourage any user that is having a specific issue or experiencing a problem to create an Incident with Esri Support. Then we can work towards a solution, explain a workflow or as in this case report the problem so it can be addressed.

‎10-25-2012

Have you evaluated all of the values in that column that you are using to create the new raster? Is there odd values within it? Missing Values? Or as Steve refers to is there a joined table to the raster?

‎10-24-2012

With the Lookup tool, you can create a new raster based on a field within the raster. Then you could use the Float tool to turn the integer to a float. You will lose the attribute table, but will gain the float raster.

‎10-24-2012

You can use this address http://support.esri.com/en/ and then login with your customer number. You can then use the webform to create an incident or call in to 1.888.377.4575 and use your customer number there.

‎10-23-2012

I would encourage you to create an Esri Support incident in order to have someone take a look at your file and sxd directly. The only other test that I can think of is if you try ArcGlobe, will the extrusion still not work on the problematic machine.

‎10-22-2012

I am not sure if the forums are a good spot to answer homework. I would recommend researching interpolation.

Online Status	Offline
Date Last Visited	‎05-21-2026 12:39 PM

My Ideas

Latest Contributions by JeffreySwain

Re: Losing Links to imagery

Re: Mosaicking is taking days, literally

Re: Calculation of builidings (LOD 2) from LIDAR Data

Re: Losing Links to imagery

Re: Error 010067 Zonal Statistics as Table

Re: ArcGlobe - Point features "extruding" underground show still show above ground

Re: LAS Dataset Toolbar

Re: Cannot convert raster to ASCII

Re: 'Out of memory' message in Image classification toolbar

Re: Define Projection fails on a TIN dataset

Re: Convert integer raster grid to float grid using one specific column in VAT

Re: Convert integer raster grid to float grid using one specific column in VAT

Re: Problem rendering feature extrusion in ArcScene 10.1--one machine works, one does

Re: Problem rendering feature extrusion in ArcScene 10.1--one machine works, one does

Re: Is better to use the IDW tool or the kriging and why?

Re: Wayback imagery and wayback metadata do not ta...

Re: Publish Imagery with symbology

Re: Replace Layer function for Tiled Imagery Layer

Re: Is there a way to stop the ArcGIS Online Map V...

Re: Mosaic Dataset hosted in ArcGIS Image for Onli...

Esri Forestry Group (EFG)