So maybe I missed this in a previous conversation on Github's GeoJSON support, but what's the bigger picture here? I see a feature. I clearly recognize its utility. But, I can't seem to spot the larger trend that prompted this feature? Are there a lot of people using Github with GeoJSON files that are stored in the repo itself? If so, what are some of the use cases for this data being stored in Github? For some reason, I would have imagined that this type of data would be stored in a database and not a Github repo and that's what's confusing me.