How long does it take for an edit to propagate from OSM to Mapbox's tiles? Average/worst case. I know this is a tough problem, so I don't envy you. :-)
Well, they probably have some kind of tile "lint", need to precompute a bunch of routing data (depending on what their actual algorithm is), sync all their rendering/prerendering pipelines at a common revision, propagate outputs to cache servers, etc. So it can't easily be done at every change, unless they have a design where small incremental deltas are explicitly supported by all their services. It is a time- and resource-intensive process. Still, three months sounds like a lot.
The concern seems to be moderation (but they haven't made a clear statement about it either). The current pace of updates is slower than what they were doing a year ago, so it probably isn't a technical thing.
Their routing engine updates more frequently than the rendering data.
OSM sub-10 minute updates really depends on zoom level and data. With low zooms the update can take weeks even there, as I recently learned in a hard way. It is more important to have consistent and laundered map data than someone's last minute changes.
What kind of places details are you looking for?
Depending on the geographic region, Mapbox has data for regions, cities, addresses, zipcodes, and points-of-interest (POI).
We expanded our team and are working on improvements to React Native SDK, which was initially a side project from one of our engineers. We’re excited to support the library and get it to feature parity with our native iOS, Android, and Qt SDKs.
Disclaimer: I work with the mobile team at Mapbox.
We did. By a lot. A few months ago we implemented a new hibernation mode that suspends location services more aggressively when you're not active. This saves about 50-90% battery on an average day. The only downside of this approach is that we can't show the first 100-200m on a map when you start moving again. If you find that important, you could use the high accuracy option at the expense of a bit more battery impact. Try it!
Strava and Human are pretty different products, where Human tracks everyday activity, and Strava focuses on specific activities like running and cycling. We became pretty close with the Strava team over the years and were honored to count their leadership to our group of advisors. Being an avid Strava user myself, I'm excited to work with Strava in my new role at Mapbox.
We're looking forward to sharing what we learned about the health & fitness space, activity tracking, and mobile with all Mapbox customers.
Paul, founder of Human here. We chose the term "join" because it really feels like we're joining forces. One of the reasons why are so excited about this is the cultural fit and shared vision between both teams. We started Human for a reason and Mapbox is just as mission driven. Glad that our team and app can now be part of that.
Can you describe how money/shares/options get traded in a deal like this? Do you get cash for your shares/options or do you get shares/options in Mapbox or a mix of both?
Apple backs up your Health data in iCloud, if you enable it.
"Your data in the Health app is encrypted with keys protected by your passcode, and never leaves your device unless you choose to back it up or grant access to a third-party app. When you do choose to back up your Health data through iCloud, it is encrypted both in transit and on our servers."
No concrete plans yet. We never share any personal identifiable data, without explicit consent of our users. So if we would like to make (parts) of our data publicly available, we have to anonymize and aggregate that data first. For now we're focused on our app first.
Our tracking accuracy overal is good, but slow motorized transport versus bike rides have the highest error rates. That means that in a small percentage of the cases slow, bumpy car rides might get detected as biking and the other way around. Movement patterns vary quite a bit from city to city, especially for public transport. Users can correct detection errors, but that doesn't catch all cases. We have a slight bias towards cycling.
Sharp. Thanks!
In some cases we mix up (slow) motorized transport and cycling. We only categorize walking, cycling, running, active (active at one location) and motorized transport, so any other moving activity might end up in one of those categories. For daily use our tracking is pretty accurate for most activity types and users can manually correct any mistakes.
We rendered visuals for different activities in all cities. Click one of the cities on the homepage for details. We've also shared all visuals (dark and light) and some bonus gifs on Dropbox: https://www.dropbox.com/sh/58chppkj2ckim7s/AAAchKhSL56mjaaiA...
https://www.mapbox.com/geocoding/
Happy to answer any questions.
Disclaimer: I work at Mapbox.