![]() ![]() What are some example use cases for this feature? Users would not need their own Mapbox accounts, you could use one token from an ODK Mapbox account. And it would mean there are more folks at Mapbox who would be able to help!Īnother benefit of using the Android SDK is that each user will have their own ceiling of 6,000 tiles for offline caching (the ODK app will need to manage the tile cache). That would allow for vector maps and would benefit from our optimized offline caching. Rather than sinking time into a Mapbox raster option (which might be more complicated and not as good), it looks like the easiest thing to try would be adding the Mapbox Android SDK to ODK, alongside the other map options. We think vector tiles would also help with low-bandwidth and offline mapping scenarios. While OSM Droid (currently in ODK) does support Mapbox, it only supports raster tiles not vector tiles, which are faster and lighter to use and are what most mobile maps are moving to. I wanted to start a topic to let you know what we've been trying and invite discussion and feedback about whether and how to add this feature. A colleague of mine on the Mapbox mobile team has been volunteering his time to investigate what would be involved to do this Earlier this year I connected with about the possibility of integrating Mapbox basemaps (which are built largely with OpenStreetMap data) as an option within ODK. ODK Collect is a very common data collection tool among our partners. Hello everyone! I work at Mapbox on our Community team, which supports non-profits, researchers, and other positive impact projects to use our tools. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |