Dynamic bounding box when supplied a coordinate

Open
#23 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift

Research direction

The issue names no files or tests; start by locating TerrainNode and reviewing the linked feature-querying documentation. Define how queried feature types map to bounding-box sizes, then verify that TerrainNode(lat:lon:) produces the intended bounds for city and natural-park features.

Written by the indexing model from the issue text.

Description

enhancement

I thought this would be a really interesting feature if possible. Create a new initializer TerrainNode(lat: , lon: ) that would take a coordinate and dynamically calculate the bounding box for you. It would use feature querying to check and see if the coordinate was a place in the city, natural park, etc. If it was in the city, the user is likely looking at a couple buildings and therefore the bounding box should presumably be small. However, if the feature is like a natural park they are likely looking at terrain and would want an understandably bigger bounding box.

It's a very preliminary idea but it would be very interesting if it could be implemented. I've noticed myself that different types of features require different bounding box sizes.

Dominant language
Swift
Stars
232
Forks
51
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/mapbox-scenekit

All issues in mapbox/mapbox-scenekit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.