Bogue
Added costs for global turns are ignored by scaled cost barriers.
| Numéro d’ID de bogue | BUG-000082445 |
|---|---|
| Envoi | October 10, 2014 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS for Desktop |
| Version trouvée | 10.2.2 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 7 |
| Statut | Known Limit |
Informations supplémentaires
There are various reasons why scaled cost barriers don’t apply to turns (this was actually by design). However, there is a very simple solution to their problem. Essentially, it appears they want global turn delays everywhere *except at a few choice intersections where they know that there are crosswalks/traffic-signals*. At those few choice intersections, they are currently willing to digitize barriers in an attempt to “scale down” the global-turn delays. A more appropriate solution would instead be to digitize explicit turns at those specific intersections, and directly assign them the desired (scaled-down) turn costs. Explicit turns always override global turns, so the global turns won’t be used at these intersections, but instead the explicit turns with the smaller desired costs will be used. This not only solves the problem, but will speed up their solves, as having to add in barriers slows things down considerably at solve time (barriers are really only intended to support ephemeral scenarios [e.g., temporary road closures or weather conditions], not permanent aspects of the network, such as this).Étapes pour reproduire
ID de bogue: BUG-000082445
Logiciel:
- ArcGIS for Desktop
Recevoir une notification lorsque le statut d’un bogue change
En savoir plus sur ce sujet
Rechercher des informations associées
Rechercher une formation sur ce sujet
Explorer des pistes et donner un avis
Obtenir de l’aide auprès des experts ArcGIS
Télécharger l’application Esri Support