Street tree survey
Use with: build-website, ship-on-github. Resume line when done: Built {project_name}, a field survey and dataset of every tree on my block — live at {url}
Brief
Every tree on your block: identified with a field guide, photographed, measured where you can, and published as a map or list backed by a data file in a public repo. It is real fieldwork at walkable scale, and the expert check at the end (the neighbor with the garden, a biology teacher) is part of the method.
Personalize
- Your block, exactly. State the boundary: which side, corner to corner. Every tree inside it gets an entry, including the dead one and the stump.
- Your field guide. A regional guide or a plant-ID app, named on the page as your identification source. Where you are unsure, record the two candidates instead of forcing a pick.
- Your checker. Someone who knows local trees better than you. Their corrections get recorded, and they get thanked on the page by whatever name they choose.
Milestones
- Walk the block once and count; set up the survey sheet: location, species guess, trunk girth, condition, photo reference.
- The survey walk: photograph and log every tree. Shoot leaves and bark close-up; that is what identification needs.
- Identify each tree with the guide; mark confidence per entry (sure, probable, unknown).
- Structure the log into one data file; build the page mapping or listing every tree with photo and details.
- The expert check: walk the block or the page with your checker; record every correction.
- Publish the repo (data file, photos, README on method) and the final page.
Done means
- Live page with every tree in the stated boundary, photos included
- Public repo with the data file and a README describing the method
- Per-tree confidence recorded; unknowns published as unknowns
- Expert check happened and the corrections are in the data
- Photos are yours from the survey walk
- SESSIONS.md has an entry per session, written by you