Design better format for setting & getting map bounds
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
LngLatBounds can currently represent an axis-aligned rectangular bounding box. When the map is rotated or tilted this doesn't fit the current view exactly.
Should switch LngLatBounds to storing four locations so that it can represent skewed and rotated bounding boxes?
We could it make it backwards compatible by making the constructor accept only two points.
cc @mourner
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 reading the LngLatBounds implementation and its current constructor and accessors. Define how four locations would represent rotated or tilted views while preserving construction from two points; done when the API and compatibility behavior are specified and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100