Baseflow / Baseflow/flutter-geolocator
[Feature Request]: Expose Location.hasBearingAccuracy() from Android platform
- Dominant language
- Dart
- Stars
- 1.3k
- Forks
- 803
- Avg merge
- 8h 16m
- Merged PRs (30d)
- 1
Description
### Is there already an issue requesting this feature?
- [X] I have searched the [existing issues](https://github.com/baseflow/flutter-geolocator/issues).
### Please select affected platform(s)
- [X] Android
- [ ] iOS
- [ ] Linux
- [ ] macOS
- [ ] Web
- [ ] Windows
### Use case
It would be nice to have the Android `Location.hasBearingAccuracy()` call exposed to Flutter, as we were filtering out inaccurate heading readings using `Position.headingAccuracy`, but on some devices this always = 0.0 if `Location.hasBearingAccuracy()` returns `false`, so on those devices, we're throwing away all readings.
### Proposal
An extra field in `geolocator_platform_interface-4.2.2/lib/src/models/position.dart` to flag whether the device has bearing/heading accuracy available.
### Specific requirements or considerations
_No response_
### Additional information or context
_No response_
Contributor guide
Research direction
Start in geolocator_platform_interface-4.2.2/lib/src/models/position.dart and trace how Android Location data reaches the Flutter Position model. Check the Android platform entry point for Location.hasBearingAccuracy(); done means Flutter exposes whether bearing or heading accuracy is available, including the relevant platform data flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100