| Numéro d’ID de bogue |
BUG-000122561 |
| Envoi | May 23, 2019 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS Utility Network Management |
| Version trouvée | N/A |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 2016 64 Bit |
| Statut | Will Not Be Addressed
L’équipe de développement a examiné le problème ou la demande et a décidé qu’ils ne seraient pas traités. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
The polygon used internally is actually buffered a bit around the original service territory on purpose. You can see this by adding your service territory to a client server map with your utility network and then disable the network topology. You will see a purple dirty area feature displayed that is representing what the utility network is using, which again is a buffer around the original input feature(s). The original intent of this is purely for calculating an extent that our network index needs to be prepared to work with, it wasn't for stopping editing really. If one were to have multiple polygons inside that service territory class, the utility network just creates a bounding box around all polygons, then also adds a buffer. So not only do you have the buffer, but you could also edit in-between the polygons. So all of that said, the real solution to stop users from editing outside of you polygon (or polygons) in the service territory is via Attribute Rules. You can create an attribute rule on the classes to ensure that features created fall within one of the polygons that you consider to be the service territory. To do that though, you will need to move up to the 10.7 server. Link to attribute rules info: https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/attribute-rule-script-expression.htm
Étapes pour reproduire
ID de bogue: BUG-000122561
Logiciel:
- ArcGIS Utility Network Management