Latest Contributions by JeffreySwain

If the lake is one value you could extract that portion of the raster by attribute and then make that particular raster the 'zone.'  In the Zonal statistics tool, you can use a raster as long as it is an integer and the values for the zone are homogenous.  There is not just a simple tool you can freehand a graphic and any created tool like that will likely contain the same tools mentioned above. ... View more

You will need the RPCs to orthorectify, but I echo what Melita said and that it should be projected already.  I would be sure that on the way to you that they have not been altered. ... View more

When you define the mosaic order, are you setting the order in the mosaic dataset by setting the default or manually changing the method in ArcMap?  Simply adding the values to the field is only halfway there.  You have to specify the default mosaic method in either spot to utilize the values you have specified. ... View more

Was the master mosaic dataset and the subsequently created mosaic datasets created at the same service pack?  Or was the original created at one level and the rest at other levels?  If so I would recommend creating a new geodatabase or new mosaic dataset and adding all the intermediate mosaic datasets again. ... View more

I would consider using the Reclassify tool on the floating point raster and then select the class break as your desired selection.  The resulting raster should have the pixels that are above the value.  While the values will be different the attribute table created could be used to total the number of pixels in your class.  Be sure your raster has statistics and a histogram created for the classify button to work in the tool. Without the statistics and histogram, the classify button will not seem to do anything. ... View more

Be sure that you have prepped the rasters accordingly, not just the mosaic dataset. You have to prep the source rasters. Per the help,     All the bands have their statistics calculated.     All the bands have their histograms built.     All the raster datasets have the same number of bands.     All the raster datasets have the same pixel type and pixel depth. Only 8-bit unsigned and 16-bit unsigned bit depths are supported.     None of the raster datasets have an associated color map. Since you mentioned that they are off a network drive, be sure there was not a network related issue. ... View more

Any 30 Meter raster imagery would for the most part be considered very pixelated.  Satellite imagery like LandSat comes in 30 x 30 meter pixels.  Depending on the scale that the imagery is viewed at, it could be very pixelated.  The pyramid generation and changing the display method on the layer properties may alter the look of the raster, but at the core, 30 x 30 would be coarse.  I would not consider trying to georference such imagery unless you have some identifiable object that occupies 900 square meters (30 * 30) or the size of one pixel.  The imagery you are using would be best used in landcover analysis where you could identify the pixels based on finer resolution imagery.  Consider the following link and open the section on pixels.  When you see the rasters presented there, it will explain the expectations. [ATTACH=CONFIG]12530[/ATTACH] ... View more

I would consider the ideas page as someone has discussed this request.  Adding more points to this post will raise the awareness of the request to the decision makers. ... View more

So you are setting the Nodata in Properties to red and getting the output there.  Correct?  If that is the case then the value is correctly set and should be ignored because when you identify it it should say NoData/Null.  Let us back up a bit.  Have you tried to evaluate the zone in particular and see if there are nodata pixels? Also I would consider converting the particular polygons into a raster to see where they are actually pulling from.  Be sure to specify a cell size to match the raster. I would still consider it a bug if the nodata value is being considered in the calculation.  The options for the NoData would be to ignore any zone that contains a nodata value or just ignore the nodata value.  I would recommend creating a Support Incident and have someone take a look at your data specifically. ... View more

Is the Nodata value of -99999 indicated in the source properties?  Or is it known to you as the filler.  Traditionally the value of Nodata will appear as Null and you will not get any information for the zones with the Null.  If you have a different nodata value described in the source properties, but have values of -99999 in your raster that you recognize as Nodata.  I would consider setting the Null value of -99999 if the ID button returns a value of -99999 when you select the raster nodata areas.  The NoData should not be considered in the calculation of the mean.  I would follow the previous recommendation and set the -99999 values to Null which should prevent the calculation error. ... View more

For part of your description, I would think that a Zonal Statistics as a table would be the best fit and then again you also describe something that I think that weighted overlay should be better. The key to the weighted overlay is that you will have to create the density percentage raster.  However, since you said that the zonal statistics as a table will only make one result and the zonal statistics is failing there must be something else wrong. Do the polygon and raster have the same coordinate systems?  Since you did the conversion to points, generally how many points are in each polygon?  Also are you using the Ascii file directly or did you go ahead and convert it?  I am not sure why you could not clip the raster, the Raster clip is under Data Management > Raster > Raster Processing.  That clip will take the raster as an input. There are a lot of moving parts and will probably require a stepwise process, but based on your last statement I would re evaluate your inputs. ... View more

To determine the specific elevation changes you indicated, I would recommend creating the streamlines, convert the vertices to points, use the add surface information to see the current elevation, add a field and modify the elevations accordingly, use the Feature to 3d by Attributes to create a new 3d points at the new elevation and then re draw the line by snapping to the new points.  Once this line is created, you can re import it to the TIN. You could copy the TIN and then add the 'burned in' areas in the form of line or polygons using the Edit Tin Tool. If you are trying to test out the look, I would consider using the Interactive Add TIN Line tool. ... View more

Can you indicate what service packs you have installed? And the format of raster you are creating?  Generally speaking, what you are describing happens when the spatial extents do not lineup.  Also indicate whether you are writing to a local location or across the network? ... View more