Numéro d’ID de bogue |
BUG-000088776 |
Envoi | June 30, 2015 |
Dernière modification | June 5, 2024 |
S’applique à | ArcGIS for Desktop |
Version trouvée | 10.1 |
Statut | Known Limit
Après examen par l’équipe de développement, il a été déterminé que ce problème est lié à une limitation connue du logiciel sur laquelle Esri n’a aucun contrôle. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
As designed. The network analyst window listens to feature modified events for feature classes in network layers and maintains the sequence IDs within a group name. Sequence IDs start from 1, and are contiguious with no duplicates. As we calculate the field route name field on a per feature basis we listen to the feature modified event and assign a sequence value.
What is happening is that the logic that updates sequence values sees a new route name being created and so it assigns a new sequence value to it. The first row with a changed route name gets a sequence value of 1, the second 2, etc without regard to the pre existing stop sequence. The order in which features have their route name field calculated determines the order of the sequence ID created. In this case it happens that the first row with an updated route name and a newly created sequence of 1 is the last row which had a sequence of 4.
Solution de contournement
- Include a routename when initially loading in the stops.
- Solve using route optimization and sequence is recalculated.
Étapes pour reproduire
ID de bogue: BUG-000088776
Logiciel: