ArcHydro: 2.1.0.98: Doesn't Acknowledge Environment Settings

[PeterWilson]

I've set the Processing Extent and well as Snap Raster under Environment Settings and Arc Hydro Fil Tool still processes the entire extent. Has anyone else come accross this?

Regards

[MarkBoucher]

Are you setting the processing extents via "Geoprocessing>Environments"?

My practice has always been to extract by mask a rough cutout portion of the our countywide DEM before starting a ArcHydro project. I originally assumed I'd need to do this to limit the processing extents. All he ESRI examples do this. A second reason to extract the local DEM is to preserve the data set. The countywide data can be updated periodically. I'd like to preserve the dataset so that if the DEM changes, I can do a comparison to see if there will be different results in the future. So I've never run into your problem.

I've had the batch processing run only for the batch point extents.  (http://forums.arcgis.com/threads/41988-Resetting-Raster-calculation-limits). This was before I knew about "Geoprocessing>Environments". So in my experience, I've had the opposite problem you are having.

[PeterWilson]

Hi Mark 🙂

Thanks for replying to my post, yes I've set the Processing Extent under the Geoprocessing\Environment Settings, yet is seems the ArcHydro Tools doesn't adhere to the Environment Settings as it still processes the entire extent. I'm busy processing a very large study area and testing a new model that I've developed with ModelBuilder; HEC-GeoHMS and ArcHydro. I don't want to clip the DEM as this resamples the DEM and changes the cell values ever so slightly causes the results to differ from the full model. I was hoping to run the model based on a defined extent of the existing rasters without having to clip the rasters.

Are you setting the processing extents via "Geoprocessing>Environments"?

My practice has always been to extract by mask a rough cutout portion of the our countywide DEM before starting a ArcHydro project. I originally assumed I'd need to do this to limit the processing extents. All he ESRI examples do this. A second reason to extract the local DEM is to preserve the data set. The countywide data can be updated periodically. I'd like to preserve the dataset so that if the DEM changes, I can do a comparison to see if there will be different results in the future. So I've never run into your problem.

I've had the batch processing run only for the batch point extents.  (http://forums.arcgis.com/threads/41988-Resetting-Raster-calculation-limits). This was before I knew about "Geoprocessing>Environments". So in my experience, I've had the opposite problem you are having.

I't seems to only be happening with the ArcHydro tools within the Toolbox as my spatial analyst tools work correctly.

Regards

[MarkBoucher]

Are you setting the processing extents via model builder or the mxd?

Does it make a difference?

[ATTACH=CONFIG]16131[/ATTACH][ATTACH=CONFIG]16132[/ATTACH]