Will bug fixes for Mapbox GL JS 2.x be backported to 1.x (by the Mapbox team)?
Mapbox-gl-js is no longer under the 3-Clause BSD license
81–90 of 200 posts
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#82Earlier quoted context omitted.
Are you sure? Deck.gl depends on react-map-gl [0] which depends on mapbox-gl [1] 0. https://github.com/visgl/deck.gl/blob/79699960e7e24daef11074... 1. https://github.com/visgl/react-map-gl/blob/aae80369ed106f5c6...
Yes, I'm a maintainer of deck.gl. That's a development dependency, not a runtime dependency. You have the option of using deck.gl completely standalone [0], or integrations are provided for Google Maps and Mapbox GL JS [1] [0]: https://deck.gl/examples/tile-layer/ [1]: https://deck.gl/docs/get-started/using-with-map
Cool, thanks for the clarification!
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#83Earlier quoted context omitted.
Openlayers has some prototype webgl support that's a bit promising. I enjoyed working with it (but hate working with buggy webgl in general). Leaflet is also great. If you're doing any sort of front end GIS I recommend openlayers above all else including mapbox. But I suspect 99% of users just need basic maps. Leaflet is great for that.
Openlayers has web GL support but not for vector tiles and I would like to have fast vector tiles :) They removed this support in some previous version, I think. Or do you have a link to a pull request or issue? (IMO Leaflet is dead now that the creator is working since several years for Mapbox)
7+ years to be exact. It's unfair to call Leaflet dead — it's still quite actively maintained, gets regular releases and has a huge community of both users and contributors, and Mapbox have always been supportive of me spending time on it during work hours.
What someone can see as less development activity is simply a sign of a mature product that doesn't need many new features and changes to remain useful — focusing on the core basic mapping needs has always been its goal, and it continues to adhere to it.
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#84This follows the same happening for Mapbox GL Native (iOS/Android) earlier this year. With Native it's more critical. A GL JS fork can continue quite easily. The iOS Native library, however, uses OpenGL and will therefore stop working when Apple finally switches to Metal-only. (Mapbox only released their Metal port under the new proprietary TOS.)
Can you point to where/when this happened for their native code? As far as I can tell, that's still licensed under 2-clause BSD ( https://github.com/mapbox/mapbox-gl-native/blob/master/LICEN... )
Everything in that repo is 7+ months old. The main GL renderer is now closed-source: see https://github.com/mapbox/mapbox-gl-native-android/pull/450 .
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#85Earlier quoted context omitted.
Can you comment on how likely similar future license changes are for these libraries? Thanks a lot for your work in the mapping space btw.
I'd say extremely unlikely — it wouldn't make sense both technically (stable, mature, small, razor-focused libraries that are already open source) and business-wise. As far as I know as someone who worked here for 7+ years (take this as personal opinion), Mapbox wants to keep investing heavily in open source and open data sustainably and indefinitely, and this GL JS change is an unevitable prerequisite for that. This…
It is not only GL JS. If Mapbox wants to keep investing heavily in open source why is it that 3 bigger mapbox libraries have a commercial license after it was open source a while ago? (mapbox navigation android & mapbox GL Native)
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#86Will bug fixes for Mapbox GL JS 2.x be backported to 1.x (by the Mapbox team)?
From the Github issue: "Updates to the v1 releases will be made only for critical browser compatibility or security issues for a limited time."
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#87Earlier quoted context omitted.
Openlayers has web GL support but not for vector tiles and I would like to have fast vector tiles :) They removed this support in some previous version, I think. Or do you have a link to a pull request or issue? (IMO Leaflet is dead now that the creator is working since several years for Mapbox)
7+ years to be exact. It's unfair to call Leaflet dead — it's still quite actively maintained, gets regular releases and has a huge community of both users and contributors, and Mapbox have always been supportive of me spending time on it during work hours. What someone can see as less development activity is simply a sign of a mature product that doesn't need many new features and changes to remain useful — focusing…
Thanks for replying and all your amazing work :) !
What I see or meant as a sign of "dead" is that there will be no new features that Mapbox GL JS has but that are critical for future applications. Like proper or inbuilt vector tiles support.
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#88We tried to implement mapbox on a new product last week. I like the style options for the maps but their reverse geo lookup and local search performed poorly vs google maps. Pins dropped down the street from actual address and search results don't narrow in accurately using POI and city/state - for example "Chipotle Parker Colorado" rather than showing the 3 chipotles in Parker, CO lists: - the city "Parker, CO" - Pa…
afaik, Mapbox's geocoding service was never meant to provide the lng,lat of retail entities. Looking over their API docs, you can search for points of interest (POI), but that's it: https://docs.mapbox.com/api/search/geocoding/ For your use case, you should look into a geocoding service [0]. And then you can display the location results with your mapping library of choice. Google Maps does provide an all-inclusive se…
> The Mapbox Geocoding API does two things: forward geocoding and reverse geocoding. Forward geocoding converts location text into geographic coordinates, turning 2 Lincoln Memorial Circle NW into -77.050,38.889.
https://www.mapbox.com/place-search
I think "location text" is the part they are not parsing well.
The screenshots all over that page show someone entering a couple of letters and getting the resulting POI with address.
Unfortunately, we could not get reliable results using their web place search so maybe they just have better mobile sdks that are adding more filter data to the requests automatically ¯\_(ツ)_/¯
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#89Will bug fixes for Mapbox GL JS 2.x be backported to 1.x (by the Mapbox team)?
From the Github issue: "Updates to the v1 releases will be made only for critical browser compatibility or security issues for a limited time."
Right. Here is the link: https://github.com/mapbox/mapbox-gl-js/issues/10162
Re: Mapbox-gl-js is no longer under the 3-Clause BSD license
#90Could we change the title to more clearly reflect that this is a license change from a permissive to a restrictive licence? Maybe "Mapbox GL JS v2 no longer uses a permissive license"? I initially thought by the title that Mapbox had removed the library from GitHub completely.
What is this talk about "permissive" licenses? It was open source, it's not open source any more. The Open Source Definition: https://opensource.org/osd
EDIT: The title has now changed but it was "Mapbox GL JS is no longer open source", which is the point: they didn't change from an open source license to another.