Bug in CLIP Function (clip raster with shapefile) ?? Need help

[bodoMalowerschnig]

Hello

I am Using Arcmap 10.0

I simply use the ArcToolBox->Data-Management -> Raster -> Clip Function to Clip a DEM File with my shapefile polygons.

Before I did that, I RESAMPLED the DEM once, to have a higher resolution and get more accurate areas (original dem has only 10x10m resolution, now it has a resolution cellsize of 0,2x0,2 meters)

First the results look fine, but see for yourself. It seems as if the CLIP function seems to add a few pixels on every upper right corner of a polygon. Ok, thats only a few pixels, but it is wrong.

It really gets worse if the polygons are very small and have many edges. (horror.jpg)


I did not change any settings with the CLIP function. I only use the 2 input files, and check the box "Use Input features for clipping..."

Any help would be appreciated.

[SusanJones]

Georeferencing is indeed broken during a clip at ArcGIS 10. I dont know how ESRI allowed this to happen because it was fixed at ArcGIS 9.3.1.

I vaguely remember scripting the same function at ArcGIS 9.3 and was relieved to see it was fixed in ArcGIS 9.3.1.
http://www.spatiallogic.co.nz/downloads/doc_download/24-clip-raster-2-shape

For now I have just spent 5 days struggling with this bug in ArcGIS 10 when the raster clipping and georeferencing function is handled correctly in FME 2010.

I am seriously considering going back to ArcGIS 9.3.1.

So I guess I am giving a heads up use the clip and georeferencing transformers in FME Desktop.

Susan Jones
Director
Spatial Logic Limited
sjones@spatiallogic.co.nz
http://www.spatiallogic.co.nz

[Anonymous User]

Original User: jpartlow

I am experiencing a similar problem - getting too many cells when clipping grid with polygon feature layer using Data Management Tools\Raster\Raster Processing\Clip.  Do you know if there have been any other fixes or solutions to this [other than springing for FME]?

[EricRice · Accepted solution]

Joe,

The workaround in 10.0 would be to use Extract by Mask from Spatial Analyst if you have it.  If you want to get 10.1 Beta, this bug is also fixed in that version.  The tracking number for this issue is NIM067762. 

Regards,
Eric