### Change list - Ensure that the default value of `Map.basemap` is `MaplibreBasemap` if no value of `basemap` was passed. Add a test for this. - Define various View classes to map to deck.gl views. - Define View models on the TS side. - When a GlobeView is passed, pass `projection="globe"` to Maplibre - Render a dark background on the canvas when in globe view - Add `views` parameter to `Map`. For now this only supports a single view instance, but hopefully in the future it'll support more. This PR also sets the stage for non-geospatial map rendering and for multi-view support. ### todo: - [ ] Should we name the Map attribute `view` instead of `views`? Hopefully soon we'll support multi-views, though maybe not with a maplibre basemap. (#965 ) - [ ] View state validation (#948) - [ ] add something like `projection="globe"` to `viz` (#949) With this PR, to generate a map with globe view, someone would call ```py from lonboard import Map from lonboard.view import GlobeView from lonboard.basemap import MaplibreBasemap lonboard.Map( layer, views=GlobeView(), basemap=MaplibreBasemap(mode="interleaved"), ) ``` ## Globe view: <img width="787" height="685" alt="image" src="https://github.com/user-attachments/assets/7a22fafd-d48c-4cc3-b5f0-8d4393dcb035" /> Closes #886 (globe view), closes #375 (orthographic view) (though might need more work to allow non-spatial data) Relates to - #905 (multi-views), - #718 (multi-view), - #658 (repeating map view), - #637 (multiple linked plots), - #494 (basemap refactor), - #404 (swipe between two maps), - #375 (orthographic view)

Should we name the Map attribute view instead of views? #965

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions