hanbyul-here
commented
2 years ago As far as I remember, Cesium's whole elevator pitch was about 'real 3d', not extracting 2d geometries. I think it expects whole different data format, I am not sure we can render tiles from titiler in Cesium? (I have zero hands-on experience with Cesium, so please correct me if I am wrong!)
Daniel already explained about the decision to use MapboxGL well but since I often think about my faith about using MapboxGL... leaving my thoughts here.
- I am not a big fan of MapboxGL, but it is undeniable that MapboxGL is one of very few rendering engines that has active development going on, like if there is a bug, we can expect that it is going to be fixed soonish.
- It has enough documentation/resource so even if a new developer without much geospatial knowledge comes, I won't worry about them figuring out how to use it. (which I think important for a long term project like VEDA)
- Using a map engine with modern UI framework (React, in our case) is sometimes tricky because each of them wants to control elements in its own ways. I am not sure MapboxGL is inherently better at being used with React, but Development Seed has accumulated institutional knowledge about it, and there are a lot of users out there who are trying to figure out similar problems.
I think it is cool that NASA is looking to use more open source libraries. I think finding alternative will likely require investing a lot more of our resource (onboarding developers, bug fix, figuring out how to use it with UI framework...) in that alternative.
nerik
In response to the question "Why Mapbox?" @danielfdsilva helped provide the following explanation:
TL;DR:
At the beginning of the project we looked at what was out there to understand if there was an alternative to mapbox (https://github.com/NASA-IMPACT/covid-dashboard/issues/557).
We were looking to have different types of projections while supporting vector layers and data-driven styling.
Because we were looking for vector layer support, mapbox was a strong choice and no other library is as powerful at doing data-driven styling.
Initially it lacked projections support, but then they added them - and globe projection is coming along.
This, tied with our extensive knowledge of mapbox, and close relationship made it an easy sell.
Now, looking at what we are working with right now, it seems that vector layers are not really needed - I’m actually not sure about this, but all our conversations seem to refer to tiled datasets.
This seemingly tiny change, means we could reassess and go with a different library.
It sounds like we may consider moving to another mapping client. From what I understand there are some deal-breaker requirements (and probably some that I am missing):
What are some other important features we need to consider in alternatives? @danielfdsilva also mentioned data-driven styling for example.
Is [CesiumJS]()https://cesium.com/platform/cesiumjs) worth exploring as well?