POST
|
You should not have to do anything after running Arc Hydro install .msi (assuming it successfully installed). The Arc Hydro add-in should just "appear" next time you open Pro and so should the Arc Hydro Pro toolbox. If it does not, try to uninstall it (using Windows Add/Remove Programs) and then installing it again. Make sure that all instances of ArcGIS Pro are closed before you do uninstall/install. You will need admin rights for installing.
... View more
03-02-2023
05:07 PM
|
0
|
1
|
745
|
POST
|
I tried your modified MB (running on Pro 2.9.2/AH 2.9.55) and was able to make it work. I have added the result of watershed delineation (watershed polygon and watershed point FC) not only as input into the longest flowpath tool but also as a precondition for it to run. i also exposed every input and output as a parameter in the model so you can explicitly assign them. see if that helps.
... View more
09-22-2022
09:48 PM
|
0
|
0
|
975
|
POST
|
Please provide ArcGIS Pro and Arc Hydro tools versions you are using. And if you have previous software versions when your MB did work. We'll try to recreate the problem on our end and see what the issue might be. Notice that your "Line Parameters from 2D Line" tool in the model builder is not being correctly validated - so there is something wrong there.
... View more
09-22-2022
04:46 PM
|
0
|
1
|
987
|
POST
|
Tom, This is not quite the experience i have seen. Just tried on my machine and opened over a year old aprx in Pro 3.0 with AH tools and the tools just worked. I run one from the history (was suspecting that this might be a problem) and one "fresh" and they both worked. Are you able to run any other geoprocessing tools (non Arc Hydro) within that project? And have you tried with another legacy project? We'll put a new 3.0 build out tomorrow (just in case, and with some new tools), but would be good if you can try to run any other gp tools first to just see if there is something wrong with the aprx. Dean
... View more
09-15-2022
04:59 PM
|
0
|
3
|
958
|
POST
|
Steve, Depending on the quality of your DEM and streams, this could be an "easy" exercise. If your DEM and the flow direction match the placement and elevation of your streams, then you can directly use the HAND (Height Above Nearest Drainage) approach. You will need the following rasters (I suggest that you use .tif format for your rasters): DEM (i'll call it DEM.tif). Should be in correct horizontal/vertical units - e.g. meters. Flow direction raster derived from the DEM (FDR.tif) that "flows" into your streams. Stream raster (STR.tif). This can have value of 1 where stream cells are and nodata elsewhere. The elevation of the streams (thalweg) should be reflected in the DEM. The steps are then (these are all core Spatial Analyst functions - you do not need Arc Hydro): Use "Flow Distance" (Hydrology toolset) to calculate the HAND (HAND.tif) surface (that is the "output raster". Specify inputs stream raster (STR), surface raster (DEM) and flow direction raster (FDR). Keep all other parameters at their default values. Once you have the HAND surface, to get the depth and extent of flooding for a specific depth (D) in the same vertical units as the DEM, use the simple conditional statement (use CON SA function from “Conditional” toolset) and specify: HAND.tif as your conditional raster. Expression as: Value is less than or equal to 3 (D is your flooding depth – in your case it is 3). 3 as your true raster (D is your flooding depth – in your case it is 3). Leave false raster entry empty (meaning all values outside of your flood extent will be nodata). Specify output raster (I like to put name of the depth in the output name – e.g. fe3m.tif – for flood extent of 3m, but it can be anything). That’s it. In the output raster, where you have values, area is flooded and where it is nodata, it is “dry”. If you want to calculate depth of flooding for each cell, just use the MINUS function and use fe3m.tif and HAND.tif as inputs (in that order). Hope this works for you.
... View more
08-15-2022
04:18 PM
|
2
|
1
|
889
|
POST
|
John, good to hear from you. Hope things up North are moving along :-). Yes, the new terrain processing workflows are geared for high-resolution DEMs (Lidar/IfSAR derived). And from current experiences and ideas, it will still be a "hybrid" where there will be some "Adjust Flow Direction" activities. High rez DEMs are noisy and without some massaging the results are not necessarily what they need to be. Specially in landscapes with built features where culverts/bridges can still pose significant problems for hydro feature extractions. And in hydro-flattened areas that can introduce additional problems. So it will be some change to the current AH workflows, some new AH tools, and some use of new capabilities in 3.0/3.1. But in a nutshell, it will still be quite a bit of "tweaks" and steps in the workflow. To take advantage of the new core SA hydro stuff you will have to be in Pro 3.0. In 2.9, we have all key Arc Hydro functions for terrain preprocessing working, but all the new stuff will be 3.0 and up based.
... View more
08-15-2022
03:22 PM
|
1
|
1
|
704
|
POST
|
Arc Hydro is not a product and does not have an explicit "road map". In general, new Arc Hydro functionality is developed through specific customer projects and the tools and knowhow developed through those projects are then rolled into Arc Hydro and made available to the community. Some of the functions (usually enhancements to existing functions) are developed based on specific requests from the users (when we hear many users asking for the same functionality) or during tool updates and bug fixes. Having said that, here is what is on our “short list” (end of 2022) in no specific order (and possibility that we swap some functions in and out): Terrain processing: Incorporation of new Spatial Analyst functions (Pro 3.0) for flow direction and flow accumulation without need for filling into Arc Hydro terrain processing workflows. HAND derivation from NHDPlusHR (tools and workflows). Watershed delineation: Batch watershed delineation for polygons. Hydraulics: Calculation of Manning’s n for cross-sections and export to HEC-RAS .sdf file. Computation of left and right overbank lengths and export to HEC-RAS .sdf file. Hydrology: Calculation of CN raster from land use and soil hydro group lookup table. Longer-term (2023), we will be looking at the tools and workflows for hydrographic feature extraction from high-resolution DEMs. This includes streams, “lakes”, and wetlands. Many of these tools and workflows already exist in Arc Hydro, but we will be revisiting those with the goal to minimize user inputs and streamline the process. This will cover both “traditional” techniques as well as introduction of new machine learning techniques. If you have any specific ideas, feel free to contact the Arc Hydro development team directly (archydro@esri.com).
... View more
08-12-2022
06:09 PM
|
0
|
3
|
743
|
POST
|
You are correct. This tool has not been ported to Pro yet. We will put it on our short-term plan. As we move the tool, this gives us an opportunity to potentially improve on it. Is there something specific about that tool that would work better for you?
... View more
05-31-2022
11:38 AM
|
0
|
1
|
559
|
BLOG
|
Attached document presents best practice in reporting issues to the Arc Hydro team when problems are encountered with Arc Hydro tools and standard problem fixing approaches do not work.
... View more
05-22-2022
03:03 PM
|
1
|
0
|
693
|
POST
|
Thanks for the problem elaboration. As always, there are many ways to do it, but I think the easiest would be to use "Drainage Area Characterization" Arc Hydro tool (in Terrain Morphology -> Drainage Boundary Processing toolset). This tool "slices" through each drainage area from its bottom up and calculates elevation-area-volume (EAV) curves and stores that in the resulting EAV table. So your workflow is then to calculate for each drainage area the water volume coming in based on the P-E-I (precip, evaporation, infiltration), from that volume look up the depth from EAV table and add that to the minimal elevation in each drainage area. That gives you the "water surface elevation" (WSE) in each drainage area after being "filled" with water. Calculate WSE-DEM and where positive you have "flood" (ignore the rest). Convert that into a polygon and that is your result.
... View more
05-19-2022
02:35 PM
|
0
|
0
|
1284
|
POST
|
Not completely sure what you are trying to accomplish. In a "mechanical" way, once you have identified which depressions you want to fill, you can copy all OTHER sink polygons into a separate feature class (these are the "deranged polygons" that you do NOT want to fill) and then use Arc Hydro "Fill Sinks" function and provide the deranged polygon feature class as one of the inputs. All other depressions will be filled. That will give you the "hydro DEM" that you can compare with the original DEM and get specific statistics. Also, if you look at the "Sink Poly" feature class resulting from the "Sink Evaluation" function you can see some metrics (FillArea, FillVolume, FillDepth) that might help you with your sink selection. A more comprehensive discussion is provided in Arc Hydro document "Arc Hydro - Identifying and Managing Sinks.pdf" https://community.esri.com/t5/water-resources-documents/arc-hydro-identifying-and-managing-sinks-pdf/ta-p/907728 .
... View more
05-17-2022
10:33 AM
|
0
|
2
|
1312
|
POST
|
There are probably several ways to do that (specially since you are focusing on the change between two locations), but here is how you can take the points with Z and impose them into the DEM. You will also need the new channel (2d) alignment that points "sit" on. Use Arc Hydro tool “Construct 3D Lines from Point Values” (in Arc Hydro Tools Pro -> Watershed Processing -> Line Processing toolset) to create a 3D representation of your new channel. Check tool help (for individual layer entry) to see the data schema requirements for the point and channel feature classes. Do not provide optional "Input Raster". Then use Arc Hydro tool “Convert 3D Line to Raster” (in Arc Hydro Tools Pro -> Watershed Processing -> Line Processing toolset) to create a raster from your 3D representation of the new channel from the step above. Then mosaic that into the original DEM. And now you have the "modified" DEM and you can do whatever else you want with it. Again, if you are just trying to compare stream power and slope of the new channel to the original channel, this might be "too much" and you can just focus on the 3D vector representation of of the two sets of lines.
... View more
04-02-2022
04:33 PM
|
1
|
0
|
1646
|
POST
|
Thanks for bringing this problem up. it seems that 2.9 is a bit more case sensitive than previous versions were. the original code stated "arcpy.env.OutputZFlag = "disabled"". Worked fine till Pro 2.9. In 2.9 it should be arcpy.env.outputZFlag = "Disabled". if you are doing it from the python command line, the autocomplete will pick the lower case string representation and either version of "disabled" will work. the script is not so forgiving. This code has been fixed in the latest released version of Arc Hydro for Pro (2.9.23) as of 3/7/22. Please download and upgrade (and as always, first uninstall the older version).
... View more
03-13-2022
06:48 PM
|
0
|
0
|
760
|
POST
|
When using HAND method for "flooding", the "Input Flood Depth" is the depth above stream centerline that you want to "flood" with. What that specific value is, is up to you. For example, if you use the "max depth of the creek", that is the equivalent of the "bankfull" and most of the resulting flood polygon should be contained within the channel. Anything higher should start spilling into the overbanks and you should get "flooding". So where do you get that number? Depends on what you are doing. It can come from the observations (e.g. high water mark or a stage from a gage) or through flow modeling and rating curve to convert flow to depth. If you are doing the rating curve approach, make sure that the rating curve is based on the same resolution data you used to derive HAND with (or is adjusted accordingly). And remember that inherent assumption in HAND flood modeling approach is that your water surface is uniform (constant) and parallel to the bottom of the channel. For each channel segment. So if you expect that the depth will change (significantly) as you go downstream, you should partition the overall stream into multiple segments that have uniform (but variable from segment to segment) depth and then use "Define HAND-based Flood Depth and Extent from Table" tool to get the floodplain. More work but might give you better results. If you stream segment is short, then first follow the approach you have presented (single reach), see if you like the results, and if not, then use the "table" approach. Note that you will have to reprocess the input data and partition the streams and get their catchments before you can use the "table" approach. Hope this helps.
... View more
03-03-2022
11:42 PM
|
1
|
0
|
1911
|
POST
|
Great, and thanks for marking it as a "solution". Let me know how your work progresses with implementation of executeAH approach. The doc I have pointed you to can use some refresh and if we can make it better based on your experience (e.g. more clearly describe the process so there is less research you need to do), I'd be happy to do so. Feel free to reach out directly to me if you have any further questions/comments. ddjokic@esri.com.
... View more
09-17-2021
08:24 AM
|
0
|
0
|
1303
|
Title | Kudos | Posted |
---|---|---|
1 | a week ago | |
1 | 04-02-2022 04:33 PM | |
1 | 12-05-2023 12:58 PM | |
1 | 10-24-2023 11:12 PM | |
1 | 03-23-2023 10:40 AM |
Online Status |
Online
|
Date Last Visited |
3 hours ago
|