| Numéro d’ID de bogue |
BUG-000110589 |
| Envoi | January 4, 2018 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS Runtime SDK |
| Version trouvée | 100.1.0 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 10.0 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 reason Collector for Windows is reporting the Course and Speed values is it is a UWP app and is using the Windows 10 Windows.Devices.Geolocation.Geolocator API. By contrast, the ArcGIS Runtime WPF API uses the .NET Framework System.Device.Location.GeoCoordinateWatcher API. There appears to be an underlying issue in System.Device.Location.GeoCoordinateWatcher, which means that the values set is not visible. There are a few reasons for this, such as issues related to driver or a Windows / .NET Framework.
You will be able to reproduce this outside of the ArcGIS Runtime by extending the sample for GeoCoordinateWatcher to report Course and Speed values: https://msdn.microsoft.com/en-us/library/system.device.location.geocoordinatewatcher(v=vs.110).aspx.
Workarounds:
The Windows 10 API will report the values. To retrieve these values in your custom application you have two options:
#1. Use the NMEA feed from the GPS instead of using the Windows location service (for an example see https://github.com/dotMorten/NmeaParser/tree/ArcGISLocationProvider). Depending on your requirements, we would typically recommend this approach due to the extra information you can obtain regarding the quality of the position. This is the preferred approach for Collector.
#2. Use the Windows 10 API (within the existing WPF application). For more information on accessing Windows 10 APIs from within WPF projects see https://blogs.windows.com/buildingapps/2017/01/25/calling-windows-10-apis-desktop-application. Having referenced the assembly and winmd, you can use the newer API for updates e.g.
```
Geolocator locator = new Windows.Devices.Geolocation.Geolocator();
…
locator.PositionChanged += Locator_PositionChanged;
…
private void Locator_PositionChanged(Windows.Devices.Geolocation.Geolocator sender, Windows.Devices.Geolocation.PositionChangedEventArgs args)
{
var position = args.Position;
var heading = position.Coordinate.Heading;
var speed = position.Coordinate.Speed;
Debug.WriteLine("Heading: " + heading);
Debug.WriteLine("Velocity: " + speed);
});
}
```
Étapes pour reproduire
ID de bogue: BUG-000110589
Logiciel: