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; } } }

ArchydroproのPoint Delineatorツール

KevinUrbanczyk

私はArcGIS Pro 3.2.0とArc Hydro Tools Proを使用しています。流域モデルのために、流向とストリームラスター、およびDrainage Line、Catchment、Adjoint Catchmentのベクターを作成しました。フローパスに沿った複数のポイントがフィーチャクラスに保存されており、それぞれのポイントの流域を計算する自動化ツールが必要です。"point delineator"ツールは、モデルビルダーで"iterate feature selection"をフローパスポイントに対して実行すると非常にうまく機能します。これは他に何もないプロジェクトで実行されます（point delineatorツール用にfdr.tif、str.tif、drainage line、catchment、adj catchmentレイヤーを追加します）。問題は、同じモデルを多数のpythonノートブックや他のモデルビルダーモデルがあるArcProプロジェクトに入れると、「invalid extent」というエラーメッセージが表示されることです： ERROR 010568:<\/U> 無効な範囲です。長さまたは幅がゼロであるか、出力空間参照への範囲投影に失敗していないか確認してください。Watershedの実行に失敗しました。 , ('line 1011', 'c:\\program files\\arcgis\\pro\\Resources\\ArcToolbox\\Scripts\\ArcHydro\\pointdelineator.py', 'IndexError: tuple index out of range'). なぜ単純なプロジェクトでは実行できるのに、他の複雑なプロジェクトでは失敗するのか理解できません。<\/SPAN><\/P>

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

Arc Hydro

Accepted answers

MarkBoucher

Kevin,

I think the error regarding extent simply means that the processing extent is invalid. It could be that whatever extent you had defined (or defaulted to) in the simple model was OK, but something in the more complex model has changed the processing extent.

I'm not quite yet using Pro, but I assume the concepts are the same as in Deskstop.

I was once working on a project using Batch Point processing and it would run but the results would be cut off in a rectangle that I eventually realized happened to be the same as the extent of my Batch Point dataset. I think this was a bug in Arc Hydro where it would reset the processing extent to match the Batch Points (or when it reset the extent based on the layers involved it only used the Batch Points). My solution was to set the processing extent in Model Builder to be that of a "mask" layer that I used to extact the limits of the DEM I was using (to reduce memory requirements).

Additionally, in the Desktop version of Arc Hydro, there is the Batch Point option. When you create Batch Points you can run Batch Point processing. This likely does exactly what your model iteration does, but since it is w/in the Arc Hydro set of tools possibly it could reduce errors or "pass-on-ability" of your work (the next person won't have to decipher your "code").

Hope this helps,

Mark

All comments

DeanDjokic

Kevin,

i suggest you look into "Watershed Delineation" tool in Arc Hydro (same toolset as Point Delineator). that tool is designed to do batch delineation and has a bit more options on snapping (if you need it). this way you do not have to write your own "looper".

also, please review the "Arc Hydro - Project Development Best Practices" document. might save you some grief - e.g. spatial reference issues, data used in analysis being in the same feature dataset, HydroID assignment, ....

Dean

KevinUrbanczyk

Good advice. I think it was a coordinate system mismatch. I reset the coordinate system of the data frame to match the data (should have done that at the beginning) and it seems to be working now. Thanks for the help.

MarkBoucher

Kevin,

I'm not quite yet using Pro, but I assume the concepts are the same as in Deskstop.

Hope this helps,

Mark

会話に参加する

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

クイックリンク

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