Latest Contributions by JeffreySwain

‎02-28-2012

Questions on georeferencing are some of the most common questions that we get in Support. These conversations range from basic how to questions all the way to questions like “Why are the buttons grayed out?” There are many places you can find georeferencing help. A few of these places are the ArcGIS Desktop Help documentation, the multiple Support Blogs (linked at the bottom), and the technical articles at Esri Support. Recently, we have been getting a lot of long-time customers using the georeferencing tool calling in because their toolbar is grayed out. If you are having trouble with an inactive toolbar – have no fear! There is a great article that details some of the known issues that can cause problems when georeferencing rasters in ArcMap. Of the issues described in the article, one of the most common has to do with datum transformations within a map document. When there are layers or rasters in the map document with different datums, the georeferencing toolbar will be grayed out or inactive. To activate the georeferencing toolbar, open a new map document and only add the raster that you desire to georeference. Georeferencing Toolbar at ArcGIS 9.3.1 Georeferencing Toolbar at ArcGIS 10 Always be mindful of which raster you are georeferencing, and always remember to save your solution by rectifying or updating the georeferencing. Otherwise the solution will only be applied to that raster in that map document.Support Blog Posts on GeoreferencingWorking with Rasters: GeoreferencingHaving problems georeferencing your raster image?Jeff S. - Raster Support Analyst

‎02-10-2012

As long as you have ArcInfo at 9.2, you should be able to use the Near Tool for the analysis. For your description you should probably split out the vector file by the different layers you are trying to determine the distance. So one polygon layer will have agriculture, urban, or grass etc. In terms of assigning a value to each cell, you could perhaps convert the polygon to a raster again and use the value for the distance created from the Near tool.

‎02-07-2012

What is the elevation of the polyline? Is it varialble or one value? Is 2 the desired elevation of the line or an offset? In terms of the viewshed tool, the SPOT field is to describe the elevation of a point for analysis, not offset the elevation. There is a bug report for the use of SPOT on a line feature, so I would recommend if you want to use an elevation other than the interpolated value of the line based on the surface raster, convert the line to points. Use the Feature Vertices to Point tool to export the vertices of the line, create the SPOT field and populate it with the values you need or use the OFFSETA to add an offset to the existing elevation.

‎02-07-2012

I am not sure you will need to perform the extract by mask prior to the zonal analysis. I would also consider if the cell size has changed when you exported the raster, be sure the cell size matches. If you are concerned that the value is not correct, the quickest test would be to resample the raster to a finer resolution. Eventhough the values will not change of the raster (just split into smaller cell sizes), performing the zonal statistics on this raster should yield better results if you are concerned that the cell centers are not in the proper zones. This will make the output from the zonal statistics tool perhaps more to your liking. To see the zones that the polygon is surveying, I recommend converting the polygon to a raster and then you will see what the tool is actually surveying.

‎02-01-2012

Were the two rasters used projected in the same coordinate system? It looks like the spatial extents are radically different or the spatial extents do not match and one is not projected. If that does not solve the issue, then I would recommend creating a Support Incident for specific trouble shooting with that data.

‎01-20-2012

I am confused about your 'depth as depths' statement. To see the layers below the ground you have to make the elevations below the surface or negative. The TIN should be the reflection of the points and breaklines that you input. If you are looking to extrude the TIN, they I would recommend converting the TIN to a multipatch or a polygon to extrude. I have seen utilizing points and then specifying depth to demonstrate the depth and even using the depth points to interpolate to a surface, but not depths displayed in a TIN. If you had a polygon layer you could have a field marked depth and then make the value negative in the extrude tab of the layer properties. There is some information on displaying some subsurface modeling here and a subsurface analysis video. You can accomplish this with 3d Analyst, but you need to generate multiple TINs for each layer and then extrude between them with the tool of the same name to create the multipatch.

‎01-20-2012

When you change the display to a 3 band color scheme, the identify tool will return that value(RGB), not the original pixel value. You can use the stretch renderer and then keep that, but the 3 band will return RGB values.

‎01-20-2012

I would recommend calling Support to create an incident, since it sounds like the problem is with all rasters. There could be issues with that particular profile, or if there is something else interfering with the display of the rasters. There should not be a limit from Image Server that will cause this issue.

‎01-20-2012

So you have to manually delete the service from the image server and then re add and then publish in order for them to turn on? Is the ArcGIS Server set to wait until the Image Server is running to start? Or prior to deleting the services do they appear off in image server and cannot be started? At this point, I would recommend calling Esri Support and we can step through the process and see if there is anything else going on.

‎01-19-2012

Also to echo what Luke mentioned, be sure you are using the proper pathing. In your example, you are not using the r".." nor the \\ necessary for python paths. I am not sure if that is causing the issue or not. Here is the help documentation that describes this. But if the paths are correct, then the only other issue maybe how much overlap and the coordinate system of the input rasters. I recommend making them the same coordinate system and like all other raster processing, having a common extent and not trying to multiply/divide NULL values is important. I would not think that the size of the rasters would cause an issue, unless they are so huge that you could not process them normally if you broke down the process step by step. Can you indicate what error message you are receiving? Or is it a direct crash? I would recommend changing the working environment if you are getting intermediate results back in the geodatabase. There is information on setting the environment in python as well.

‎01-18-2012

There seems to be a lot going on with your project based on the description. If you are having issues with the points as a TIN, then I recommend trying to convert the points to an interpolated raster, a terrain or try a smaller subset of the points, since TINs have a finite size based on the nodes. It is possible to try and create a TIN that is too large or complex and you will generate that error. In terms of your questions about workspaces, the TIN generation will follow whatever field you specify as the 'elevation' or height field. If it is confused, perhaps the wrong field was used? The Extrude between tool requires two TINs and a polygon. I recommend being sure you have coverage overlap with both the TINs completely and be sure your polygon does not have a coincident boundary. So the TINs will need to cover more area than the polygon. If you look at the diagram for the Extrude Between tool then you will see a good example. If you are under a time crunch, rather than wait on the benevolent input from fellow users, try calling in to Esri Support. You will find they are much more responsive and more than likely will have the information you need to proceed.

‎01-18-2012

Per the Supported Raster Formats help, ArcMap does not write back out to .dem as the format is read only. You will definitely have to project the data between the coordinate systems, while you might be able to change the projection designation it will introduce new problems for the data. It will not display correctly since the extents were not altered, just what you defined it as. There is an gdal utility that can process the conversion listed here. It looks as if you will need to convert the raster in ArcMap to an ASCII file prior to using it. I recommend the Raster to ASCII tool.

‎01-13-2012

If you do not see the 'frame' I would consider the resampling method of the pyramids. If you have bilinear, then I would recommend trying to create the pyramids with nearest neighbor. If you see the reference in this help document, you can see what this will fix. To modify the resampling method use the Build Pyramids tool and then modify the environment settings to change the resampling method. [ATTACH=CONFIG]11174[/ATTACH]

‎01-13-2012

You can convert the polygon to a raster with the Feature to Raster or Polygon to Raster. Be sure to specify the elevation of the polygon in the field when prompted in the tool. This will make each of the polygons one raster value. You cannot use the multiple vertices in your polygon, you will have to export them as points in order to interpolate the edges. The polygons will have one value in raster form for that contiguous polygon.

‎01-13-2012

Based on what you have provided, I have a few follow up questions. 1. What bit depth are the rasters that you are finding the difference of? 16 bit as well? 2. Are you sure it is using a color map and not just a color ramp? 3. What is the range of values present in your raster per the statistics? 4. How large is this dataset, file size wise? It will not be possible to find the raster attribute table if the number of unique values exceeds a threshold established by the properties in the map document, the highest default value is 65,536. This is set to avoid memory crashes, you can increase that number, but bear in mind it may allow the processing to proceed, but will take a long time to process. The value can be found under Customize > Options > Raster > Raster Dataset. If you are looking to find output values with decimals as indicated, something is not correct as your output appears to be a signed integer. Without knowing more about the inputs, I would ask you provide more information about the inputs and perhaps the reason the processing is not working will become more clear.

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

My Ideas

Latest Contributions by JeffreySwain

Georeferencing in ArcGIS 10 or “Why is my georeferencing toolbar suddenly grayed out?”

Re: calculating the distance polygon to polygon

Re: polyline ZM process Viewshed

Re: Zonal statistics as table does not produce correct results

Re: Extract by mask shifts cells when set processing extent

Re: Surface interpolation difficulties in ArcScene

Re: Pixel value from mosaic but not a layer?

Re: Problem getting services

Re: Image service does not start after restart unless done manually

Re: calculations on rasters stored in memory

Re: Surface interpolation difficulties in ArcScene

Re: How to convert a raster file in a USGS DEM (*.dem) file ?

Re: Raster Split Tool creates NoData Frame for Clipped Raster

Re: PolygonZ to Raster

Re: Processing raster difference in Image Analysis

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)