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

Mesure de la zone sale d'utilisation

DamienPyne

<\/HEAD>

À partir des images relatives au Utility Network - Zone Sale des entités ponctuelles, quelle unité de mesure est utilisée avec la distance tampon pour créer les polygones ?<\/P>

Il semble que la distance tampon soit toujours de 0,5, donc le diamètre\/périmètre est de 1 et l'unité de mesure est basée sur le système de coordonnées de référence du service\/source de données du utility network.<\/P>

<\/P>

Dans les données de démonstration de Naperville, le système de coordonnées de référence des données\/service est projeté en pieds (NAD 1983 StatePlane Illinois East FIPS 1201) et la zone sale résultante a un périmètre de 1 pied.<\/P>

<\/P>

Nous avons développé une preuve de concept avec des données en Geocentric Datum Australia 2020 (GDA2020) qui est géographique en degrés décimaux. 1 degré en distance correspond à environ 101-111 km selon qu'il s'agit de la latitude ou de la longitude. Comme vous pouvez le voir, la distance du périmètre est d'environ 100-110 km, ce qui est une méthodologie cohérente avec l'exemple d'1 pied avec les données de Naperville.<\/P>

<\/P>

De plus, peut-on confirmer que ce tampon résultant est passé à une fonction de boîte englobante minimale pour produire le rectangle car le tampon sur les points crée des cercles ?<\/P>

<\/P>

Paul LeBlanc<\/A> cela est-il lié au problème de projection mentionné dans Applying WaterDistribution_AssetPackage fails<\/A> ou lié à Apply Asset Package error - Get attribute metersPerUnit does not exist<\/A><\/P><\/BODY><\/HTML>

Trouver plus de publications taguées avec

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

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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