Tree-protection presets

City of Acworth, GA

• ⚠ ACWORTH PUBLISHES NO CRZ RADIUS ANYWHERE — no feet-per-inch multiplier, no dripline rule, no table. Checked § 73-14.5 (Tree Protection Standards), § 73-14.9, § 73-14.10 and the § 73-15 definitions: the ordinance uses the term 'critical root zone' throughout and requires CRZs to be drawn and fenced, but never says how to derive one. That is a finding about the code, not a gap in this preset, and it is why no CrzMode or multiplier ships. Both tools keep whatever radius rule the user already has — set it deliberately, and note the 20 percent encroachment limit above is measured against THAT zone.
• The tree density standard has no field in either tool: § 73-14.2 requires one hundred (100) inches per acre for non-single-family residential development and fifty (50) inches per acre for single-family, and holds 'whether or not a site had trees prior to development'. Stated here so the numbers are not lost — the ordinance's own worked example is 3.2 acres x 100 = 320 inches required.
• Only trees two inches DBH or greater count (§ 73-14.9): 'Existing trees less than two (2) inches DBH will not be counted toward the required density', and they need not be shown individually. Neither tool has a minimum-countable-diameter field, so filter the survey by hand.
• Specimen MITIGATION is a replacement schedule, not a survey value, so it is not modelled: a removed specimen is replaced with minimum four (4) caliper inch trees on an inch-for-TWO-inch basis (§ 73-14.4), and those recompense trees are IN ADDITION to the 100 inches per acre. The ordinance works it through: a 24-inch oak needs 48 replacement inches, i.e. twelve 4-inch trees.
• Acworth's specimen CONDITION test (§ 73-14.4) is an arborist judgement — life expectancy over fifteen years, a relatively sound and solid trunk with no extensive decay, no more than two major and/or several minor dead limbs, radial trunk dieback under 20 percent and canopy dieback under 30 percent. The preset can only approximate it by excluding poor and dead trees, and BOTH size and condition must be met. ⚠ An arborist report signed by a certified arborist or registered forester is required for EVERY specimen tree impacted by a development needing an LDP, and City staff make the final determination — so specimen status here is not something a drawing can settle.
• Small trees can also qualify as specimen without meeting any size threshold — 'if of a rare or unusual species, of exceptional quality, or socio-historical significance', or if used as a focal point of the landscape design, on a certified arborist's letter (§ 73-14.4). No size rule can express that; flag those by hand.
• Table 7.3.6.H.3 (§ 73-14.6) converts a planted EVERGREEN's nursery height to inches of credit (2 in at 6 ft minimum, rising to 6 in at 18 ft). It is a planting schedule keyed to height, not a DBH-to-units chart, so the tools' units chart cannot hold it.
• Alternative compliance (§ 73-14.7) caps at 40 percent of the required replacement density and is priced at $200 per DBH inch for non-specimen trees and $400 per DBH inch for specimen trees, paid to the City tree bank fund. A fee schedule has no field in either tool.
• The 1.5x specimen credit is stated by the ordinance as '1.5 x inches DBH' because Acworth's density metric is DBH INCHES, not density units. The multiplier ships because the ratio is the rule and transfers exactly; do not read it as a claim that Acworth publishes a units table. It does not.
• No structural-root-plate (SRP) chart is published in this ordinance, so SRP stays disabled. § 73-14.5 specifies protection FENCING (minimum four feet, orange laminated plastic netting, bilingual signage) around the whole CRZ rather than an inner no-disturbance ring.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Specimen Hardwood and Conifer (24 in), Specimen Fast-Growing (30 in), Specimen Understory (10 in). Without it the thresholds load but no tree is classified.

City of Atlanta, GA

• Atlanta lets the city arborist adjust the assumed CRZ for documented site conditions (§ 158-26); a preset cannot model a case-by-case discretion.
• Atlanta's current Chapter 158 does not use the term 'specimen tree' at all — the June 2025 re-enactment (Ord. 2025-19) dropped it. There is no specimen threshold in this code to set.
• Atlanta's mitigation is a dollar recompense (§ 158-103), not a units ratio, so no unit multiplier is set.
• The SRP table covers 6 to 83 inches DBH. The ordinance gives no radius for a tree under 6 inches or over 83 — those fall outside the published table.
• The city arborist may adjust the assumed SRP for documented site conditions (§ 158-26).

Cherokee County, GA

• ⚠ THE SPECIMEN CREDIT MULTIPLIER OF 4x IS WITHHELD, AND IT IS REAL ADOPTED LAW. Appendix A (§ 27.18): "Credit for any Specimen Tree thus saved would be four times the assigned unit value shown in Appendix C - Table A." The ordinance then takes it back — the tree "must be within or directly adjacent to the developable areas of the site" and "Specimen Trees which lie inside areas already protected, such as open space, stream buffers and Zoning buffers shall not receive extra density credit." A CriteriaGroups UnitMultiplier applies to every tree in the group with no way to express that exclusion, so shipping 4x would quadruple the credit of every specimen standing in a stream buffer and make a plan read as compliant when it is not. Withholding it under-credits instead: each specimen counts once, the designer plants more than required, and the error runs the safe way. Apply the 4x by hand for specimens the design deliberately saves outside protected areas.
• ⚠ THE WETLAND CREDIT OF 2x IS WITHHELD FOR THE SAME REASON, one step further removed. Appendix C: trees preserved "within 100' of delineated wetlands and/or ephemeral streams that are specifically protected as part of the design of a project MAY apply 2x the unit value", and only if "Entire wetland or ephemeral channel and entire CRZ of all credited trees must be protected". An AreaDefinition applies its multiplier to whatever polygon is drawn, unconditionally — it cannot represent an election the designer may or may not make, nor a condition about protecting the whole channel. CanopyCode only; ArborCode ignores areas entirely. Gap register.
• The Site Density Factor CANNOT be shipped and this is a limit of the tools AND of the shape of the rule. § 27.8 sets it per zoning district across 21 districts — 20 units/acre for AG, TND, R-80, R-60, R-40 and R-30, falling through 19, 18, 17 and 16 to 15 for HC, OD, LI and HI — so there is no city-wide figure. Appendix C adds a further reduction to 10 units/acre for pasture land. Neither CanopyCode nor ArborCode has a units-per-acre field at all. Gap register.
• Table A stops at 40 inches. For a tree 41" or greater the ordinance gives a FORMULA rather than a row — "(Diameter) 2 x .7854 ÷ 144", i.e. basal area in square feet — and a units chart holds rows, not expressions. A 41-inch-plus tree must be computed by hand; the tools would otherwise resolve it downward to the 37–40 band and under-credit it.
• Boundary trees have their OWN, SMALLER CRZ and it cannot ship. § 27.3: "Boundary tree critical root zones shall be reduced to a radius equal in feet to one point three times the number of inches of the tree's trunk diameter at DBH." The preset's CRZ multiplier is a single site-wide value, so 1.5 ships as the general rule; a tree on an adjoining property is 1.3. Neither tool has a per-tree CRZ override or a boundary-tree flag. Gap register.
• The specimen CONDITION test is only approximated. Appendix A requires life expectancy over fifteen years, a relatively sound trunk with no extensive decay, no more than one major and several minor dead limbs, and no major insect or pathological problem, all "As determined by County Arborist". ConditionType records Excellent/Good/Fair/Poor/Dead/Unknown, so the ExcludePoor and ExcludeDead flags carry as much of that as the data model can hold.
• "Pines species do not qualify as Specimen Trees" (Appendix A) is a SPECIES exclusion, and neither tool can exclude a species from a classification group — the group keys on DBH and condition only. A pine over 24 inches will therefore classify as a specimen in the tool and must be de-selected by hand. Gap register.
• No SRP chart is published anywhere in Article 27, so SRP stays disabled.
• No impact-threshold percentage ships. The two the ordinance prints are both SCOPED rather than site-wide: a boundary tree needs owner notification past "an encroachment into the Critical Rood Zone of greater than 10%" (§ 27.3, the county's own typo for Root), and a tree prescription may substitute for recompense planting "for specimen trees with critical root zone impacts between 10-20 percent" (§ 27.18). RemovalMinPct is a single site-wide number, and neither of these is one — the Dallas precedent.
• The recompense arithmetic is mitigation, not credit, and has no field: a removed specimen (or one with impacts of ten percent or greater) requires "recompense planting equaling two times their density unit value", and an UNPERMITTED removal "eight times the unit value of the tree removed" (§ 27.18). Both are penalties computed after the fact, not multipliers on a surveyed tree.
• Table B (replacement caliper 2"–10" to density units) is deliberately NOT shipped as the units chart. It converts the caliper of NEW nursery stock, not the DBH of surveyed existing trees, and the tools' chart is read against an inventory. Shipping it would silently re-price every existing tree on the site.
• Heritage Trees (Appendix B) are a REGISTRY, not a size class — the Board of Commissioners designates them on the Arborist's recommendation and the Arborist maintains the list. There is no threshold to set, so nothing ships; the county's registry has to be consulted per site.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Overstory, Understory. Without it the thresholds load but no tree is classified.

City of Dallas, GA

• ⚠⚠ TABLE 7.11 HAS HOLES, AND THEY ARE THE ORDINANCE'S. No unit value is printed for a 16, 17, 19 or 20 inch tree. Both tools look up a value by the band START only, so a 16-inch tree will silently take the 15-inch value (3.3) and a 20-inch tree the 18-inch value (4.2) — an UNDER-credit, i.e. the safe direction, but not a number the code states. Confirm those four diameters with the city rather than relying on the chart.
• ⚠ THE CHART STOPS AT 34 INCHES. Table 7.11's last entry reads "37 or greater 12.0 + 1.0 each inch" — a formula, not a row, and an ambiguous one (whether the 1.0 runs from 36 or 37 is not stated). No units-chart row can hold it, so nothing above 34 inches is modelled and a large tree will be substantially UNDER-credited. Diameters 35 and 36 have no printed value at all. Compute the credit for any tree over 34 inches by hand.
• The Tree Density Standard of sixteen (16) Tree Density Units per acre — the same figure for residential, office/commercial/mixed-use and industrial (§ 7.06) — has no field in either tool; neither models a per-acre density target. Stated here so the number is not lost.
• Table 7.12 (units for NEW replacement trees) is a planting schedule rather than a survey value, and the tools' chart is keyed to surveyed DBH only. Its own top band is likewise a formula ("17+ 3.5 + 0.5 for each"). Not modelled.
• ⚠ DALLAS'S IMPACT PERCENTAGES ARE NOT A SITE-WIDE RULE AND ARE DELIBERATELY NOT SHIPPED. The 19 percent / 20-33 percent CRZ-TPZ thresholds in § 7.06 sit under "parameters shall be followed when determining BOUNDARY TREE viability interference" — the procedure for a neighbour's tree affected by construction, which also requires a signed, notarised boundary tree agreement. Setting them as the removal and prescription thresholds for every tree on the site would be our inference, not the law.
• The specimen double credit is DISCRETIONARY AND CONDITIONAL: the code says units "may be" increased, provided extraordinary measures (tree wells, retaining walls, aeration, supplementary irrigation) are taken and approved by the Director. Do not bank it without planning those measures.
• Dallas's specimen definition also admits trees BELOW the size thresholds — a rare or unusual species, exceptional or unique quality, historical significance, or a tree used as a landscape focal point — each subject to the Director's approval. No size rule can detect those; flag them by hand. The same is true of a "specimen tree stand", which is judged as a grouping.
• The four-part fair-or-better condition test (a life expectancy over fifteen years; a structurally sound trunk, not hollow, with no extensive decay and less than 20 percent radial trunk dieback; no more than one major and several minor dead limbs (hardwoods only); no major insect or pathological problem) is approximated only by excluding poor and dead trees.
• Street trees COUNT here — "Trees, including street trees, may be retained or planted for credit within a public street right-of-way" (§ 7.06). That is the opposite of several neighbouring codes, but right-of-way is a built-in geometry classification in CanopyCode rather than a preset field, so it cannot be set from this file.
• The easement and lake/pond provisions (§ 7.06) exclude land AREA from the site acreage used to compute the requirement. They change the denominator, not any tree's credit, so they are not area definitions. The 20 percent bonus for the enhanced protection program is likewise a canopy-coverage bonus, not a per-tree unit multiplier.
• Dallas publishes no structural-root-plate chart, so SRP stays disabled.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Overstory Hardwood, Understory, Pine. Without it the thresholds load but no tree is classified.
• Draw a polyline for each area and name it exactly as listed above — the tools match an area to its shape by name. An area you never draw is simply ignored.

Douglas County, GA

• Douglas defines 'fair or better condition' with four specific tests (§ 803) — life expectancy over 15 years, a structurally sound trunk with under 20 percent radial dieback, limited dead limbs, and no major insect or pathological problem. The preset approximates this by excluding poor and dead trees; the judgement is still the arborist's.
• A SMALLER tree can still be a specimen if it is a rare or unusual species, of exceptional quality, or of historical significance, subject to the County Arborist (§ 803). That has no size rule and cannot be auto-detected.
• The CRZ definition states no dripline alternative, so the mode stays the default DBH multiplier.
• No numeric root-zone disturbance limit is stated in the definition section, so no removal threshold is set.
• No structural-root-plate (SRP) chart is published, so SRP stays disabled.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Overstory hardwood, Overstory softwood, Understory small tree, Pine (all species). Without it the thresholds load but no tree is classified.

Duluth, GA

• Duluth has NO specimen-tree size threshold. A specimen tree is one a registered landscape architect, the Director, or a certified arborist determines to be of high value (§ 1403), so there is no number to set.
• Duluth states no numeric root-zone disturbance limit in the CRZ definition, so no removal threshold is set — the tool keeps its own default.
• No structural-root-plate (SRP) chart is published, so SRP stays disabled.

Fayetteville, GA

• ⚠ FAYETTEVILLE STATES NO CRITICAL ROOT ZONE RADIUS ANYWHERE IN ITS 512 SECTIONS. The UDO uses the term and regulates inside it — "in no circumstance shall a grade change be allowed to intrude upon the critical root zone of a specimen" (§ 403.19), and §§ 403.89 and 403.91 prohibit paving, filling and material storage within the CRZ of a city tree — but it never says how far the zone reaches. No feet-per-inch multiplier, no dripline definition, no table. So no CRZ value is authored and both tools keep the multiplier the user already has. ⚠ THE PRACTICAL CONSEQUENCE: the CRZ drawn on a Fayetteville plan is the designer's own standard, not the city's, because the city has not published one. Confirm the expected radius with the UDO Administrator before relying on it.
• The nearest thing to a published radius is a CONSTRUCTION PRACTICE rule, not a protection zone, and it is deliberately not used: § 403.70 allows trenching "no closer to a tree's trunk than 75 percent of the dripline radius". That is a limit on one activity, expressed as a fraction of a dripline the code never requires anyone to measure — it is not a CRZ definition and cannot be read as one.
• There is NO tree-density or units system. § 403.20 sizes replacement planting off IMPERVIOUS SURFACE instead — "For every 2,000 square feet of impervious surface, the landscape plan shall provide no less than three caliper inches of canopy trees and no less than two caliper inches of understory trees." Neither tool has an impervious-driven replacement field; both model density units per acre. It cannot be approximated either, because it keys on pavement rather than on the trees being surveyed. Gap register.
• The $100 per caliper inch in § 403.12 is NOT a mitigation rate and must not be shipped as one. The sentence is permissive and evaluative: "For evaluation purposes, the criteria of $100 per caliper inch of trunk as measured at the top of the remaining stump MAY be used." It values a stump after an unpermitted removal; it sets no replacement obligation. (This is the reading recorded at S126 and it is unchanged.)
• The 25 percent tree-save credit in § 403.21 is a DISCRETION, not a threshold, so no impact threshold ships: the Planning and Zoning Commission "MAY permit up to a 25 percent reduction in the total number of trees required". "Up to" and "may" are not a rule a preset can state as law, and RemovalMinPct means something different in any case — how much CRZ disturbance kills a tree's credit, not how much planting a commission may waive.
• No SRP chart is published, so SRP stays disabled.
• NO AREAS. Section G was swept. § 403.21 excludes tree save areas that are "vegetation located within required buffers or areas identified for future development" from the credit above — but that is an exclusion from a discretionary planting reduction, not a rule that changes what a surveyed tree is worth. Modelling it as an AreaDefinition would be our inference rather than the law, which is the call already made for Marietta and Snellville.
• Historic significance is the FIFTH specimen criterion and cannot ship: "Any tree which has a significant historical value and can be documented through historical records, or otherwise" (§ 403.8). It has no DBH, so there is no threshold to set — a tree of any size may qualify. The four size classes above are complete for everything the tools can classify; a historic tree must be flagged by hand.
• "A specimen tree is any tree OR GROUPING OF TREES" (§ 403.8). Neither tool can classify a grouping — both key on an individual surveyed stem — so a stand that qualifies collectively while no single tree meets a threshold will not be caught. Gap register.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Deciduous Canopy, Evergreen Canopy, Understory, Dogwood, Redbud or Magnolia. Without it the thresholds load but no tree is classified.

Forsyth County, GA

• ⚠⚠ THE ORDINANCE'S OWN WORKED EXAMPLE DOES NOT FOLLOW FROM ITS OWN TEXT, and a designer copying it would over-credit a site by a wide margin. § 2.11's example preserves three 18-inch oaks, marks them significant, and totals them at 64.8 units — exactly FOUR TIMES the 3 x 5.4 = 16.2 that Table A gives. The EDF of 91.5 depends on that 64.8, so it is not a typo in one cell. Nothing in Ordinance 98 grants a preserved significant tree a multiplier: the only 'four times' in the document is § 2.8 B, the PENALTY for removing a significant tree without the County Arborist's approval, and the example says the trees remain. Read position-true from page 25, the '3' and the '64.8' are both INSERTIONS in the current draft while the 91.5 total is unchanged, so the discrepancy predates the amendment. No multiplier ships, because no sentence states one — a ratio we worked out ourselves is arithmetic, not law. Ask the County Arborist which is right; it is worth an email on its own.
• ⚠ THE SITE DENSITY STANDARD ITSELF HAS NO FIELD IN EITHER TOOL (gap register G1) — the chart says what a tree is WORTH, never what the site OWES. Stated here so the numbers are not lost: § 2.11 requires disturbed acreage x 20 tree density units for single-family residential zoned property, and x 15 for commercial, mixed use, industrial and all other non-single family zoned property. Both numbers are UNCHANGED by the amendment (the draft only renumbers the two clauses from 1./2. to A./B.), so they hold in either version.
• ⚠ TABLE B, THE REPLACEMENT TREE TABLE, CANNOT SHIP: a preset holds ONE units chart and Table A already occupies it. Table B converts the caliper of a NEWLY PLANTED tree to units — 2 in = .5, 3 = .6, 4 = .7, 5 = .9, 6 = 1.0, 7 = 1.2, 8 = 1.3, 9 = 1.5, 10 = 1.7 — read position-true from page 27. ⚠ The current draft DELETES its old rows for 11 to 14 inches, so the amended table stops at 10, and it also deletes the note granting seven-gallon or larger container-grown pines a 0.4-unit replacement credit. Enter replacement units by hand.
• ⚠ THE ZONING-BUFFER RULE IS NOT AN AREA MULTIPLIER AND MUST NOT BE MODELLED AS ONE. § 2.11 says existing SIGNIFICANT trees inside a required zoning buffer may count toward the existing density factor only if the ENTIRE CRZ is protected, while non-significant trees and inadequately protected significant trees may not count at all. A single `UnitMultiplier` on a buffer area would apply to every tree in it: set it to 0 and the protected significant trees lose credit the code grants them; set it to 1 and the non-significant trees keep credit the code denies. The rule depends on the tree's CLASS and on whether its CRZ is protected, and no area field can read either.
• § 2.12's exclusions reduce the DENOMINATOR, not a tree's credit, so no area expresses them: public utility easements carrying petroleum, gas, electric transmission or major sewer and water mains come out of the total acreage (provided no building, parking or roadway sits in the easement); public athletic fields and trails come out of the disturbed area; and in industrial districts with building footprints aggregating over 30,000 square feet the building area is excluded. Subtract these before multiplying by 20 or 15.
• § 2.7's significant-tree test is FIVE parts and the preset can only approximate three of them. Beyond the size table it requires a sound trunk with less than 20% radial trunk dieback, no major insect or pathological problems, and a life expectancy of 15+ years for hardwoods or 8+ years for pines — approximated here by excluding poor and dead trees. It also lets SMALLER trees qualify if they are rare or of unusual quality, species, or historical significance, and any landmark or historic tree qualifies outright. Those have no size rule and cannot be auto-detected; flag them by hand.
• Removal recompense and penalties have no field. § 2.7: a significant tree removed WITH prior approval must be replaced at one unit for each unit awarded in Table A, on top of the minimum site density factor, and in commercial and industrial districts that recompense will not exceed 30.0 units per acre. § 2.8: removed WITHOUT approval, a landmark or historic tree costs eight times its unit value and any other significant tree four times, with a minimum three-inch caliper on the replacements.
• The fee-in-lieu is priced PER UNIT SHORT, which `RecompenseFormula` cannot express (it is per-tree and per-DBH-inch). § 2.14: where the density cannot be met, a contribution of $1,500.00 per unit short must be paid into the county Tree Replacement Fund before any permit issues, with the Director's approval. Commercial and industrial applicants may instead plant in a required side or rear buffer, or off-site within one mile on public property, subject to an indemnification agreement.
• Per-lot and open-space planting quotas have no field. § 2.9 A: every detached single-family lot needs at least two trees with one in the front yard (three on a corner lot, one per street-facing yard), minimum two-inch caliper overstory hardwood, and they may count toward the site density factor. Open space in new and future-phase major subdivisions must preserve or provide 15 overstory trees per acre. ⚠ A preserved healthy overstory tree over 16-inch dbh 'can count for three newly planted overstory trees' there — a 3x that does NOT ship, because it is scoped to subdivision open space and is granted 'as approved by the County Arborist', so it is neither site-wide nor automatic.
• ⚠ NO IMPACT THRESHOLD SHIPS, and the code is not silent — it is SCOPED. Ordinance 98 publishes no tolerated share of CRZ disturbance anywhere (the only percentage near a tree is the 20% trunk-dieback limit in the significant-tree test). § 2.9 C sets a genuinely zero-disturbance rule, but only for BOUNDARY trees: every tree 8 inches dbh or greater within 25 feet of the property line must be shown with its CRZ, and the limits of disturbance adjusted so nothing beyond minimum utility work enters it. `RemovalMinPct` is site-wide with no scope field, so shipping 0 would disqualify every disturbed tree on the site. Same call as Dallas.
• No structural-root-plate (SRP) chart and no inner ring are published, so SRP stays disabled — read, not assumed. § 3.1 requires protection devices around the whole CRZ instead: active protection (chain link, orange laminated plastic, wooden post or rail fence, at least four feet high) near construction, passive protection elsewhere, installed before any land-disturbing activity and kept functioning until the certificates of occupancy issue.
• Terminology: Forsyth writes 'critical root zone (CRZ)', 'tree density unit', 'site density factor (SDF)', 'existing density factor (EDF)', 'replacement density factor (RDF)', 'tree save area' and 'tree protection area'. Its protected class is a SIGNIFICANT tree, not a specimen tree — the draft strikes the word 'specimen' throughout — so a drawing legend reading 'specimen' will not match the reviewer's vocabulary.
• ⚠ SCOPE, WHICH DECIDES WHETHER ANY OF THIS APPLIES AT ALL. § 2.1 exempts ten activities from the whole ordinance, and two of them cover most residential work: construction of a single-family detached dwelling that is NOT part of a major subdivision, and tree removal by an existing single-family homeowner. Also exempt are agricultural clearing in agricultural districts, additions and minor remodelling of an existing residence, cell towers, nursery and orchard stock, utility and government work in rights-of-way, removal of dead, diseased or infested trees on written confirmation from the Georgia Forestry Commission or Arborist, and unzoned tracts under O.C.G.A. 12-6-24(e)(4)(B).
• Regime: this is a plain protection-plan jurisdiction, which is ArborCode's default, so nothing is emitted for it. §§ 2.3 to 2.5 build the whole process around Tree Protection and Replacement Plans submitted with the land disturbance permit, prepared by a registered landscape architect, urban forester or arborist, with a site walk by the County Arborist after submission. ⚠ Two procedural traps a drawing cannot show: a pre-submittal meeting with the County Arborist is REQUIRED for residential projects on ten acres or more outside a Mixed Use district (§ 2.2 B), and a property clear cut within three years of a zoning application is ineligible for rezoning for three years (§ 2.2 A). In commercial, mixed use and industrial districts the trees must also survive a maintenance inspection one full growing season after final inspection (§ 2.15).
• ⚠ CanopyCode has no canopy or dripline input, so it cannot express a dripline-based zone at all. That costs nothing here: Forsyth's CRZ is a pure DBH circle and the multiplier above is exactly what both tools compute.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Overstory Hardwood, Pine, Poplar, Sweetgum, Understory / Small. Without it the thresholds load but no tree is classified.
• Draw a polyline for each area and name it exactly as listed above — the tools match an area to its shape by name. An area you never draw is simply ignored.

City of Gainesville, GA

• ⚠⚠ THE 4x SIGNIFICANT-HARDWOOD CREDIT IS REAL LAW AND CANNOT BE SHIPPED, because the group it attaches to has no size rule. § 13-3-15 says 'When an existing tree meets the definition of "significant hardwood tree" as provided in this Chapter, the value assigned is four times the value shown in Table 13-6', and § 13-3-6 repeats it. But a 'significant tree' is one 'determined to be of a high value by an Arborist, Forester, or other qualified professional' (§ 2-1-4), so no diameter threshold can select it. Both tools attach a unit multiplier to a CLASSIFICATION GROUP, and there is no group to attach it to. Apply the 4x by hand to the trees the arborist designates.
• ⚠ A significant tree does carry a CONDITION test, and it is the one part of the definition that is mechanical: a tree is 'in fair or better condition' if its life expectancy is greater than 15 years, it has a relatively sound and solid trunk with no extensive decay or hollow with less than 29% radial tip die-back, and it has no major insect or pathological problems (§ 2-1-4). Condition alone does not make a tree significant, so it cannot be shipped as a group either.
• ⭐ TABLE 13-6 (§ 13-3-15) IS A REAL DBH-TO-UNITS CHART — 1 to 4 in through '50 and above', ending at 17.0 units — and it is a genuine `unitsChart` candidate that is DELIBERATELY NOT SHIPPED YET. Three things have to be true first and none of them is a judgement call: the rows must be extracted POSITION-TRUE from the source PDF (the flattened body interleaves two DBH/units column PAIRS and repeats its header mid-table, which is exactly how a row gets paired with the wrong value); the chart's first two rows are BANDS ('1 to 4', '5 to 6') which the single-diameter row format cannot express; and the ordinance prints its values without a leading zero ('.3', '.6'), which the builder's adjacent-token check does not yet recognise. Enter Table 13-6 by hand until then.
• Table 13-7 (§ 13-3-16) cannot be shipped at all, for the Marietta reason: it gives TWO unit values per caliper — one 'Generally' and one for 'Large Species' (a species reaching 40 feet or more at maturity) — and the tools' units chart holds a single value per band. It is also keyed to REPLACEMENT caliper rather than survey DBH.
• The tree density standard has no field in either tool: § 13-3-12 requires 'a total Tree Density Unit of no less than 18 units per acre' of the development site, and 'development site' excludes both undeveloped portions of the lot and land area covered by buildings. Stated here so the number is not lost.
• ⚠ GAINESVILLE PUBLISHES TWO DIFFERENT CRZ DISTURBANCE RULES AND NEITHER MAPS CLEANLY TO `RemovalMinPct`, so no impact threshold ships. § 13-3-11(e) permits encroachment where necessary to the development 'provided the tree is not counted toward the required minimum tree units per acre' — i.e. ANY encroachment costs the tree its credit — and then caps encroachment at 'nor more than 25% of the total area in the root protection zone circle'. Those are a credit rule and a hard cap, not one threshold. Shipping 25 would tell a designer they may disturb a quarter of the root zone and still count the tree, which is the opposite of what (e) says.
• Gainesville's other CRZ protections are prescriptive rather than numeric and have no field: no grade change, no topsoil stripping, no ditches or trenches, no impervious paving within the critical root zone, and where limited encroachment is approved the zone must first be mulched with a 4-inch layer of processed pine bark or wood chips or a 6-inch layer of pine straw (§ 13-3-11).
• Recompense for unauthorised removal is a penalty schedule, not a survey value: a specimen tree removed without prior approval must be replaced by trees totalling TWICE the unit value of the tree removed, with replacements a minimum 3-inch caliper; a historic or landmark tree, FOUR times (§ 13-3-6). Historic and landmark trees are those on the state urban forest council's landmark and historic tree register (§ 2-1-4), which no drawing can detect.
• No structural-root-plate (SRP) chart is published in this code, so SRP stays disabled.

• Draw a polyline for each area and name it exactly as listed above — the tools match an area to its shape by name. An area you never draw is simply ignored.

City of Grayson, GA

• ⭐ THE DBH-TO-UNITS CHART (§ 1503 C) IS A REAL `unitsChart` CANDIDATE AND IS DELIBERATELY NOT SHIPPED YET. It runs from a 1-4 inch band at 0.10 units to 50 inches at 13.60. Three things block it, none of them a judgement call: the rows must be extracted POSITION-TRUE from the source PDF (the flattened body interleaves THREE DBH/units column pairs across the page); the first three rows are BANDS ('1-4', '5-7', '8-9') which the single-diameter row format cannot express; and every value is printed to two decimals ('0.10', '13.60'), which the builder's adjacent-token check does not yet recognise. Enter the chart by hand until then.
• ⚠⚠ AND THE CHART CONTAINS A PRINTED ERROR, WHICH IS THE BEST ARGUMENT FOR NOT READING IT OFF THE PAGE. The row between 29.00 and 31.00 is printed as '3.00 4.90' — the diameter is missing a zero and should read 30.00. Two independent facts confirm it: the surrounding diameters ascend one inch at a time, and Sugar Hill's Buffer, Landscape and Tree Ordinance — a separate city whose Table B carries IDENTICAL unit values from 14 inches upward, both being adoptions of the same Georgia model text — assigns 4.9 units to a 30-inch tree. ⚠ That neighbouring table is EVIDENCE, never a substitute: Grayson's chart still has to be read position-true from Grayson's own PDF before it ships. Never borrow one city's table for another.
• The tree density standard has no field in either tool: § 1503 A requires a Tree Density Factor of twenty (20) tree density units per acre, exclusive of all acreage within a required buffer, and § 1111 repeats the same 20 units per acre for all non-residential development. The ordinance sets out the arithmetic itself — acreage less buffer, times 20, minus the Trees to Remain Factor, equals the Required Replacement Density.
• ⚠ A SECOND, PARALLEL STANDARD RUNS BY ZONING DISTRICT AND IS EASY TO MISS BECAUSE IT USES DIFFERENT UNITS: § 1503 E requires PUD, RM, O-I, C-1, C-2, C-3 and M-1 properties to provide a minimum of one hundred (100) inches in caliper per acre, and R-100, R-100 Modified and MH properties fifty (50) inches per acre — caliper inches, not density units, on top of the 20 units per acre above. Residential subdivisions additionally require three canopy and two understory trees per R-100 lot, or two and two in R-100 Modified and the residential portion of a PUD.
• A retention quota applies to specimen trees and cannot be expressed as a per-tree rule: § 1503 G.3 — 'No more than fifty (50%) percent of specimen trees shall be permitted to be removed.'
• Specimen MITIGATION is a replacement ratio, not a survey value: a removed specimen must be replaced 'by species with potentials for comparable size and quality' at one and one half (1½) times the specimen tree size, and that recompense does NOT count toward the Required Replacement Density (§ 1503 G). Species selection and replacement densities are subject to the City Arborist's approval, and an on-site inspection by the City Arborist is required (§ 1502).
• Grayson restricts which SPECIES earn density credit at all — § 1503 F lists 30 acceptable canopy trees (oaks except Live Oak, hickories, tulip poplar, sweetgum, sycamore, loblolly and Virginia pine, and others) and 6 understory trees (dogwood, sourwood, redbud, trident maple, crape myrtle, wax myrtle). Neither tool has a species-eligibility field, so a survey that counts an unlisted species will over-credit the site.
• Container-grown pine has its own credit ratio and cap (§ 1503 D.1): seven-gallon trees earn credit at seven trees for every .2 units, and no more than twenty percent of the replacement credit may be in seven-gallon container pines. All planted trees must be a minimum of two inches caliper.
• No structural-root-plate (SRP) chart is published in this ordinance, so SRP stays disabled, and no CRZ encroachment percentage is published either.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Specimen Tree. Without it the thresholds load but no tree is classified.

Gwinnett County, GA

• Gwinnett's specimen CONDITION test (§ 630-70.3.A.2) is a five-part arborist judgement — life expectancy over 10 years, a sound trunk, limited dieback, no major insect or pathological problem. The preset can only approximate it by excluding poor and dead trees; the survey still has to be done on site.
• The two OPTIONAL specimen criteria — exceptional quality and historical significance (§ 630-70.3.A.2.f-g) — have no size rule and cannot be auto-detected. Flag those by hand.
• The Table 630.3 preservation-credit tiers (100/75/50/25 percent by disturbance band) have no field in the preset schema; they are summarised in the disclaimer instead.
• SPECIMEN TREES ARE UNDER-CREDITED, and by a knowable amount. The units chart this preset carries is Table 630-2, Credit for Existing Trees. Gwinnett publishes a SECOND chart for specimen trees, Table 630-3, whose value is exactly one third higher at every diameter the two share. Neither CanopyCode nor ArborCode has a field for a second chart, and the code never prints the ratio as a number, so no multiplier could be cited even though one would fit. Multiply a specimen tree's units by 4/3 by hand, or read Table 630-3 directly.
• No structural-root-plate (SRP) chart is published in this ordinance, so SRP stays disabled.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Large Hardwood, Large Softwood, Small Native Flowering. Without it the thresholds load but no tree is classified.
• Draw a polyline for each area and name it exactly as listed above — the tools match an area to its shape by name. An area you never draw is simply ignored.

Johns Creek, GA

• ⭐ THE ARITHMETIC OF THIS ORDINANCE IS NOT IN THE ORDINANCE, AND AS OF 2026-08-22 WE HOLD THE DOCUMENT IT IS IN. Chapter 109, Article VII repeatedly hands its numbers to a separate instrument it adopts BY REFERENCE — "Administrative guidelines means those certain guidelines, including any appendices... incorporated by reference into the tree preservation ordinance" (§ 109-189) — and § 109-190(a) adds that copies "are now on file in the office of the clerk... and the provisions of the same shall be controlling." The city's Administrative Guidelines of the Tree Preservation Ordinance (Updated July 2025) were obtained from the city and ingested, which is where the specimen table, the DBH-to-units chart and the root protection zone on this preset all come from. ⚠ A codifier publishes the CODE; a document incorporated by reference is not part of it, so no amount of re-downloading Municode would ever have closed this.
• ⚠ THE UNITS CHART SHIPS BUT THE SITE TARGET DOES NOT, so this preset converts trees to units and cannot tell you how many the site needs. § 109-189 defines a "Density factor for the site (DFS)": site acreage multiplied by 15 for Agricultural Districts, by 20 for Single Family Residential and by 30 for Commercial and all other Non-Single Family Districts, and the Guidelines § F restates the same three figures. Two independent reasons it is withheld: neither CanopyCode nor ArborCode has a units-per-acre field at all (gap register), and the value is per DISTRICT CLASS while a preset field is city-wide. Work the site target by hand: acreage x 15, 20 or 30 by district, less the units this preset's chart credits for retained trees.
• ⚠⚠ A DIFFERENT SPECIMEN TABLE GOVERNS DEVELOPED SINGLE-FAMILY RESIDENTIAL LOTS. The thresholds on this preset (27in large hardwood / 24in beech / 24in large softwood / 10in small native flowering) are the DEVELOPMENT standard, from the Guidelines' Section B. The city's same handout prints a SEPARATE and differently-drawn table under "Removal of Tree(s) on Developed Single-Family Residential Lots" — different sizes, and pine treated differently. If the work is a teardown, an addition or a removal on an already-built single-family lot rather than a land-development project, READ THAT SECTION FIRST; these numbers do not apply there. ⛔ LandCode deliberately does not carry that half of the handout, because it restates Chapter 109 Article VII in wording that has diverged from the codified text, and holding both would put one law under two citations. Get it from the city.
• A MULTI-STEM RULE EXISTS AND ITS CHART IS AN IMAGE. § 109-189 says that where a tree splits below 4 1/2 feet you "refer to chart in appendix I to the ordinance from which this section is derived"; in the current edition of the Guidelines that chart is APPENDIX G, "Multi-Trunked Tree Calculations to Determine Specimen Tree Status" — the appendix letters have shifted since the ordinance was written, so cite what the current document prints. Its method is stated in text (measure each trunk at 4.5 feet, convert to area in square inches, total them, compare to the minimum specimen size), and its DIAMETER-to-AREA table is a scanned picture we do not transcribe. Its printed notes do corroborate this preset's thresholds: 79 square inches is the area at which a native flowering tree becomes a specimen, 452 for pines and beech, 572 for most hardwoods. ⚠ Neither tool exposes a multi-stem setting, so aggregate multi-trunk trees by hand.
• ⚠ THE CITY ARBORIST MAY REQUIRE MORE GROUND THAN THIS PRESET DRAWS. Guidelines § B: "In some instances, the City Arborist or authorized agent(s) may require an additional area of no disturbance up to 10 feet outside the root protection zone." That is discretionary, so no field can carry it. Separately, protective fencing goes "a minimum of 3 feet beyond the outer edge of the root protection zone" — the fence line is outside the zone this preset computes, not on it.
• No SRP chart is published, so SRP stays disabled.
• No impact-threshold percentage ships, and the reason is that Johns Creek does not use one. Its regime is a HARDSHIP TEST, not a survivability percentage: to remove a tree in the protected zone "the owner/developer must document a hardship such as but not limited to economic or zoning restrictions" (§ 109-194(a)). ⚠ But disturbance is not free: Guidelines § C doubles a specimen tree's unit value as recompense where unpermitted disturbance of its root protection zone leaves it "less than a 50% chance of surviving for two (2) years". Neither tool has a penalty field, so that consequence is not modelled anywhere in this preset.
• NO AREAS, although the ordinance comes closer than most. The protected zone expressly includes landscape strips, zoning buffers, state water buffers, tributary buffers and tree save areas (§ 109-189) — but that makes them places where DISTURBANCE is restricted, not places where a tree is worth a different number of units. An AreaDefinition changes credit; nothing here changes credit. Modelling it as one would be our inference, not the law.
• The minimum size at which something counts as a tree at all is stated — "a trunk diameter of two inches or more measured at a point two inches above the ground level" (§ 109-189) — but neither tool has an inventory-threshold field. ⚠ Note it is measured two inches above ground, NOT at DBH, so it is not comparable to a 2-inch DBH rule elsewhere. Gap register.
• The 25-foot undisturbed perimeter buffer for timber harvesting (§ 109-193(e)) is a permit condition for one activity, not a tree-credit rule, and does not ship.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Large Hardwoods, Beech, Large Softwoods, Small Native Flowering. Without it the thresholds load but no tree is classified.

Lawrenceville, GA

• Lawrenceville states NO tree replacement or mitigation arithmetic. Article VIII requires a Tree Replacement/Protection Plan (§ 8.3, defined at § 8.2.22) but never sets a density, a replacement ratio, or a caliper-inch requirement anywhere in its 42 sections.
• The only tree-density number Lawrenceville publishes is in the ZONING ordinance, not this one, and it is scoped to a single district: § 102.11 requires Community Mixed-Use developments to meet "16 tree density units per acre". A preset field is city-wide, so shipping a district-specific figure would state it as law everywhere. Separately, neither CanopyCode nor ArborCode has a units-per-acre field at all — see docs/sibling-tool-gaps.md.
• No specimen or heritage classification exists. § 8.2 defines 25 terms and none of them is a specimen, landmark or heritage tree, so there is no threshold to set and no size at which a tree earns different treatment.
• No structural-root-plate (SRP) chart is published, so SRP stays disabled.
• § 8.2.20 sets the minimum size at which something counts as a tree at all — "a diameter at breast height of at least three (3) inches" — but neither tool has an inventory-threshold field, so it cannot ship. Gap register.
• § 8.2.10 states a MULTI-STEM measurement rule: where a tree splits below 4½ feet, the diameter is taken "at the most narrow point beneath the split". Neither tool exposes a multi-stem measurement setting, so it cannot ship. Gap register.
• The CRZ definition names only the DBH circle. There is no dripline alternative and no "whichever is greater", so the tool's default DbhMultiplier mode is already correct and nothing is emitted for it. (An absence cannot be proven by a quote, which is why this is recorded here rather than authored as a crzMode claim.)
• The buffer widths in § 8.3.2 are ZONING-DISTRICT-PAIR buffer dimensions (LM abutting single-family = 50 feet, and so on), not rules about how a tree inside them is credited. They are not AreaDefinitions and no area ships.

City of Marietta, GA

• ⚠ THE TREE DENSITY CHART CANNOT BE SHIPPED, and this is a limit of the tools, not a gap in the code. Marietta's Table E gives TWO unit values for every DBH band — one for evergreens, one for hardwoods (3-4" = 0.2 / 0.3 … 41+" = 2.5 / 7.0). Both tools' units chart holds a single value per band, and the evergreen-to-hardwood ratio is not constant across the bands (1.50, 2.00, 2.25, 2.00, 2.375, 2.333, 2.25, 2.80), so it cannot be recovered with a group multiplier either. Shipping one column would silently mis-credit every tree of the other type. Enter Table E by hand; the values were read position-true from the source PDF and are printed verbatim in § 712.08.
• The Site Density Factor of 17 density units per acre (Table D) has no field in either tool — neither models a per-acre density target. It is stated here so the number is not lost: a 2.2 acre site needs 2.2 x 17 = 37.4 units, which is the ordinance's own worked example.
• Tables F-1 and F-2 (density credit for NEWLY PLANTED trees, by caliper and by height) are replacement-planting schedules rather than survey values, and the tools' units chart is keyed to DBH only. Not modelled.
• Marietta's specimen CONDITION test (§ 712.08) is a four-part arborist judgement — life expectancy over 15 years, a relatively sound and solid trunk with no extensive decay, no more than one major and several minor dead limbs (hardwoods only), and no major insect or pathological problem. The preset can only approximate it by excluding poor and dead trees, and BOTH size and condition must be met for a tree to qualify.
• The double specimen credit is CONDITIONAL on protection actually holding: a certified arborist must verify the criteria before the land disturbance permit issues, and failure to protect the tree during construction may forfeit the additional credit and void the approved plan. No field can express that; it is a site-management obligation, not a drawing rule.
• ⚠ CanopyCode has no canopy or dripline input, so it cannot compute this jurisdiction's CRZ at all and will fall back to a DBH circle using whatever multiplier is already set. Marietta publishes no feet-per-inch multiplier, so LandCode supplies none. Use ArborCode for the protection radius here, or set the CRZ by hand from the surveyed canopy.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Large Hardwood, Large Softwood, Understory. Without it the thresholds load but no tree is classified.

City of Newnan, GA

• ⭐ TABLE 2 — CREDIT FOR EXISTING TREES (§ 10-85) IS A REAL DBH-TO-UNITS CHART and is DELIBERATELY NOT SHIPPED YET, for the same three reasons as Gainesville's and Grayson's: the rows must be extracted POSITION-TRUE from the source PDF (the flattened body interleaves FOUR diameter/units column pairs across the page), and the builder's chart check does not yet read a verified sidecar or tolerate the printed decimal forms. Enter Table 2 by hand until then. Table 3 (Credit for Replacement Trees) is a planting schedule keyed to nursery diameter, not survey DBH, and is not modelled at all.
• The site density factor has no field in either tool, and Newnan publishes TWO: § 10-85 requires a minimum of 12 units per acre for all commercial, multi-family and attached residential projects (including single-family lots under 7,500 square feet), and 8 units per acre for all industrial projects. The ordinance prints the formula itself: SDF = (total site area in acres, minus zoning buffers, stream buffers, floodplain, or delineated wetlands) x 12. Individual single-family lots of 7,500 square feet or more instead plant two shade or canopy trees each, while their subdivision's common areas must still meet the 12 units per acre.
• ⚠ THE DOUBLE SPECIMEN CREDIT IS CONDITIONAL AND THE FIELD CANNOT SAY SO. It applies to a specimen 'which [is] successfully saved by a design feature specifically designated for such purpose' (§ 10-85) — not to every specimen that survives construction. Preserving a specimen incidentally earns the ordinary Table 2 credit; earning the 2x means showing the design feature. The ordinance separately notes that increased credits can also be earned by conserving non-specimen GROUPS of trees 18 inches and larger, which has no field either.
• Only trees ten inches DBH and above count toward density (§ 10-85): 'Only trees (ten inches dbh and above) that are designated on the tree protection plan will be counted towards density requirements.' Neither tool has a minimum-countable-diameter field, so filter the survey by hand — and note this floor is unusually HIGH (Acworth and Union City count from 2 inches, Sugar Hill from 3).
• Newnan's specimen CONDITION test (§ 10-85) is an arborist judgement — a life expectancy of more than 15 years, a structurally sound trunk with no obvious hollows and no extensive decay, and less than ten percent radial trunk dieback. The preset can only approximate it by excluding poor and dead trees, and BOTH size and condition must be met for a tree to qualify.
• A smaller tree can still be a specimen, and no size rule can detect it: § 10-85 lets the city landscape architect designate a lesser-sized tree, including one 'specifically used by a builder, developer, or design professional as a focal point in a project or landscape'. There is also a separate SPECIMEN TREE STAND category — a contiguous grouping of four or more trees judged to be of high value — which is a stand-level designation the per-tree fields cannot express. Flag both by hand.
• Specimen MITIGATION is a replacement schedule, not a survey value: a removed specimen must be replaced with minimum three-inch caliper trees at a HALF-INCH FOR ONE INCH ratio, in addition to the minimum required tree density (§ 10-85). A specimen DAMAGED during construction is replaced inch-for-inch instead, and any other saved tree damaged is replaced by unit value.
• ⚠ NEWNAN PUBLISHES NO TOLERATED SHARE OF CRZ DISTURBANCE, so no impact threshold ships. Its protections are prescriptive rather than numeric: four-foot orange mesh barriers around the whole critical root zone before any land disturbance, no open trenching inside the zone (utilities must be bored, or tunnelled at 24 inches minimum depth), fill no deeper than two inches within the drip line, no grubbing in the root zone, and roots cut by hand where they cross a tree-save boundary (§ 10-85). The ordinance's own framing is that 'most trees can tolerate only a small percentage of critical root zone loss' — a statement, not a threshold.
• No structural-root-plate (SRP) chart is published in this ordinance, so SRP stays disabled.
• ⚠ THE PROTECTIVE ZONE FOR A SPECIMEN OR A TREE-SAVE AREA IS DEFINED SEPARATELY FROM THE CRZ and is dripline-only: 'the protective zone of specimen trees or stands of trees or otherwise designated tree save areas shall include no less than the total area beneath the tree(s) canopy as defined by the furthest canopy drip line' (§ 10-85). The CRZ shipped above is the greater of dripline and 1.25 ft/inch, so it is never smaller than that protective zone — but the two terms are not synonyms in this code, and a plan should label them the way the ordinance does.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Overstory Hardwood, Overstory Pine and Fast-Growing, Understory. Without it the thresholds load but no tree is classified.
• Draw a polyline for each area and name it exactly as listed above — the tools match an area to its shape by name. An area you never draw is simply ignored.

Snellville, GA

• Right-of-way trees are NOT part of the tree-density calculation here — they carry their own 1:1 replacement obligation (1 inch of caliper per inch of DBH removed) IN ADDITION to the site's required density (§ 207-4). No preset field models a separate parallel obligation. Public right-of-way and required buffers are also excluded from the site acreage itself, which no preset field can express either.
• Snellville has NO specimen-tree size threshold. A specimen tree is one the Director designates as high-value (§ 102-2), so there is no number to set — ask the city which trees are designated.
• Snellville's CRZ is the DBH circle alone — no dripline alternative is stated — so the mode stays the default DBH multiplier.
• The ordinance lets the Director adjust the root save area for documented site conditions (§ 102-2); no preset can model a case-by-case discretion.
• No structural-root-plate (SRP) chart is published, so SRP stays disabled.

City of Sugar Hill, GA

• ⭐⭐ TABLE B (§ 5.3) IS THE CORPUS'S BEST `unitsChart` CANDIDATE AND IS DELIBERATELY NOT SHIPPED YET — but for a DIFFERENT reason than Grayson's or Gainesville's, and a much smaller one. Its 48 rows (3 in at .05 units through 50 in at 13.6) were already extracted POSITION-TRUE from the source PDF during the clean-tables campaign and are stored as a verified sidecar, so the position-true requirement is ALREADY SATISFIED here. What blocks it is that the builder checks a chart against the FLATTENED body rather than against that verified sidecar, and the body prints values without a leading zero ('.05', '.6'). Reading the sidecar is the right fix and it would unblock this chart immediately. Enter Table B by hand until then.
• Table C — credit for REPLACEMENT trees, keyed to planted diameter rather than survey DBH — is a planting schedule and is not modelled. Credit is denied to new trees under 1 inch in diameter and to new trees planted in a required zoning buffer (§ 5.3.2.b).
• The tree density standard has no field in either tool: § 5.3.1 requires a Tree Density Standard of 16 Tree Density Units per acre, 'exclusive of any acreage within a zoning buffer and any trees required to be preserved or planted within a zoning buffer', and § 5.3 additionally requires each residential lot to have a minimum of two Tree Density Units. Stated here so the numbers are not lost.
• ⚠ THE SPECIMEN BONUS IS DISCRETIONARY AND A CEILING, SO IT CANNOT SHIP AS A MULTIPLIER. § 5.3.2 c(1) reads 'A total tree density credit not to exceed three (3) times the units shown on Table B, MAY be granted by the Department for existing trees to be retained which have greater value as outstanding specimen trees or having historic value or being a rare or unique species.' Both words matter: 'not to exceed' makes 3x a maximum rather than the value, and 'may be granted by the Department' makes it an official's decision. A `UnitMultiplier` field can say neither (gap register B4), and shipping 3.0 would promise every big tree a credit the city has not granted. Ask the Department, then enter it by hand.
• ⚠ AND THERE IS NO SPECIMEN SIZE THRESHOLD AT ALL. Sugar Hill never defines a specimen tree by diameter — 'outstanding specimen trees' appears only inside that discretionary credit — so no classification group ships. This is the Snellville, Duluth and Gainesville case: inventing a number would be worse than shipping none, because a designer would survey to it.
• Minimum countable size is 3 inches for existing trees (§ 5.3.2.a: 'Credit shall be given all trees preserved on a property having a diameter of 3" or more'). Diameters are measured at DBH, or below DBH for new or multi-trunked trees but never less than 6 inches from the ground, and fractions round up at 0.5 inches. A multi-trunked ornamental is credited on its single largest trunk, not the cumulative total, and tree-form shrubs earn no credit. Neither tool has a minimum-countable-diameter field, so filter the survey by hand.
• ⭐ Trees in a public street right-of-way MAY be retained or planted for credit 'if granted authorization by the Department of Transportation' (§ 5.3.1). That is the OPPOSITE of the usual right-of-way rule and is worth knowing, but it is conditional on an approval, so it is not shipped as an area.
• Encroachment is handled by consequence rather than by percentage (§ 5.4.1.c): if encroachment into a Tree Protection Area causes irreparable damage, the Tree Preservation/Replacement Plan must be revised to compensate for the loss. There is no tolerated share of disturbance to map to an impact threshold, so none ships.
• No structural-root-plate (SRP) chart is published in this ordinance, so SRP stays disabled. § 5.4.1.b requires protective fencing, staking or continuous ribbon between the protection area and disturbed ground, installed before any land disturbance and kept until final landscaping, plus silt screens up-slope.
• ⚠ CanopyCode has no canopy or dripline input, so it cannot compute this jurisdiction's CRZ and will fall back to a DBH circle using whatever multiplier is already set. Sugar Hill publishes no feet-per-inch multiplier, so LandCode supplies none. Use ArborCode for the protection radius here, or set the CRZ by hand from the surveyed canopy.

• Draw a polyline for each area and name it exactly as listed above — the tools match an area to its shape by name. An area you never draw is simply ignored.

City of Union City, GA

• The tree density standard has no field in either tool: § 9-4 requires a minimum tree density of 100 inches per acre of the entire tract being developed, calculated as a collective measurement of tree trunk diameter of existing and replacement trees — existing trees credited at DBH, replacement trees at nursery caliper. Stated here so the number is not lost.
• Only trees two inches DBH or greater may be counted (§ 9-3): 'Only existing trees with a DBH of two (2) inches or greater may be counted toward the minimum tree density.' All trees 12 inches and larger must be shown on the tree survey regardless. Neither tool has a minimum-countable-diameter field, so filter the survey by hand.
• ⚠ THE 6-FOOT CONSTRUCTION SETBACK OUTSIDE THE CRZ HAS NO FIELD, and it is the one rule here most likely to be missed on a drawing. § 9-4 A.6.b prohibits encroaching or placing solvents, material, construction machinery or temporary soil deposits 'within six (6) feet of the area outside the critical root zone' of any tree subject to preservation. Neither tool models a staging buffer beyond the CRZ, so the protection radius the preset produces is SMALLER than the area that must actually be kept clear. Draw the fence six feet out.
• A retention quota applies on top of the density standard and cannot be expressed as a per-tree rule: § 9-4 B.2 requires that 'Within the protected areas of the site at least 50 percent of all significant trees shall be preserved.'
• § 3-172 defines a separate 'Protection Area' — land outside the buildable area, required open space, the dripline area beneath retained trees, and required landscape strips or buffers. It is a SITE-PLANNING term, not a per-tree root-zone rule, so it does not change `CrzMode`; the critical root zone stays the § 3-60 one-foot-per-inch circle. Named here so it is clear the dripline language in this code was read and considered.
• Union City's specimen list has a fourth, size-less criterion: 'Any tree which has a significant historical value and can be documented through historical records or otherwise' (§ 3-203 D). No size rule can detect that; flag those by hand.
• The Tree Bank alternative (§ 9-4 C) is priced at a Monetary Compensation Value that the ordinance does NOT print — it directs the applicant to 'Contact the City Engineer for the current Monetary Compensation Value.' There is no number to ship, and inventing one would be the worst kind of guess. It is also hardship-gated and requires the Zoning Administrator's approval.
• No structural-root-plate (SRP) chart is published in this ordinance, so SRP stays disabled, and no CRZ encroachment percentage is published either — § 9-4 A.6 requires protective fencing encircling the critical root zone rather than tolerating a share of disturbance within it.

• Your tree survey needs a classification column (CanopyCode looks for “TreeType”) saying which group each tree falls in — Deciduous Canopy, Evergreen Canopy, Understory. Without it the thresholds load but no tree is classified.