Latest Contributions by EricRice

Hi Phil, If you're migrating from stand-alone Image Server and you have source images and SO's already built (in an ISDef), then no images will get loaded into the geodatabase.  Load the MD's using the ISDef file.  The MD will reference both the source and the SO's that already exist. The default behavior for mosaic dataset overviews changes depending on the type of geodatabase.  I can assume you plan on using an enterprise geodatabase if the overviews are going directly to the gdb.  FGDB mosaic datasets do not load overviews into the FGDB - they create a folder at the same location as the FGDB with the same name, but with a .overviews added to the folder name. This is a great starting place. Migrating an .ISDef to a mosaic dataset This is also a must read if you're going to work with mosaic datasets. Imagery: Data management patterns and recommendations Pertinent information for your question. Mosaic dataset overviews My personal preference is to not load overviews into my sde geodatabase.  I define them so they go to my file system, where they will reside as tiff files and can be easily managed with OS tools. Hope this helps! Regards, Eric ... View more

Bryan, You should probably contact Esri Support to provide us with a reproducible case.  My only other suggestion is to use Extract Multi Values to Points instead.  The main benefits of this newer tool: There is no output feature class - we simply edit the input. Multiple input rasters simultaneoulsy Output field name remapping. Support for multiband raster input This tool is available begining in ArcGIS 10.0. Note: If completely unable to upgrade, you might find this useful. Python garbage collection module. http://docs.python.org/library/gc.html  referenced in this thread. http://forums.arcgis.com/threads/36799-Zonal-Statistics-as-Table-Overlapping-Polygons-Solution-Required?highlight=python+garbage+collection Regards, Eric ... View more

Chris, Thanks for the follow up on my last post to clarify, and thanks for helping Carina.  I have not had any time to get back to this thread (internal event) so it was good see that peer to peer support. Thanks again, Eric ... View more

Manahoana, If the extents are all correct, have you verified that your pour points are actually on the flow accumulation raster (where there is high flow)? If not, please use the Snap Pour Point tool.  Lacking this snapping procedure can also, but less common than extent settings, lead to small watersheds. Here are other threads on the topic. http://forums.arcgis.com/threads/24716-Watershed-tool-problem?highlight=watershed+extent http://forums.arcgis.com/threads/20305-Watershed-polygons-cut-off?highlight=watershed+extent Eric ... View more

Chris, The output of Snap Pour Point is a raster.  You input your point features, specify a radius, and it will move the 'feature' to the highest value cell of the flow accumulation grid within the radius.  It's similar to what your doing but easier. It also virtually guarantee's you won't hit that occasional issue you mention. Watersheds that are single pixels or just a few is basically 99.9% an extent setting issue.  If someone is using pour points, the way to verify the extent is the problem is to take the resulting (wrong) watershed raster and display the nodata pixels as some color.  You'll find the extent of the watershed raster is limited by the geographic extent of the pour points and is not equal in extent to the DEM, flow direction, or flow accumulation rasters.  This issue can be avoided by running the Snap Pour Point tool and specifying output extent = Flow Dir, Accumulation, or DEM.  Snap Raster should always be set. Regards, Eric ... View more

Ok, got this one figured out.  We need to delete the comma's and replace with spaces.  I reviewed our own documentation for the Ascii to Raster tool and it basically says the cell values should be delimited by spaces.  When I do that the data comes in fine even without running the Ascii to Raster tool.  Like I said earlier, we support .asc files as raster datasets (when they are formatted properly).  Here is a screenshot of the data. ... View more

I am having the same issues as you with this data.  I'm still looking for a solution.  I also don't get why the instructions are telling us to do a find/replace to remove semi-colon + space and put in a comma, when after we save from Excel to CSV it becomes comma delimited.  So I guess we can skip that step.  🙂 I'll keep you posted on any progress I make. Note: I'm working with the orginal file named Speed10.asc. Eric ... View more

I downloaded the entire database from the website so I have the data.  I have not gone through the steps to get it working; I simply read their instructions and passed on relevant points to you.  I can try to get it working with the data I have and let you know, but to be totally honest and up front with you, I may not get to this problem today.  If you have a deadline or urgent need to get it working I strongly encourage you to go through official channels. i.e. Esri Support or Esri UK Support if you're an international customer in the UK. If you're not in the UK, contact your local distributor.  They should have analyst standing by that can provide immediate support. I'll do my best to try and get the data working asap. Eric ... View more

Hi Daniel, A carriage return is basically when someone presses the Enter key on the keyboard.  As an example of what they are telling you to do.... Pretend you finished the last paragraph of a paper you were writing; then you hit Enter once,twice, 3 times to create empty lines at the end of the paragraph.  It's those empty lines they want you to delete.  Which can be hard because there isn't anything there for you to see to delete.  In terms of the data, the file I opened was not comma delimited.  The data I downloaded looks like this. 9.4; 9.6; 8.2; 4.8; 3.5; 6.3; 7.1 So it is semi-colon + space delimited.  They want you to do a find/replace in notepad to make it comma delimited.  If your download was comma already you should be all set and just need to remove the carriage return and add the header. Even though you shouldn't have to...I'm going to recommend that you run the ASCII to Raster tool once you have completed the steps. Regards, Eric ... View more

Greetings, Check your extents as this is the most common cause.  Try setting the processing extent to that of the original DEM. Regards, Eric ... View more

Greetings, After reading the Windspeed Database Information Sheet I found the section you need... �??The ETSU NOABL wind speed data is stored in ASCII (text) format. The file format is ASCII, a simple text format. It may be that there is no dedicated function in any particular GIS to read this file type. However, as the file type is simple and readable by a number of different applications, (eg MS notepad, or Excel) that it should be possible to import the data. The text file accompanying the ASCII files describes the file format.�?� Importing into ArcView Open your ASCII file in Excel as semi-colon delimited data, delete header line and first column and then save as a CSV comma delimited file. Open this in a text editor such as Wordpad and Replace the 'semi-colon+space' with a 'comma' and then delete carriage return at the end of the file and then add the new header lines at the top of the file: ncols 700 nrows 1300 xllcorner 0 yllcorner 0 cellsize 1000 Save it. Next, in the file manager just delete the ".csv" suffix and replace with ".asc" and it is ready for Import into ArcView if you turn on the "Spatial Analyst" extension. My note would be, if you perform these steps, you don't need Spatial Analyst.  ArcGIS reads .asc files as raster datasets assuming they have the header information outlined above.  You will still have to define a spatial reference for the data, but I didn't see any information provided by the data provider as to what it is.    You can see from their instructions that they are basically trying to get you to create an Esri Ascii Raster ... View more

Please use Extract by Mask.  If you run Feature Vertices to Points you won't be extracting all the cells underneath the line, unless you densify the line in advance to the resolution of the raster you wish to extract from.  Extract by Mask requires no conversion in advance of the process and will save you time.  The output will be just the pixel values underneath the line.  What is your desired output?  Points, Raster, Table... Regards, Eric ... View more

Noel, What is the projection listed in the layer properties?  Have you confirmed that the projection listed in the tiff header is different?  ArcGIS reads tiff header information.  The other thing to consider is the coordinate system of the map's dataframe.  If it is different, then ArcMap will project the data on-the-fly to whatever the dataframe is.  My guess is your data is either in a geographic coordinate system, or the dataframe is.  To check the dataframe, go to ArcMap > View > Dataframe Properties > Coordinate System tab. Perhaps some screen shots would be helpful to show the distortion in the X direction, and of the layer properties (coordinate system info).  It would also be helpful to know the location of the data - some projections distort more severely in certain geographic locations. Best Regards, Eric ... View more

In the Plus tool, just browse to the individual band.  The other option is to add each band to the TOC, then the tools should see the band as a raster layer, which is valid input. Regards, Eric ... View more

Hi Cory, The reinstall I'm sure you don't need Support's help with, but if that doesn't solve it we may want to have a look at your data and Support is the best option for getting it to Steve and myself.  They'll also check for any other conflicts that may be the source of the issue.  If you contact Support please point them to this thread. Eric ... View more