71–74 of 74 posts
I've checked my local area, and already spotted more mistakes and omissions than correct tree markers. Not saying it as a complaint - there are so many more trees here than specified in the map, I bet the map only shows about 20-30%.
I've been Git scraping the San Francisco version of this for a few years now. My https://github.com/simonw/sf-tree-history repo now has 444 commits (most recent one was just 4 days ago) tracking every change that's been made to https://data.sfgov.org/City-Infrastructure/Street-Tree-List/... since March 2019. I haven't yet done anything with this data, but there is so much potential for visualizations and other fun st…
I love the idea of syncing git commit history with data change history, like using git for a repo of data. It's actually quite possible if you use pretty printed JSON as a record format (or other simple linear text formats). I explored more of this "git as DB backend" in some places including: https://github.com/dosyago/sirdb Also, just as a headsup to any folks, the SF version of this "tree map" (Heh) is at: https:/…
I've checked my local area, and already spotted more mistakes and omissions than correct tree markers. Not saying it as a complaint - there are so many more trees here than specified in the map, I bet the map only shows about 20-30%.
It says on the website that it shows 800 000 out of an estimated 8 million, so it shows just 10%
Earlier quoted context omitted.
I love the idea of syncing git commit history with data change history, like using git for a repo of data. It's actually quite possible if you use pretty printed JSON as a record format (or other simple linear text formats). I explored more of this "git as DB backend" in some places including: https://github.com/dosyago/sirdb Also, just as a headsup to any folks, the SF version of this "tree map" (Heh) is at: https:/…
I've been thinking about this recently also. I can't think of any downsides off the top of my head but I might be blinded by the idea? Can you?
There's a size limit to consider: GitHub won't let you push a file larger than 100MB and prefer you to keep the repo itself below 2GB.
Most of my scraping projects are a tiny fraction of that size though.