mapillary / mapillary/mapillary-js
Handle panoramas with orientations other than 1
Open
Nobody has claimed this yet.
affects-component
bug
- Dominant language
- TypeScript
- Stars
- 516
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
mapillary-js version: 1.7.2
Steps to Reproduce Behavior
- Navigate to a panorama with orientation other than 1
Expected Behavior
Image is oriented correctly.
Actual Behavior
Image is flipped incorrectly.
Additional Information
Orientation 6:
Q1v_6jbT4Rqh4_yqWMbnkQ
7glJ5x_FlzE0ZGiHs0-36Q
Orientation 8:
CaSZn95CyAskZQkclO_M1w (incorrect gpano information)
Orientation 1 for reference:
qZsQ-hLfxGFD3o8TxY8VIw
Not working:
nuhtysVeUP765GP6kSXOAg
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 reproducing the issue with the listed Orientation 6 and Orientation 8 panorama IDs, comparing them with the Orientation 1 reference. Trace how panorama metadata is read and applied during rendering, then verify that all listed orientations display correctly without flipping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100