Hi Jamal,
I agree that the reclassify tool should automatically read min/max. I tried to reproduce this issue with similar data in ArcGIS 10 SP 2; however, I have not been able to reproduce the behavior you are experiencing. It could be possible that this behavior is either a data or a computer specific issue. Could you please try to see if you can reproduce this behavior with other rasters and/or on other computers?
ArcGIS 10.1 is scheduled to be released in the first quarter of 2012. ArcGIS 10.1 Beta 1 is currently available. Domestic (USA) users need to be current on maintenance and approved by the maintenance contact for their organization to participate. International users need to be nominated by their distributor.
We greatly appreciate our users�?? feedbacks and try our best to fix issues that we are aware of or our customers brought to us. We are sorry that you encounter issues in ArcGIS 10 and we will be glad to work with you to identify those issues and fix them in next service pack/release. You could contact Esri Support Services (in your case, I guess Esri UK) to report bugs.
Thank you for your feedback.
Best regards,
Pavan
Hello again,
I believe the source of the warnings we were getting in reclassifying our raster (this could or could not be the same source for Jamal's troubles) was that somehow the raster pixel depth (8/16/32 bit signed, unsigned, etc.) had been changed so that the reclass we were trying to pull off (the new values we were assigning) was not supported in the format the raster was in.
What we did to change this was go back a few processing steps and make sure all statistics had been calculated and that our raster that we eventually wanted to reclass had the correct pixel depth. Somehow along the way the pixel depth was changed to 8-bit unsigned and in order to reclassify how we wanted we needed 16-bit signed.
This may help, but likely the issue has already been resolved,
PVS