Same acceleration bug with Firefox under Linux that makes me hates Mapbox GL with passion ... Makes quite a lot of website unbearably unusable ...
Would you please provide a way for the user to deactivate that terrible idea ? Thanks.
Maplibre: community-driven Mapbox GL fork
51–60 of 87 posts
Re: Maplibre: community-driven Mapbox GL fork
#52[deleted]
Re: Maplibre: community-driven Mapbox GL fork
#53Earlier quoted context omitted.
The site mentions "additional functionality" vs. Mapbox Native. Is that additional functionality listed somewhere? (Apologies if it is and I missed it)
Metal support (coming soon) and MBTiles support (released AFAIK) are two things I know of, but I defer to the Releases page for specifics beyond that: https://github.com/maplibre/maplibre-gl-native/releases .
Thanks!
Re: Maplibre: community-driven Mapbox GL fork
#54Earlier quoted context omitted.
Yeah, the bit about the developer of Leaflet is accurate. One thing I'd expand on: the first iteration of web mapping was all built on raster maps, where the map was rendered in advance, server-side, and a simple client downloaded tiles to the client to build a slippy map. Leaflet was an open source library that did that task well. The commercial players have mostly abandoned this approach, though, in favor of techno…
Isn't it the case that pre-rendered tiles are more performant for the mobile user? Continously rendering the tiles on a smartphone is draining more battery? I would guess?
It's true that raster tiles are easier to draw, but CPU/GPU is rarely the limit for performance even on (modern) mobile devices, network access then disk access then memory usage is. And using the network is one of the largest sources of power use. Vector tiles are smaller downloads, therefore they are more performant.
Wall time CPU profiling is just not that useful anymore and yet it's the only thing most people ever think about for some reason.
Re: Maplibre: community-driven Mapbox GL fork
#55Same acceleration bug with Firefox under Linux that makes me hates Mapbox GL with passion ... Makes quite a lot of website unbearably unusable ... Would you please provide a way for the user to deactivate that terrible idea ? Thanks.
Can you please report this on our issue queue? From a cursory search, it doesn't look like anyone complained about scroll zoom on Firefox under Linux before. We'd be happy to fix this after hearing more details. https://github.com/mapbox/mapbox-gl-js/issues
Re: Maplibre: community-driven Mapbox GL fork
#56I'm one of the folks behind the fork (and part of the initial steering committee). Happy to answer any questions!
I've struggled to understand the relationship between Mapbox, Mapbox Studio, Mapbox GL, OpenStreetMap, and other libraries like OpenLayers or Leaflet. Could you please explain (in brief) the mapping "ecosystem" as it were, and where Maplibre fits into the picture?
Leaflet - developed to work with PNG image map tiles
Mapbox GL/Maplibre - works with vector tiles which are similar in format to an SVG
I believe this plugin[1] is a hybrid approach which allows Leaflet to load vector tiles on a plain 2D map with no map tilt or rotation
Re: Maplibre: community-driven Mapbox GL fork
#57Earlier quoted context omitted.
Im curious as to integration with DeckGL which seems to be the emerging standard for 3d maps and also for interactivity. Do you know if maplibre will work the same with it as mapboxgl does?
I'm not sure as to specifics (as I haven't tried this), but if DeckGL worked with 1.x Mapbox GL JS, it should just work with MapLibre, with a few potential minor adjustments (e.g., nomenclature). Can't promise it though.
I can verify this: I upgraded my Deck.gl project from MapBox to MapLibre recently, and it was a simple matter of renaming some imports.
This works absolutely seamlessly.
I'm using Vue instead of the React integration and that's also working without any issues.
Re: Maplibre: community-driven Mapbox GL fork
#58This needs really solid Metal support or it won't be adopted on mobile.
Re: Maplibre: community-driven Mapbox GL fork
#59Earlier quoted context omitted.
I've struggled to understand the relationship between Mapbox, Mapbox Studio, Mapbox GL, OpenStreetMap, and other libraries like OpenLayers or Leaflet. Could you please explain (in brief) the mapping "ecosystem" as it were, and where Maplibre fits into the picture?
A big difference moving from OpenLayers and Leaflet to MapLibre GL is that you can use vector tiles and style them in the browser as opposed to rendering PNG files on the server. Converting OpenStreetMap to vector tiles is implemented by OpenMapTiles and they also have some open map styles.
no, openlayers supports vector tiles out-of-the-box and leaflet with a plugin
Re: Maplibre: community-driven Mapbox GL fork
#60Earlier quoted context omitted.
I've struggled to understand the relationship between Mapbox, Mapbox Studio, Mapbox GL, OpenStreetMap, and other libraries like OpenLayers or Leaflet. Could you please explain (in brief) the mapping "ecosystem" as it were, and where Maplibre fits into the picture?
Good question! There's a lot of Map s and it's very unclear how they all fit together without prior experience. OpenStreetMap (OSM) is a community-driven, fully open and usable data library. It has usable data for almost the entire world for everything from cities, roads, houses, parks, country borders, and work. It's a database of everything you need to make map. They also have a website that renders that map, but i…
Leaflet started because openlayers was very clunky. But since the major rewrite of openlayers v3 it's become a great choice and the author of leaflet has stated here on hackernews hat it's probably what you should use these days