131–140 of 200 posts
This is going to fracture the fledgling community building on mapbox-gl-js - I expect we'll see a divergent BSD version as a result. I regret building out on mapbox-gl-js rather than leaflet...
Earlier quoted context omitted.
An incredible ironic statement since what you’ve done is only possible because of open source. If you don’t realize that taking a huge dump on the open source community will have profound consequences for Mapbox then you’re in for a surprise.
It won't make much difference. The damage is done, Mapbox has remade the community in its image and we can only live in that world.
Earlier quoted context omitted.
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.
I thought one of the primary features of Leaflet was its modularity. Would built-in vector tile support be an anti-pattern?
What a shame. I guess they got sick of people taking their code and ripping out their API subscriptions. For anyone interested in an open source mapping library (that also has 3D support) that can handle raster data (including the Mapbox tiles), I launched a project 2 weeks ago that is the culmination of 7 years effort: https://github.com/felixpalmer/procedural-gl-js/ . I must say (while acknowledging my huge bias) t…
What other alternatives exist? I know now: * openlayers, but vector tiles have no web GL support there * Procedural GL JS * tangram * deck.gl (from Uber) * harp.gl (from HERE Maps)
I'm keen on industrial archaeology and it's really helpful to have 3D visualisations of sites like old quarries.
Stand-alone 3D models can be done like [1] and the detail is substantially better compared to the map 3D views [2] (pits are pits again!) but I want to embed these into a website and start overlaying other data - just like I can with Mapbox maps.
1. https://sketchfab.com/3d-models/dinorwic-snakes-ladders-and-...
2. https://felixpalmer.github.io/procedural-gl-js/, search for Llanberis
Earlier quoted context omitted.
An incredible ironic statement since what you’ve done is only possible because of open source. If you don’t realize that taking a huge dump on the open source community will have profound consequences for Mapbox then you’re in for a surprise.
It won't make much difference. The damage is done, Mapbox has remade the community in its image and we can only live in that world.
Earlier quoted context omitted.
Founder, Stadia Maps here. We're looking into this, as well as trying to build consensus with the other map vendors on how to approach it. If you're a vendor and what to be part of it, email me (luke at stadiamaps.com).
Glad to see this. I’m a long time mapbox gl js user for https://onthegomap.com which costs $300-400 per month for running my own graphhopper routing servers and Stadia Maps tile hosting. It would cost over $3000 per month to upgrade to 2.0 and I have no need for 3D. I also use mapbox gl js for visualizing large datasets locally (precomoute vector tiles from non-geographic datasets), which doesn’t seems like it needs…
We 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…
We wrote and maintain the open-source Pelias geocoder(https://github.com/pelias/pelias) at Mapzen and have been continuing to improve it in the 3 years since Mapzen's shutdown.
Geocode Earth is our hosted service built around Pelias so you can get started quickly, not worry about keeping data up to date, or doing all the fine tuning and optimization that we've had to do to get fast and reasonably accurate autocomplete outside of Google and Mapbox.
Using our hosted comparison tool you can see that we do a pretty decent job of finding two out of 3 of the Chipotles (the third might have been deduplicated or not in OSM): https://pelias.github.io/compare/#/v1/autocomplete?text=Chip...
Most our users end up passing a focus point, in which case the results are generally even better, although they're the same in this example https://pelias.github.io/compare/#/v1/autocomplete?focus.poi...
Earlier quoted context omitted.
I won't get into all the context, but I think we should consider whether a community without contributors is a community. GL JS never had major active contributors outside of the company, and there are no self-funded webgl experts with lots of time who are ready to maintain a fork. OSS, we hoped, was about enabling people and unlocking people's ability to collaborate. It turns out that in 2020, it's mostly helping co…
Oh come on Tom. Making a great, free toolkit utterly decimated the competition. Just completely destroyed any funding for a competitor. And I should know. I believe that you believe this is well intentioned, but it had a very negative impact on open source geospatial software development. Again, I SHOULD KNOW. Mapbox is doing what is good for Mapbox. It's a company. But let's not pretend this change is good for anyon…
Earlier quoted context omitted.
I won't get into all the context, but I think we should consider whether a community without contributors is a community. GL JS never had major active contributors outside of the company, and there are no self-funded webgl experts with lots of time who are ready to maintain a fork. OSS, we hoped, was about enabling people and unlocking people's ability to collaborate. It turns out that in 2020, it's mostly helping co…
I don't understand your last paragraph. On the one hand you're saying OSS in 2020 mostly helps companies, but on the other hand you say this dynamic of company-helping is not one that you can build a sustainable business on. Am I missing something?