mapillary / mapillary/mapillary_tools
Support new "heading" tag from osmand tracker plugin
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 315
- Forks
- 145
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 2
Description
Note that osmand now supports to track the heading in an "extension": (Needs to be explicitly enabled in the settings of the tracker plugin)
<trkpt lat="4X.XXXXXXX" lon="1X.XXXXXXX">
<ele>XXX.XXX</ele>
<time>2020-04-03T13:03:47Z</time>
<hdop>7.504</hdop>
<extensions>
<speed>1.24</speed>
<heading>233</heading>
</extensions>
</trkpt>
- Please support taking the direction from that.
- To correct for phone/camera alignment issues, it might be possible to use the (smoothened) direction from the "next" point as a comparison and filter accordingly. This might enable to correct e.g. a constant offset, if a separate camera is mounted in a fixed angle to the phone, and it might be able to detect if both do not fit at all and throw an error. Or it might correct for magnetic errors due to large metal objects (car). Maybe a kalman filter could be useful here.
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 reviewing the existing OsmAnd tracker-plugin handling and how direction is currently obtained. Confirm support for the value in the supplied example, then add coverage for that input and verify the resulting direction. Treat alignment correction and filtering as separate design questions, since the issue only proposes them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100