Timeline for Keeping track of updates to open data published as CSV
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2013 at 15:12 | comment | added | dwillis | Here's a tip about using Github for datasets: the size limits for files and bandwidth limits are different for Github Pages, so if you keep the data on the gh-pages branch, you can store more there with fewer concerns about violating ToS. | |
| May 27, 2013 at 21:15 | comment | added | Alvaro Graves | True, but I'm pretty sure that for many, many small organiztions (at county or municipal level) that have low use of bandwidth this is still useful. Even more, the same process and use of git doen't need github necessarilly - that's only to make the tutorial simpler. You can always configure a git repository in your iwn servers and keep track of changes in files | |
| May 27, 2013 at 9:47 | comment | added | Deer Hunter | github may be not a fitting solution for datasets - From their ToS: "If your bandwidth usage significantly exceeds the average bandwidth usage (as determined solely by GitHub) of other GitHub customers, we reserve the right to immediately disable your account or throttle your file hosting until you can reduce your bandwidth consumption." | |
| May 27, 2013 at 1:02 | history | answered | Alvaro Graves | CC BY-SA 3.0 |