| Numéro d’ID de bogue |
BUG-000134868 |
| Envoi | October 24, 2020 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS Pro |
| Version trouvée | 2.6.2 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 10.0 64 Bit |
| 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
The behaviors described here are as designed.
When running the Add Locations tool for network analysis layers referencing a portal service (including ArcGIS Online), the points are appended to the sublayer and the location fields are not calculated. The location fields are only calculated during the solve time because the data is sent to the server to be processed once.
As a result, it is correct that the SourceID, SourceOID, PosAlong, SnapX, SnapY, SnapZ, and DistanceToNetworkInMeters fields are not populated for service-referencing layers until after solving it.
For the same reason, the Snap to Network option does not apply to service-referencing layers. This option is hidden from the Add Locations tool UI for these layers in ArcGIS Pro 2.7, and the documentation is updated. This option should be hidden for service-referencing layers. This is because it is not possible to snap inputs to the network for service-referencing layers, and the DistanceToNetworkInMeters field to be populated generally with non-zero values.
The issue mentions that the SourceID value is 1 for all points in the service-referencing layer. That is also correct, as the points are located on the underlying network's only edge source, which has an ID of 1.
Étapes pour reproduire
ID de bogue: BUG-000134868
Logiciel: