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

Meten van vuile gebieden in gebruik

DamienPyne

<\/HEAD>

Uit de afbeeldingen met betrekking tot het Utility Network - Vuile Gebied van puntkenmerken, welke meeteenheid wordt gebruikt bij de bufferafstand om de polygonen te creëren? <\/P>

Het lijkt erop dat de bufferafstand altijd 0,5 is, dus de diameter\/omtrek afstand is 1 en de meeteenheid is gebaseerd op het referentiecoördinatensysteem van de utility network service\/datasource.<\/P>

<\/P>

In de Naperville Demo-gegevens is het referentiecoördinatensysteem van de data\/service geprojecteerd in feet (NAD 1983 StatePlane Illinois East FIPS 1201) en het resulterende vuile gebied is 1 voet omtrek.<\/P>

<\/P>

We hebben een PoC ontwikkeld met gegevens in Geocentric Datum Australia 2020 (GDA2020) wat geografisch is in decimale graden. 1 graad afstand is ongeveer 101-111 km afhankelijk of het betrekking heeft op breedtegraad of lengtegraad. Zoals je kunt zien, is de omtrekafstand ongeveer 100-110 km wat een consistente methode is met het voorbeeld van 1 voet met de Naperville-gegevens.<\/P>

<\/P>

Kan ook worden bevestigd dat deze resulterende buffer wordt doorgegeven aan een minimum begrenzingsvakfunctie om het rechthoek te produceren aangezien de buffer op punten cirkels creëert? <\/P>

<\/P>

Paul LeBlanc<\/A> heeft dit te maken met het projectieprobleem genoemd in Applying WaterDistribution_AssetPackage fails<\/A> of gerelateerd aan Apply Asset Package error - Get attribute metersPerUnit does not exist<\/A><\/P><\/BODY><\/HTML>

Vind meer berichten getagd met

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

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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