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

使用されるダーティエリアの測定

DamienPyne

<\/HEAD>

ユーティリティネットワークのポイントフィーチャのダーティエリアに関連する画像から、ポリゴンを作成するためのバッファ距離に使用される単位は何ですか？<\/P>

バッファ距離は常に0.5のように見えるので、直径／周囲距離は1であり、単位はユーティリティネットワークサービス／データソースの参照座標系に基づいています。<\/P>

<\/P>

ナパービルデモデータでは、データ／サービスの参照座標系はフィート単位の投影座標系（NAD 1983 StatePlane Illinois East FIPS 1201）であり、結果として得られるダーティエリアは周囲1フィートです。<\/P>

<\/P>

また、Geocentric Datum Australia 2020 (GDA2020) のデータでPoCを開発しました。これは小数度の地理座標系です。距離としての1度は緯度か経度によって約101〜111kmです。ご覧の通り、周囲距離は約100〜110kmであり、ナパービルデータの1フィートの例と一貫した方法論です。<\/P>

<\/P>

\u00A0<\/P>

また、この結果として得られたバッファが最小境界ボックス関数に渡されて長方形を生成していることを確認できますか？ポイント上のバッファは円を作成します。<\/P>

<\/P>

Paul LeBlanc<\/A> これは Applying WaterDistribution_AssetPackage fails<\/A> に記載された投影問題に関連していますか、それとも Apply Asset Package error - Get attribute metersPerUnit does not exist<\/A> に関連していますか？<\/P><\/BODY><\/HTML>

タグ付きの投稿をもっと見る

Accepted answers

PaulLeBlanc1

Those issues with the asset package were related to GCS. Regardless of how you create your UN, the default dirty area size is based on the units of the spatial reference of your feature dataset.

Roughly yes, it's buffering the point by half the defined unit of the spatial reference. There's some extra tolerance that's added, so it's bigger than the circle's MBR.

All comments

PaulLeBlanc1

Those issues with the asset package were related to GCS. Regardless of how you create your UN, the default dirty area size is based on the units of the spatial reference of your feature dataset.

Roughly yes, it's buffering the point by half the defined unit of the spatial reference. There's some extra tolerance that's added, so it's bigger than the circle's MBR.

DamienPyne

Thanks Paul. You stated the "the default dirty area size ...". Does this mean there is a configuration somewhere that can be updated?

PaulLeBlanc1

At this time there isn't a mechanism to update the default dirty area size.

WillBooth1

Hi Paul,

I have attempted to change the coordinate system of Naperville to Geographic (GDA2020) via "Change Asset Package Spatial Reference" and then re-appending all the network data, so everything including the Feature Layer is geographic. The Apply Asset Package through to Share Web Layer all went fine. The feature layer looks good too as far as having all the layers expected including Point/Line/Polygon Errors and Dirty areas. When I add this feature layer to ArcGIS Pro 2.4.2 I get all the layers except for Point/Line/Polygon Errors and Dirty areas although I can view the Dirty areas via a map service. Dirty areas are small, unlike the issue that Damian Pyne found where his map units were in degrees, so I am unsure how to replicate the issue where the default dirty area size is huge. The reason why I am going through this process is to upgrade and test ArcGIS Pro 2.5 beta, have you any idea what I may have missed regarding replicating this issue? When I upgrade is there a setting in ArcGIS Pro 2.5 beta where I can set the default dirty area size, if so where would I find it?

Thanks Will

Esri Australia Professional Services.

PS This is the enhancement I want to test in ArcGIS Pro 2.5 ENH-000123974 "Provide the ability to configure the dirty area buffer distance default calculation for a Utility Network"

WillBooth1

With ArcGIS Pro 2.5 there is a setting <MinimalDirtyAreaSize> in the enterprise geodatabase which allows the size of dirty areas around points to be set to a fraction of a coordinate system linear unit, at the moment I have only been able to set this via SQL. Following is the result of this having the value <MinimalDirtyAreaSize>0.01</MinimalDirtyAreaSize> (dirty area size 0.01 degrees square around an edited point).

AnthonyRyanEQL

Will,

Is there any limit on how far the scale can be? In your example of 0.01 decimal degree, this would be approx. 1 sq kilometre. I would be thinking of 1 sq metre (similar to 1 sq feet in Naperville demo data) so the factor would need to be around 0.00001. Good work on the testing so far.

Thanks

WillBooth1

Hi Anthony,

Here is the result from <MinimalDirtyAreaSize>0.00001</MinimalDirtyAreaSize>

dirty area size 0.00001 degrees square around an edited point

Cheers

Will

AnthonyRyanEQL

Will,

Thank you for testing this. We just need the MBR geometry changed to a buffer geometry and everything will be great

会話に参加する

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

クイックリンク

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