Use this field guide after you have selected the correct parcel in Tulsa’s official GIS. It explains how ZONE_TYPE, LEGEND, ZCASE_NUM, ORDINANCE, ACRES, COUNTY, and maintenance dates fit together. If you still need to find the parcel or confirm the map point, start with the Tulsa zoning map by address guide. Field values help trace the record, but they do not approve a proposed use or replace the current ordinance.
Do not use a field value until the parcel matches
Compare the address, parcel outline, county, and acreage before using a case or ordinance field to explain the property. A neighboring geometry can carry a different district or legal history even when the map labels appear close together.
Last checked: August 7, 2026.
Begin the county-and-acreage-to-ordinance chain at Tulsa GIS maps, which supplies official map entry. Cross-check the selected geometry through Tulsa Zoning open-data layer, the route used for exact zoning field schema. Before copying ZONE_TYPE, verify CityofTulsaGIS publisher and TulsaZoning_OpenData service; those markers keep the TulsaZoning_OpenData row tied to the intended jurisdiction and record period.
COUNTY confirms the Tulsa parcel before ZONE_TYPE is read
Tulsa's record connects a public code with several audit clues. ZONE_TYPE is the exact district identifier, such as AG, OL, or IM. LEGEND expands the family to Agriculture, Office, or Industrial, but cannot replace the code. ZCASE_NUM supplies a case route, and ORDINANCE may contain more than one identifier that must be untangled rather than copied as one adoption. ACRES is calculated geometry, useful for detecting a selection problem but not a surveyed boundary. COUNTY records a county value, which does not independently prove City of Tulsa zoning jurisdiction. created_date and last_edited_date belong to service maintenance, not ordinance adoption. Read together, the fields support a chain from code to legend, case, legal actions, geometry, and jurisdiction. The chain breaks if the friendly legend is published without ZONE_TYPE or if a service timestamp is substituted for the ordinance history.
ZCASE_NUM and ORDINANCE connect the parcel to legal action
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| ZONE_TYPE returns AG; OL; IM | Compare with LEGEND, which expands the district family | Stop the county-and-acreage-to-ordinance chain if LEGEND is missing, dated differently, or points to another record. | Continue through the TulsaZoning_OpenData row: Open the matching Tulsa zoning code district. Then test whether LEGEND changes that route. |
| LEGEND returns Agriculture; Office; Industrial | Compare with ZCASE_NUM, which stores the zoning case number | Stop the county-and-acreage-to-ordinance chain if ZCASE_NUM is missing, dated differently, or points to another record. | Continue through the TulsaZoning_OpenData row: Use it to cross-check, not replace, ZONE_TYPE. Then test whether ZCASE_NUM changes that route. |
| ZCASE_NUM returns Z-7616 | Compare with ORDINANCE, which stores one or more ordinance identifiers | Stop the county-and-acreage-to-ordinance chain if ORDINANCE is missing, dated differently, or points to another record. | Continue through the TulsaZoning_OpenData row: Retrieve the case and final action when populated. Then test whether ORDINANCE changes that route. |
| ORDINANCE returns 136641, 24709 in a sampled row | Compare with ACRES, which stores calculated acreage | Stop the county-and-acreage-to-ordinance chain if ACRES is missing, dated differently, or points to another record. | Continue through the TulsaZoning_OpenData row: Determine which ordinance applies and whether a later action superseded it. Then test whether ACRES changes that route. |
| ACRES returns 185.59; 1.36; 5.62 | Compare with COUNTY, which states the county recorded for the feature | Stop the county-and-acreage-to-ordinance chain if COUNTY is missing, dated differently, or points to another record. | Continue through the TulsaZoning_OpenData row: Use acreage as a geometry clue, not proof of a surveyed boundary. Then test whether COUNTY changes that route. |
| COUNTY returns Tulsa | Compare with created_date / last_edited_date, which provide service-edit clues | Stop the county-and-acreage-to-ordinance chain if created_date / last_edited_date is missing, dated differently, or points to another record. | Continue through the TulsaZoning_OpenData row: County name does not by itself establish city zoning jurisdiction. Then test whether created_date / last_edited_date changes that route. |
| created_date / last_edited_date returns timestamps present in the service | Compare with ZONE_TYPE, which stores the zoning code | Stop the county-and-acreage-to-ordinance chain if ZONE_TYPE is missing, dated differently, or points to another record. | Continue through the TulsaZoning_OpenData row: Do not call them ordinance adoption dates. Then test whether ZONE_TYPE changes that route. |
Keep LEGEND, ACRES, and edit timestamps beside the selected geometry
The TulsaZoning_OpenData row table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is ZONE_TYPE, which may appear as AG; OL; IM; from there, Open the matching Tulsa zoning code district. A blank in the county-and-acreage-to-ordinance chain stays visible so another reader can distinguish an empty official return from an unexamined field.
| Local field, layer, or record | What it does | Displayed value or scope | Next code or record check | Official page |
|---|---|---|---|---|
| ZONE_TYPE field | stores the zoning code | AG; OL; IM | Open the matching Tulsa zoning code district. | Open exact record |
| LEGEND field | expands the district family | Agriculture; Office; Industrial | Use it to cross-check, not replace, ZONE_TYPE. | Open exact record |
| ZCASE_NUM field | stores the zoning case number | Z-7616 | Retrieve the case and final action when populated. | Open exact record |
| ORDINANCE field | stores one or more ordinance identifiers | 136641, 24709 in a sampled row | Determine which ordinance applies and whether a later action superseded it. | Open exact record |
| ACRES field | stores calculated acreage | 185.59; 1.36; 5.62 | Use acreage as a geometry clue, not proof of a surveyed boundary. | Open exact record |
| COUNTY field | states the county recorded for the feature | Tulsa | County name does not by itself establish city zoning jurisdiction. | Open exact record |
| created_date / last_edited_date fields | provide service-edit clues | timestamps present in the service | Do not call them ordinance adoption dates. | Open exact record |
A reproducible Tulsa chain from parcel boundary to ordinance
- Open the TulsaZoning_OpenData row; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the county-and-acreage-to-ordinance chain by copying ZONE_TYPE exactly as returned, including AG; OL; IM.
- Keep LEGEND in a second TulsaZoning_OpenData row worksheet field because it expands the district family.
- Test ZCASE_NUM independently, then mark its value, service layer, or documented blank in the county-and-acreage-to-ordinance chain.
- Give ORDINANCE and every later item a separate row; never compress history, plans, and overlays into the TulsaZoning_OpenData row result.
- Attach the TulsaZoning_OpenData row lookup time to ZONE_TYPE, while preserving this separate currency clue: The hosted service edit timestamp and ORDINANCE values should be logged separately; one measures dataset maintenance and the other points to legal action.
- If ZONE_TYPE and LEGEND conflict, send the county-and-acreage-to-ordinance chain to Tulsa GIS maps and ask whether the selected geometry belongs to the intended parcel and county.
The TulsaZoning_OpenData row worksheet is complete only when another reader can reproduce the county-and-acreage-to-ordinance chain from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record whether the selected geometry belongs to the intended parcel and county as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: The hosted service edit timestamp and ORDINANCE values should be logged separately; one measures dataset maintenance and the other points to legal action.
What happens when the acreage or county value points to adjacent land
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | LEGEND='Office' is reported without the exact OL code. | Preserve ZCASE_NUM, the selected geometry, and both timestamps from the TulsaZoning_OpenData row check. | Use Tulsa GIS maps to settle whether the selected geometry belongs to the intended parcel and county; then Retrieve the case and final action when populated. |
| Scenario 2 | Two ordinance numbers in one row are quoted without establishing which is current or what each changed. | Preserve ORDINANCE, the selected geometry, and both timestamps from the TulsaZoning_OpenData row check. | Use Tulsa GIS maps to settle whether the selected geometry belongs to the intended parcel and county; then Determine which ordinance applies and whether a later action superseded it. |
When a Tulsa summary says merely 'Office zoning' or lists two ordinances without explanation, restore the underlying row. Pair LEGEND with ZONE_TYPE OL, retrieve ZCASE_NUM, and read each ordinance independently. Confirm City jurisdiction instead of relying on COUNTY, and use ACRES only to test whether the selected feature seems plausible. Label created_date and last_edited_date as service metadata. If the legal sequence remains unresolved, send the zoning case, ordinance values, and parcel reference to Development Services. Ask: 'For this feature, is OL the current City of Tulsa district, what did ordinances 136641 and 24709 each change, and does case Z-7616 or a later action supersede either result?' The response can establish the record sequence. It should not be paraphrased as an agency guarantee of acreage, ownership, or development eligibility.
A zoning case that edits the record after the ordinance date
Hypothetical Tulsa worksheet: ZONE_TYPE is OL, LEGEND is Office, ZCASE_NUM is Z-7616, ORDINANCE contains 136641 and 24709, ACRES is 1.36, and COUNTY is Tulsa. A careful reading keeps OL as the code and Office as its cross-checking family, then retrieve the zoning case and investigate what each ordinance changed. The acreage could help spot an obvious geometry mismatch, but it would not be promoted to a survey. The county value would remain a jurisdiction clue until city coverage is confirmed. This hypothetical combination does not assert that a real parcel has this row, that both ordinances remain operative, or that an office use is allowed. created_date and last_edited_date, if present, would be recorded separately from both ordinance identifiers because they describe the hosted feature's maintenance.
Tulsa, Oklahoma date check: The hosted service edit timestamp and ORDINANCE values should be logged separately; one measures dataset maintenance and the other points to legal action.
Tulsa rows can carry several dates and numbers that look comparable but are not. An ordinance identifier points toward a legal action; ZCASE_NUM points toward the proceeding; created_date and last_edited_date show when the hosted record was created or maintained. A new edit can correct geometry without adopting new zoning, and an old ordinance can remain relevant after a service refresh. When ORDINANCE contains two values, do not guess that the larger or newer-looking number controls. Retrieve both Tulsa actions and ask what each changed. The open-data row is not a title opinion or survey, so ACRES and COUNTY should retain their limited roles. For current reliance, compare the exact ZONE_TYPE with the current code and case history, then preserve the service timestamps as metadata only.
Use GIS Maps, OpenData, and the zoning office to resolve identity
| Official page | What to check there | Local coverage shown |
|---|---|---|
| Tulsa GIS maps | official map entry | City-owned map portal |
| Tulsa Zoning open-data layer | exact zoning field schema | CityofTulsaGIS service |
| Tulsa zoning | code and agency guidance | Official city page |
How should ZONE_TYPE be checked in Tulsa, Oklahoma?
Open the official ZONE_TYPE record and capture the value inside the TulsaZoning_OpenData row. That record shows how ZONE_TYPE stores the zoning code; one displayed form is AG; OL; IM. Place the copied value in the county-and-acreage-to-ordinance chain, then follow its separate rule route: Open the matching Tulsa zoning code district.
How should LEGEND be checked in Tulsa, Oklahoma?
Open the official LEGEND record and capture the value inside the TulsaZoning_OpenData row. That record shows how LEGEND expands the district family; one displayed form is Agriculture; Office; Industrial. Place the copied value in the county-and-acreage-to-ordinance chain, then follow its separate rule route: Use it to cross-check, not replace, ZONE_TYPE.
How should ZCASE_NUM be checked in Tulsa, Oklahoma?
Open the official ZCASE_NUM record and capture the value inside the TulsaZoning_OpenData row. That record shows how ZCASE_NUM stores the zoning case number; one displayed form is Z-7616. Place the copied value in the county-and-acreage-to-ordinance chain, then follow its separate rule route: Retrieve the case and final action when populated.
- Selected parcel key, geometry, and responsible jurisdiction
- Every returned value from the local field table
- Page titles, URLs, lookup times, and update clues
- Opened code, plan, case, ordinance, or metadata records
- Unresolved blanks, boundary splits, dates, and competing outputs
- Proposed activity stated in code-relevant facts
- Agency contact, narrow question, reply date, and limits
The TulsaZoning_OpenData row does not decide title, survey boundaries, private restrictions, vested rights, building-code compliance, utilities, licensing, or permit issuance. Request a written response when the county-and-acreage-to-ordinance chain leaves competing official results or when substantial reliance is planned. A useful request to Tulsa GIS maps identifies the parcel, quotes ZONE_TYPE and LEGEND, gives their source dates, and asks whether the selected geometry belongs to the intended parcel and county.
Use tulsa zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the county-and-acreage-to-ordinance chain. The TulsaZoning_OpenData row evidence linked for ZONE_TYPE and LEGEND remains the local starting point.
Reviewed August 7, 2026. Recheck the TulsaZoning_OpenData row, its cited ordinance, and the agency procedure before relying on the saved worksheet.