The Licensing_Zoning service prevents Oklahoma City’s straight zoning from being confused with overlay points, overlay parcels, or non-zoning parcel actions. Keep USERCODE and ORDNUM with the matching geometry, then trace the relevant action to its case and effective ordinance. It is not an approval.
Last checked: August 7, 2026.
Begin the straight-zone-versus-parcel-action split at Oklahoma City subdivision and zoning, which supplies official map and process entry. Cross-check the selected geometry through OKC Licensing and Zoning feature service, the route used for exact zoning layer inventory. Before copying Overlay Point Zoning (layer 0), verify AGOL_Content_OKC publisher and OpenData/Licensing_Zoning service; those markers keep the Licensing_Zoning service tied to the intended jurisdiction and record period.
Non-Zoning Parcels are a stop signal, not an empty district
Oklahoma City's service separates categories that are easy to collapse in a screenshot. Straight Zoning is layer 3 and supplies the base geography. Overlay Parcel Zoning in layer 1 adds parcel-shaped supplemental coverage, while Overlay Point Zoning in layer 0 records point-style overlay information that should not automatically be stretched across an entire tax parcel. Non-Zoning Parcels in layer 2 is a different record family; a class such as CE and description Closed Easement describes an action, not a district. Within that layer, USERCODE can preserve the full identifier, such as CE-464, and ORDNUM may supply an ordinance number. A careful lookup starts with layer 3, tests the parcel against layers 1 and 0, and logs layer 2 separately. This order keeps a case identifier, ordinance reference, overlay, and base district from being presented as interchangeable answers to 'what is the zoning?'
Point overlay, parcel overlay, and straight zoning use different geometry
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| Overlay Point Zoning (layer 0) returns layer ID 0 | Compare with Overlay Parcel Zoning (layer 1), which stores parcel-shaped overlay zoning | Stop the straight-zone-versus-parcel-action split if Overlay Parcel Zoning (layer 1) is missing, dated differently, or points to another record. | Continue through the Licensing_Zoning service: Use it as a supplemental record and confirm its governing ordinance. Then test whether Overlay Parcel Zoning (layer 1) changes that route. |
| Overlay Parcel Zoning (layer 1) returns layer ID 1 | Compare with Non-Zoning Parcels (layer 2), which stores mapped non-zoning actions such as closed easements | Stop the straight-zone-versus-parcel-action split if Non-Zoning Parcels (layer 2) is missing, dated differently, or points to another record. | Continue through the Licensing_Zoning service: Reconcile it with Straight Zoning rather than replacing the base district. Then test whether Non-Zoning Parcels (layer 2) changes that route. |
| Non-Zoning Parcels (layer 2) returns sample class CE; description Closed Easement | Compare with Straight Zoning (layer 3), which stores the base zoning geography | Stop the straight-zone-versus-parcel-action split if Straight Zoning (layer 3) is missing, dated differently, or points to another record. | Continue through the Licensing_Zoning service: Do not report this layer as a zoning designation. Then test whether Straight Zoning (layer 3) changes that route. |
| Straight Zoning (layer 3) returns layer ID 3 | Compare with USERCODE, which stores the full case identifier in the non-zoning layer | Stop the straight-zone-versus-parcel-action split if USERCODE is missing, dated differently, or points to another record. | Continue through the Licensing_Zoning service: Use this as the starting district before overlays. Then test whether USERCODE changes that route. |
| USERCODE returns CE-464; CE-367 | Compare with ORDNUM, which stores an ordinance number when supplied | Stop the straight-zone-versus-parcel-action split if ORDNUM is missing, dated differently, or points to another record. | Continue through the Licensing_Zoning service: Use it to retrieve the action record, not to classify zoning. Then test whether ORDNUM changes that route. |
| ORDNUM returns 21029 | Compare with Overlay Point Zoning (layer 0), which stores point-style overlay zoning records | Stop the straight-zone-versus-parcel-action split if Overlay Point Zoning (layer 0) is missing, dated differently, or points to another record. | Continue through the Licensing_Zoning service: Check the ordinance's subject, adoption, and legal description. Then test whether Overlay Point Zoning (layer 0) changes that route. |
USERCODE and ORDNUM connect an OKC polygon to its action
The Licensing_Zoning service table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is Overlay Point Zoning (layer 0), which may appear as layer ID 0; from there, Use it as a supplemental record and confirm its governing ordinance. A blank in the straight-zone-versus-parcel-action split 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 |
|---|---|---|---|---|
| Overlay Point Zoning (layer 0) layer | stores point-style overlay zoning records | layer ID 0 | Use it as a supplemental record and confirm its governing ordinance. | Open exact record |
| Overlay Parcel Zoning (layer 1) layer | stores parcel-shaped overlay zoning | layer ID 1 | Reconcile it with Straight Zoning rather than replacing the base district. | Open exact record |
| Non-Zoning Parcels (layer 2) layer | stores mapped non-zoning actions such as closed easements | sample class CE; description Closed Easement | Do not report this layer as a zoning designation. | Open exact record |
| Straight Zoning (layer 3) layer | stores the base zoning geography | layer ID 3 | Use this as the starting district before overlays. | Open exact record |
| USERCODE field | stores the full case identifier in the non-zoning layer | CE-464; CE-367 | Use it to retrieve the action record, not to classify zoning. | Open exact record |
| ORDNUM field | stores an ordinance number when supplied | 21029 | Check the ordinance's subject, adoption, and legal description. | Open exact record |
Choose the matching geometry before following the ordinance number
- Open the Licensing_Zoning service; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the straight-zone-versus-parcel-action split by copying Overlay Point Zoning (layer 0) exactly as returned, including layer ID 0.
- Keep Overlay Parcel Zoning (layer 1) in a second Licensing_Zoning service worksheet field because it stores parcel-shaped overlay zoning.
- Test Non-Zoning Parcels (layer 2) independently, then mark its value, service layer, or documented blank in the straight-zone-versus-parcel-action split.
- Give Straight Zoning (layer 3) and every later item a separate row; never compress history, plans, and overlays into the Licensing_Zoning service result.
- Attach the Licensing_Zoning service lookup time to Overlay Point Zoning (layer 0), while preserving this separate currency clue: The hosted service can show recent edit metadata, but each overlay or non-zoning action must be tied to its own case and ordinance effective date.
- If Overlay Point Zoning (layer 0) and Overlay Parcel Zoning (layer 1) conflict, send the straight-zone-versus-parcel-action split to Oklahoma City subdivision and zoning and ask whether an overlay or non-zoning action changed the parcel record.
The Licensing_Zoning service worksheet is complete only when another reader can reproduce the straight-zone-versus-parcel-action split from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record whether an overlay or non-zoning action changed the parcel record as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: The hosted service can show recent edit metadata, but each overlay or non-zoning action must be tied to its own case and ordinance effective date.
A point feature over land that is outside the expected zoning layer
Consider a hypothetical Oklahoma City map check in which Straight Zoning layer 3 returns a base district, Overlay Point Zoning layer 0 places a marker nearby, and Non-Zoning Parcels layer 2 returns class CE with USERCODE CE-464 and ORDNUM 21029. The worksheet should record four things independently: the unnamed hypothetical base result from layer 3, the point location from layer 0, the absence or presence of parcel geometry in layer 1, and the closed-easement record from layer 2. It should not call CE-464 the zoning or assume the point covers the full parcel. The ordinance number is a retrieval clue, so the next step is to read its subject and legal description. This invented exercise makes no claim about a real address, the contents of ordinance 21029, or whether an overlay applies; it only demonstrates the service's category boundaries and the evidence needed before drawing that conclusion.
Recent service edits cannot substitute for case and ordinance effect
Oklahoma City, Oklahoma date check: The hosted service can show recent edit metadata, but each overlay or non-zoning action must be tied to its own case and ordinance effective date.
A recent edit timestamp on Oklahoma City's hosted service tells the reader when data was maintained, not when every mapped action became legally effective. Straight zoning, an overlay, and a closed-easement record can each originate in different proceedings and ordinances. The presence of ORDNUM in a non-zoning row does not date the base district, and an overlay point does not reveal the effective geography of a parcel overlay. For Oklahoma City, keep layers 0 through 3 separate and use USERCODE and ORDNUM to retrieve the underlying action. Do not convert the service refresh into a citywide legal effective date. When timing matters, save the map query date, retrieve the action tied to the relevant layer, and compare its ordinance and legal description with the current Subdivision and Zoning guidance.
Resolve a service-area or non-zoning mismatch with the correct OKC office
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | Non-Zoning Parcels layer 2 is mistaken for current base zoning. | Preserve Non-Zoning Parcels (layer 2), the selected geometry, and both timestamps from the Licensing_Zoning service check. | Use Oklahoma City subdivision and zoning to settle whether an overlay or non-zoning action changed the parcel record; then Do not report this layer as a zoning designation. |
| Scenario 2 | An overlay point is treated as covering the whole tax parcel without checking layer 1 geometry and Straight Zoning. | Preserve Straight Zoning (layer 3), the selected geometry, and both timestamps from the Licensing_Zoning service check. | Use Oklahoma City subdivision and zoning to settle whether an overlay or non-zoning action changed the parcel record; then Use this as the starting district before overlays. |
If an Oklahoma City note labels CE-367 or CE-464 as a zoning district, discard that conclusion and return to the layer names. Confirm the base polygon in Straight Zoning layer 3, inspect Overlay Parcel Zoning layer 1, and measure any layer 0 point against the selected parcel rather than assuming full coverage. Keep the layer 2 USERCODE and ORDNUM as references to a non-zoning action. A geometry conflict should be sent to the City's planning staff with the parcel key, layer IDs, case value, ordinance value, and lookup date. Ask: 'For this parcel, what is the current Straight Zoning designation, does the point or parcel overlay legally cover the selected geometry, and is USERCODE CE-464 solely a closed-easement record rather than zoning?' This wording exposes the exact category problem and lets the agency identify the controlling record without being asked to approve a project.
| Official page | What to check there | Local coverage shown |
|---|---|---|
| Oklahoma City subdivision and zoning | official map and process entry | City planning page |
| OKC Licensing and Zoning feature service | exact zoning layer inventory | OKC OpenData service |
| Oklahoma City zoning districts | district definitions | Official city page |
How should Overlay Point Zoning (layer 0) be checked in Oklahoma City, Oklahoma?
Open the official Overlay Point Zoning (layer 0) record and capture the value inside the Licensing_Zoning service. That record shows how Overlay Point Zoning (layer 0) stores point-style overlay zoning records; one displayed form is layer ID 0. Place the copied value in the straight-zone-versus-parcel-action split, then follow its separate rule route: Use it as a supplemental record and confirm its governing ordinance.
How should Overlay Parcel Zoning (layer 1) be checked in Oklahoma City, Oklahoma?
Open the official Overlay Parcel Zoning (layer 1) record and capture the value inside the Licensing_Zoning service. That record shows how Overlay Parcel Zoning (layer 1) stores parcel-shaped overlay zoning; one displayed form is layer ID 1. Place the copied value in the straight-zone-versus-parcel-action split, then follow its separate rule route: Reconcile it with Straight Zoning rather than replacing the base district.
How should Non-Zoning Parcels (layer 2) be checked in Oklahoma City, Oklahoma?
Open the official Non-Zoning Parcels (layer 2) record and capture the value inside the Licensing_Zoning service. That record shows how Non-Zoning Parcels (layer 2) stores mapped non-zoning actions such as closed easements; one displayed form is sample class CE; description Closed Easement. Place the copied value in the straight-zone-versus-parcel-action split, then follow its separate rule route: Do not report this layer as a zoning designation.
- 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 Licensing_Zoning service does not decide title, survey boundaries, private restrictions, vested rights, building-code compliance, utilities, licensing, or permit issuance. Request a written response when the straight-zone-versus-parcel-action split leaves competing official results or when substantial reliance is planned. A useful request to Oklahoma City subdivision and zoning identifies the parcel, quotes Overlay Point Zoning (layer 0) and Overlay Parcel Zoning (layer 1), gives their source dates, and asks whether an overlay or non-zoning action changed the parcel record.
Use oklahoma city zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the straight-zone-versus-parcel-action split. The Licensing_Zoning service evidence linked for Overlay Point Zoning (layer 0) and Overlay Parcel Zoning (layer 1) remains the local starting point.
Reviewed August 7, 2026. Recheck the Licensing_Zoning service, its cited ordinance, and the agency procedure before relying on the saved worksheet.