Mobile AL Tree Removal Research · Dataset documentation
Tree Removal Permit Requirements — Change Log
Current version: 2026.07.28 · Records: 32 · Last verified:
This log records every released version of the 32-city tree removal permit requirements dataset. Versioned files are immutable. A future correction creates a new dated file and a new entry here identifying the affected row, old value, new value, reason, and primary source.
Version 2026.07.28 —
Initial production release after final primary-source audit. The release contains 32 jurisdiction records, the four-model classification, a six-state statutory layer, a Mobile and Alabama Gulf Coast comparison, source-status fields, excluded-field handling, and CSV/JSON distributions.
Verified corrections made during the final audit:
- Corrected the Hauer and Peterson denominators for the 89% ordinance figure and 25% private-property restriction figure.
- Corrected the dataset model count to 16 A / 5 B / 5 C / 6 D after the Jacksonville reclassification.
- Corrected the measurement-basis count from three to four (DBH, DSH, caliper, and circumference are each in active regulatory use).
- Replaced Gulf Shores' stale 2025 endpoint with Ordinance No. 2206, adopted March 23, 2026.
- Corrected San Antonio's completed-single-family exemption and its 5-inch listed-small-species threshold.
- Replaced Washington, D.C.'s superseded 44-inch Special Tree threshold with the current 40-inch threshold effective May 21, 2026.
- Corrected the Washington, D.C. Heritage Tree statement to reflect current statutory permit pathways rather than a blanket prohibition.
- Updated Jacksonville to the 2026 location-based 6/8/11.5-inch thresholds and current fee schedule.
- Updated San Francisco to the fee schedule effective July 1, 2026, including the listed $9 surcharge and $2,646 in-lieu fee where applicable.
- Removed unconfirmed secondary-source figures and converted unresolved claims into explicit excluded fields.
- Replaced promised dataset placeholders with actual versioned CSV and JSON files.
Immutability policy
Once published, a versioned release file is never overwritten. A later correction must create a new dated version and identify the affected row, old value, new value, reason, and primary source in this log. This allows prior citations to be reconstructed exactly.