nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

流域の最長流路エラー 010429

TysonBartlett

<\/HEAD>

ArcHydroの流域の最長流路がうまく動作せず、実行すると010429および010067のエラーが発生します。これを防ぐ方法をご存知の方はいらっしゃいますか？私はWindows 10上でArcGIS 10.6.1と最新バージョンのArcHydro（10.6.0.13）を使用しています。ArcHydroは初心者ですが、このツールの入力は多くないため、何が間違っているのか理解できません。こちらのいくつかの提案も試しましたが効果はありませんでした。添付は、私が現在取り組んでいるプロジェクトで区画した流域と流路線、および受け取ったエラーメッセージのスクリーンショットです。<\/P><\/BODY><\/HTML>

タグ付けされた投稿をもっと見る

Arc Hydro

Accepted answers

All comments

ThomasHollenhorst

I see that the Python tool for LFP for Adjoint Catchments also requires LFP for Catchments as input. Was this with a different version? Has the memory leak been addressed? I'm still getting an error like this.

Anonymous User

Were you able to solve this? I am getting the same error message repeatedly. Cannot get past this step.

Thanks

TysonBartlett

That doesn't work either. Longest Flow Path for Adjoint Catchments requires the output from Longest

Flow Path for Catchments, as seen below.

If I try to run Longest Flow Path for for Adjoint Catchments using the output I got from Longest Flow Path for Catchments or Drainage Lines, an error message pops up: "No corresponding flowpath found for catchments!". Is there a workaround I should be aware of to avoid this?

ChristineDartiguenave

Try to use the Python version of the Longest Flow Path for Adjoint Catchments tool under the Arc Hydro Tools Python toolbox. It skips the Longest Flow Path for Catchments step which is problematic for large rasters (memory leak). To support LFP for Watershed, you do not need the LFP for Catchments, only the LFP for Adjoint Catchments.

Christine Dartiguenave

Esri Water Resources Team

TysonBartlett

I went through all of those steps once again in order and still got stuck on Longest Flow Path for Catchments. In the image I posted I had the adjoint catchments turned by accident, which is why it looked like there were two centroids per catchment.

MarkBoucher

Looking at your watershed boundaries and points, it seems odd that there are two points in each watershed (polygon) as well as two drainage lines (blue polylines). If the points are centroids, then there is something wrong. The "two points inside each polygon" is so consistent, it makes me think that maybe you change the number of cells in the stream definition an didn't rerun some other part of the Basic Dendritic Terrain Processing functions

If the polygons are the catchment layer, then I'd check to make sure everything is correct at that step.

Flying in the blind here since I don't know everything about your project, but if you redo any step before the step you are one, you have to redo all the steps in between. There's a good chance you didn't do this, but maybe there is something is a process before the longest flow path routine that is not finishing.

I've inserted a screen capture and highlighted just the steps I use. They have to be done in order and if you re-do any step, you must redo all the following steps.

Heading out of town with limited ability to follow this. Hope you figure it out!

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.