mapbox / mapbox/mapbox-maps-flutter
User location Tracking methods as found in 'mapbox_gl'
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 380
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am porting my Flutter app from 'mapbox_gl' to this official library day by day and found that there is no similar implementation of Tracking modes as found in 'mapbox_gl'. I am not talking about location tracking as I am using geolocation and other libraries for that, but basically in-built tracking and displaying the user's location puck on the map in different ways, such as by compass (keeps up the location bearing).
'mapbox_gl' handles this very well and comes in very handy for great UX. I believe this feature will be useful for many, and I am open to contributing to this if someone can point me in the right direction as I am a bit new to hard-code Dart & Flutter programming.
For now, I am working on implementing this locally but not sure if it would be well worth the time and may keep my keep my app on 'mapbox_gl' for longer.
Reference from 'mapbox_gl':
/// The camera mode, which determines how the map camera will track the rendered location.
enum MyLocationTrackingMode {
None,
Tracking,
TrackingCompass,
TrackingGPS,
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the official Flutter library's camera and location-puck APIs with mapbox_gl's MyLocationTrackingMode enum. Determine how None, Tracking, TrackingCompass, and TrackingGPS should map to this library, then verify that each mode provides the requested camera behavior and user-location display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100