Building a public zoning lookup map residents can actually use

Reference article · 6 min read

Planning counters absorb a steady volume of the same question, asked in different words: can I build a garage here, can I rent the back unit, can I open a small shop in this storefront. Staff answer it by pulling up the parcel, identifying the zoning district, checking overlays, and reading the ordinance. A public zoning lookup map is an attempt to hand residents the first part of that answer directly, without simply exposing a general-purpose GIS viewer and expecting the public to interpret it.

The difference between a map that reduces call volume and one that increases it is trust. A resident who gets an answer they cannot verify, or who cannot tell how old the underlying data is, calls anyway, and now calls with a screenshot. The design goal is a page a homeowner, a contractor, or an agent can read on a phone, understand in a few seconds, and describe accurately when they do reach staff.

Start from the parcel, not the map

Most residents do not want to pan a map. They want to type an address. Treat the search box as the front door and the map as supporting evidence.

Address and APN in one field. Accept both, plus partial addresses, and show disambiguation when a match is uncertain rather than silently picking the closest one.
Handle the hard cases. Condominium units, multi-parcel sites, newly split parcels, and addresses that are not yet in the assessor file all need a defined behavior, including a clear message when there is no match.
Make results shareable. Every parcel result should have a stable permalink so a resident can send it to a contractor and staff can open the exact page the caller is looking at.
Support map entry too. Some people only know where the property is, so clicking a parcel should produce the same result page as searching for it.

What belongs on the parcel answer page

Order the page by what the reader came for. Lead with the plain-language answer, then the supporting detail.

Zoning district and overlays. Name them, expand the abbreviations, and state plainly that an overlay may add or remove what the base district allows.
A use answer in ordinary words. A short list of common uses with permitted, conditional, or not permitted, written for a general reader. Conditional should say what that process involves.
Dimensional standards summary. Setbacks, height limits, lot coverage, and parking, with a note that measurement rules and exceptions live in the ordinance.
What this page does not decide. Flood zones, historic designation, easements, private covenants, nonconforming status, and open enforcement cases are common surprises. Naming them prevents a false sense of completeness.

Keep the summaries tied to the ordinance

The most common failure mode is a set of friendly summaries written once, pasted into a content management system, and then left behind when the ordinance is amended. Avoid hand-maintained copies.

Store district and overlay standards as structured records, one authoritative record per district, with an effective date and a citation to the ordinance section it derives from. The map renders those records rather than storing its own text. Give planning staff, not IT, the ability to edit the records through a reviewed workflow, and keep a change history so anyone can see what the page said on a given day. When the ordinance is amended, the update is one edit that propagates to every page that uses it. The same records can feed the permitting intake system, which removes a second copy that would otherwise drift.

Accessibility, mobile performance, and plain language

Accessibility is not a later phase. The U.S. Department of Justice has adopted a technical standard for web content and mobile apps under Title II of the ADA for state and local governments, with compliance timelines that vary by entity size, and many states impose their own requirements. Confirm current obligations with your counsel and your state's accessibility office.

Provide a non-map path. Everything the map conveys must be available as text on the result page, reachable by keyboard and readable by a screen reader.
Do not rely on color alone. Zoning maps are color-heavy by tradition. Labels, patterns, and text results carry the meaning.
Budget for slow devices and cellular. Serve simplified geometry or vector tiles, do not load a jurisdiction-wide parcel layer into the browser, and run the point-in-polygon lookup on the server. Test on an older phone on a weak connection, not on office wifi.
Write for a general reader. Short sentences, expanded acronyms, and translations for the languages your jurisdiction serves.

Disclaimers and data currency the reader can see

Put the disclaimer next to the answer, not in the footer. It should say that the information is for general reference, that it is not a zoning verification or a determination, and that the ordinance controls if they differ. Beside it, show a data currency date for each source: the parcel layer, the zoning layer, and the ordinance version. Then give the reader the next step, including how to request an official written determination, what it costs, and roughly how long it takes.

Log what people could not find

Search logs are the cheapest research your planning department will ever get.

Record searches that returned nothing, geocode failures, districts viewed most often, and sessions that ended without reaching a result.
Add a short feedback control on the result page asking whether the reader found their answer.
Review the log with counter staff on a regular cycle and use it to decide which uses and which districts need clearer summaries.
Decide retention and privacy up front. Collect no more than you need, avoid storing personal information, and remember that logs may be subject to public records law.

What to ask vendors and how to start

Where are the plain-language summaries stored, who edits them, and how does an ordinance amendment reach the public page?
Provide an accessibility conformance report and the results of testing with assistive technology, not just an automated scan.
How does parcel and zoning data refresh from our authoritative source, and what happens when that feed fails?
What are the performance targets on a mid-range phone, and how are they measured?
Can the same lookup run as an API that our permitting and code enforcement systems call?
On exit, do we keep the data, the configuration, and the summary records in a usable format?

Start narrow. Inventory the questions your counter actually receives for a month, launch with the districts and uses that dominate that list, and expand once the summaries hold up. HQT builds and integrates public-facing GIS and permitting applications for state and local agencies, including work of this kind.

Frequently asked questions

Does publishing a zoning lookup map create legal exposure for the jurisdiction?

Most jurisdictions publish these tools with a clear statement that the results are informational, that they are not a zoning verification or determination, and that the adopted ordinance and official map control. The practical protections are a visible disclaimer placed next to the answer, a data currency date, a version history showing what the page said on a given date, and an easy path to request an official written determination. Liability rules vary by state and by local ordinance, so confirm the wording with your jurisdiction's counsel before launch.

How do we keep the plain-language zoning summaries from going stale after an ordinance amendment?

Store the standards as structured records, one per district or overlay, each carrying an effective date and a citation to the ordinance section it comes from, and have the public page render those records rather than separately written copy. Give planning staff a reviewed workflow for editing them so updates do not require an IT ticket. Add the summary update to the checklist your department already uses when an amendment is adopted, and keep a change log so anyone can reconstruct what the page displayed on a given day.

Should a public zoning map replace zoning verification letters?

No. The map answers the common preliminary question quickly, while a zoning verification letter is a reviewed, signed determination that lenders, title companies, and businesses often require. The map should say plainly that it does not replace that determination and should show how to request one, including the fee and typical turnaround. Many agencies find the map reduces routine calls while verification letter requests stay roughly the same.

What accessibility requirements apply to a public zoning map on a city website?

State and local government web content and mobile apps are covered by Title II of the ADA, and the U.S. Department of Justice has adopted a technical standard with compliance timelines that differ by entity size. Many states add their own requirements and procurement language. In practice, that means the parcel result must be fully usable as text by keyboard and screen reader, color cannot be the only way zoning is conveyed, and vendor accessibility claims should be backed by testing with assistive technology. Confirm current obligations with your counsel.

What should we log when residents use the zoning lookup?

Log searches that returned no result, geocoding failures, the districts and uses viewed most often, and sessions that ended before a result was reached, plus a short feedback prompt on the result page. Review this with counter staff on a regular cycle to decide which summaries need rewriting. Decide retention and privacy in advance, collect no more than necessary, avoid personal information, and account for the possibility that the logs are public records in your state.