LandCode™ · Early access
You shouldn't have to decipher 300 pages to answer one question. Let us find it for you.
Ask it the way you'd ask a colleague: setbacks, buffers, parking, stormwater. LandCode finds the rule in plain language, cited to the adopted code and kept current, so you get the answer in seconds, with the receipt to prove it. A research tool, never legal advice.
Covering 19 metro-Atlanta jurisdictions today, and growing. For arborists, landscape architects, civil engineers, and site developers.
In action
The LandCode workspace
Minimum lot size 12,000 sq ft. Street setback 30 ft on an arterial, 20 ft otherwise.
- Lot frontage
- 80 ft, or 65 ft on a cul-de-sac
- Interior setback
- 10 ft
- Rear setback
- 30 ft
- Max building height
- 35 ft
- Max impervious surface
- 40%
Show the source
Matched to the enacted section before the answer is shown. One click opens the primary source so you can confirm it and keep the citation.
240 spaces, at 2 per dwelling unit. At least 72 of them have to sit in a side or rear yard.
- Base ratio
- 2 per dwelling unit
- Side or rear yard
- at least 30% of required spaces, in RM-6 and RM-8
- Within 250 ft of a transit stop
- 25% reduction
- Deck or underground parking
- 15% reduction
- ADA accessible spaces
- not counted toward the requirement
Show the source
One answer, four separate subsections. The ratio is in the table, the yard split and the two reductions are in the general provisions above it, and the ADA exclusion is a third. LandCode pulls them together and cites each one.
320 inches. Non-single-family sites need 100 inches per acre, so 3.2 acres x 100 = 320 inches.
- Single-family sites
- 50 inches per acre
- Counts toward it
- existing trees preserved with no impact to the CRZ, measured at DBH
- New trees
- minimum 2-inch caliper
- Shrubs
- no credit
- If the site had no trees
- the requirement still applies
Show the source
The ordinance gives the formula, not the number. LandCode runs it against your acreage and shows the section it came from, so the math on your plan matches the math the reviewer will do.
A planted area that cannot double as your setback, and it has to include a solid fence or wall at least 6 ft tall.
- Not allowed inside
- parking, or any structure other than a fence or required drainage
- Slope easement
- up to 40% may be cleared to prevent erosion
- State waters
- no encroachment within the 75 ft stream bank buffer
- Fencing
- installed before the certificate of occupancy
- Split by a street
- buffer not required, landscaping still applies
Show the source
Not every question has a single number for an answer. Where the code sets conditions instead, LandCode gives you the conditions rather than inventing a figure.
Preview of the LandCode answer view. The values are real, read from Acworth's adopted Zoning Ordinance (Chapter 73, adopted Nov 20, 2025). A research tool, not legal advice; always verify at the source.
Per-site search
One search, every rule your site has to meet
Give LandCode the site and its zoning district, and it pulls the requirements that actually apply, setbacks, buffers, tree protection, and more, each in plain language and cited to the adopted code. No more hunting across a dozen chapters.
Illustrative preview using Acworth's adopted code (as of Nov 2025). A research tool, not legal advice; always verify each citation at the source.
Where it's live
Built on the actual adopted code, not a generic chatbot
LandCode reads the enacted ordinances, parsed section by section. The full land-development code for 19 metro-Atlanta jurisdictions, over 10,800 code sections including the City of Atlanta itself, is in the corpus today, and growing every week.
- Acworth, GA
- Atlanta, GA
- Cherokee County, GA
- Dallas, GA
- Douglas County, GA
- Duluth, GA
- Fayetteville, GA
- Forsyth County, GA
- Gainesville, GA
- Grayson, GA
- Gwinnett County, GA
- Johns Creek, GA
- Lawrenceville, GA
- Marietta, GA
- Newnan, GA
- Paulding County, GA
- Snellville, GA
- Sugar Hill, GA
- Union City, GA
Don't see your area? Request your city when you join, and it moves up the build queue.
How it works
From a plain-language question to a cited answer
Three steps replace an afternoon of scrolling municipal PDFs.
- 01
Ask in plain language
Type the question the way it comes up at your desk. No section numbers, no boolean search through a PDF.
- 02
Get a cited answer
LandCode returns the rule in plain English, pulled from the adopted code, with the exact section and an 'as of' date.
- 03
Verify and move on
One click opens the primary source. You confirm it, keep the citation, and stay the professional of record.
Ask it like a person
The questions you'd normally dig through a PDF for
Why you can trust it
Accurate, cited, and honest about its limits
Cited, and checked against the source
Every answer is matched to the source section before you see it. If a value can’t be verified, you get the source, not a guess.
Dated, and labelled by source
Every answer carries an “as of” date and the state of the source behind it, published code or unofficial draft, so you always know what you are standing on.
Honest when it’s unsure
When the code is unclear, LandCode says so and points you to the city, never guessing.
A research tool, not legal advice
You stay the professional of record. LandCode shows its receipts so you can stand behind the answer.
Where every answer comes from
Every source is labelled, including the messy ones
Most code sits in a clean published database. Some of it does not. Sometimes a county hands you a preliminary red-line because the ordinance never made it online, and you still have to design to it. We take those in too, and we never let one pass as the published code. Every source carries its state and the date we last checked it.
- Official
Pulled straight from the jurisdiction’s own published code.
- Unofficial, from jurisdiction staff
A document a city or county sent us directly because it is not in their published code. Real, usable, and never passed off as published.
- Draft or red-line
A preliminary version that was never finalized. Shown when it is the only version that exists, and always flagged as draft.
- Last verified
Every jurisdiction carries the date we last checked it against its source, so you can see how fresh it is.
A label tells you where a document came from, not that it is correct. The official published source of the adopting jurisdiction always governs, so verify against it before you seal or submit. That is in our terms, and it is how we would use it ourselves.
Why it's different
Digging through PDFs vs. asking LandCode
Same question, two very different afternoons.
Be first, and put your city first.
Early access is opening to a small group of land-development firms. Tell us your city when you join, and we'll prioritize bringing it online.