Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Layers not visible in globe projection with initial zoom > 6 #1930

Closed
TheKeenestKeen opened this issue Jul 25, 2022 · 3 comments · Fixed by #2229
Closed

[Bug] Layers not visible in globe projection with initial zoom > 6 #1930

TheKeenestKeen opened this issue Jul 25, 2022 · 3 comments · Fixed by #2229
Labels

Comments

@TheKeenestKeen
Copy link

TheKeenestKeen commented Jul 25, 2022

Description

Initial zoom greater than 6 does not show layers unless we zoom out and then back in when using the globe projection

Expected Behavior

Layers rendered

Steps to Reproduce

https://codesandbox.io/s/eloquent-curran-369y7k

Environment

  • Framework version:"7.0.18"
  • Map library:"^2.9.2"
  • Browser:Chrome
  • OS:macOS 12.3.1

Logs

No response

@Pessimistress Pessimistress changed the title [Bug] [Bug] Layers not visible in globe projection with initial zoom > 6 Jul 25, 2022
@maheshgudisa
Copy link

Hey, you should specify layer id's that you want to interact in interactiveLayerIds paramerter in the Map component like this <Map interactiveLayerIds=[layer1.id, layer2.id]>

@pierceglennie
Copy link

I have this same issue with layers not appearing when the globe projection is used and initial zoom is greater than 6. @maheshgudisa suggested solution does not fix it – here's the same sandbox with that applied:

https://codesandbox.io/embed/blue-voice-nfpmp0?fontsize=14&hidenavigation=1&theme=dark

The layers work correctly if the globe projection line is commented out.

@Pessimistress
Copy link
Collaborator

Fixed in v7.1.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants