feat: add per-marker elevation override - #113
Open
TomPlanche wants to merge 2 commits into
Open
Conversation
|
@TomPlanche is attempting to deploy a commit to the shu Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds the ability to specify a custom elevation for each marker on the globe. When a marker doesn't have a custom elevation specified, it will fall back to the global
markerElevationsetting.Example Usage:
markers: [ // Uses the global markerElevation { location: [37.7595, -122.4367], size: 0.03 }, // Uses a custom elevation { location: [51.5074, -0.1278], size: 0.05, elevation: 0.15 }, ]