Latest Contributions by SteveLynch

- how many columns and rows does the output raster have? - do the input points display within the extent of the raster? - include a print of the number of records in out_weatherstations, use GetCount, in your script to see how many points are going into IDW ... View more

Please keep me posted via this thread or via email slynch@esri.com You could use RasterCopy, with output to .tif for example, when making a copy of the raster extent from the mosaic dataset and remember to, in the tool's environment, set SnapRaster = input Mosaic ... View more

I do have some questions: 1) what version of ArcGIS are you using? 2) how many columns and rows does the raster have? 3) what type of raster, Esri grid or .tif or .img or FGDD raster or ? 4) use CopyRaster, with output to default FGDB, does the output have the line? ... View more

- can you post a screen shot of the whole screen? - try changing "Weight by" to Multiplier and then back to Percent ... View more

The contour lines should be a single line per interval unless you've specified a value for "Maximum vertices per feature" but I don't think that is the case because you are having the same problem with ContourList. What version of ArcGIS are you using, how many columns and rows is the input raster, have you set any environments? Could you zoom to an area which includes a few of these short segments and take a screen shot of the contours, symbolized on something that'll show them as segments, and the input raster. Could you post the output from ContourList (i.e. zip and attach to post)? ... View more

Your input is integer.   You could add a bit of "noise" to your DEM. For example, use CreateRandomRaster using your DEM's extent and cell size to create a raster of random values between 0 and 1. Add this noise to your DEM and Contour it. ... View more

The RasterToPolygon tool threw 2 errors, viz., ERROR 000864: Input raster: The input is not within the defined domain. ERROR 000969: The input raster is not integer type. The first one is stating that the tool requires a certain type of raster, for example, integer raster, integer image service, integer mosaic, etc. and because the supplied raster is of type Float it does not fall within that domain and then the second error is self explanatory. It is always helpful to look at the error Error 000864 ... View more

The input raster must be of type integer. ... View more

Mark Are you 1) assigning different suitability values to each of the zones? or 2) do you only want suitability to be calculated in non-NoData areas?   for #1 I'd suggest you look at Con and for #2, don't use the zones as a criterion but rather set it as a mask in the Environment. ... View more

Mark Your IndustrialZoning layer has a lot of NoData and this means that no suitability values are created in those areas. I.e if any of the input criteria have NoData in a particular area implies that the suitability at that location will also be NoData.   ... View more

Screenshots of 1) Transformation panes of each one of the Unique categories 2) suitability map   will be useful. ... View more

the output coordinate system, if not defined, usually comes from the input.   Glad to help and happy modelling. ... View more

... and we do have an issue where this error is thrown when projected and geographic coordinate system are used in the same Suitability model. Therefore please make sure that all your data are in a projected coordinate system. ... View more

Your data don't need to have the same cell size or extent. The final output will be resampled to the largest cell size of your input criteria. The extent relies on what area is common to all criteria. The first criterion that causes the error to be thrown, does it have the same coordinate system as the criteria already transformed? ... View more

 click on the first raster and then shift click on the last raster ... View more