GitHub's API rate limit is a problem

[gregoryjscott]

It's pretty easy to hit the rate limit of 60 requests/hour while doing development work since each refresh makes at least one request per .geojson file. We need a work around for development or another way to fetch the data.

[corys]

Wow, I had no idea the limit was that low. It would be preferable to load the geojson files that are local to the map file. We'd need server-side code to tell javascript which files to load. If we're not careful, this thing is going to turn into a real application. 😀

[gregoryjscott]

I edited the title since this could be a problem for users as well.

One option would be to use Jekyll to get GitHub to use the .geojson files from the repo, thereby avoiding API calls and server-side code.

Edited: I'm not sure if the Jekyll data files would work or not, but it seems like it should be possible to generate static content in way such that the data is available to the .js code.