-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Feat] MapboxLayer / MapboxOverlay integration with globe
projection
#7920
Comments
This would be amazing to have! |
We have some related issues, like visgl/react-map-gl#2091. We need mapbox to expose more of their camera parameters to pull this off. See more discussion in mapbox/mapbox-gl-js#12040. In particular:
Also, @Pessimistress accomplished this in |
Hello, can I learn the implementation code of the effect of your comment video |
Is the feature "MapboxLayer / MapboxOverlay integration with globe projection" planned for feture iterations ? |
Mapbox does not currently support custom layers in globe projection. We can't do anything until they expose sufficient API for us to implement integration. |
If I'm not mistaken it seems that it does support custom layers for globe projection with parameters for both the mercator and globe + the transition between them: What else is missing? |
maplibre-gl@5.0.0-pre.3 has released globe projection and custom layer related APIs. Do we have any plans? |
Target Use Case
In my organization we are required to use the Globe projection for our maps. Recently I stumbled upon the deck.gl library and would love to use it for the potential in additional 3D visualization it provides on top of mapbox.
However we quickly realized that although mapbox supports custom layers in globe view, the deck.gl layers don't update according to the projection which provides for some silly looking bugs like this one:
screen-capture.1.mp4
We'd love to contribute to the deck.gl library and get this behavior fixed, where should we look to begin with?
Proposal
The mapbox
globe
projection is an adaptive projection which gradually morphs from the 3d globe to a 2d mercator projection between zoom levels 6-8. Seeing as these are arbitrary numbers which could be changed in the future, the MapboxLayer / MapboxOverlay integration should always update its projection matrix (and any other dependent properties) by the current zoom projection so that it stays accurate. All points without height should also clamp to the spheroid, while datasources with height should be offset from the spheroid rather than the 2d plane in mercator projection.The text was updated successfully, but these errors were encountered: