A Douglas-Omaha GIS row is a checklist, not merely a zoneclass label. Its height value, PUD and PUR flags, special-district flags, direct code link, and edit date decide which Chapter 55 route and approval record must be opened. It is not an approval.
Last checked: August 7, 2026.
Begin the zoneclass-to-special-approval checklist at Douglas-Omaha GIS, which supplies parcel and map lookup. Cross-check the selected geometry through Omaha Zoning feature layer, the route used for exact zoning field schema. Before copying zoneclass, verify dcgis.org official GIS host and Hosted/Zoning_Omaha_view service; those markers keep the Douglas-Omaha GIS flag row tied to the intended jurisdiction and record period.
zoneclass reaches Chapter 55 only after the Douglas-Omaha parcel is fixed
Omaha's zoning row works as a compact escalation checklist. zoneclass gives the public classification, while zonedesc may merely repeat that code and therefore cannot be assumed to contain a full narrative. zoning_height contributes a mapped number, but its units and exceptions still come from the applicable Chapter 55 provisions. The Boolean-style pud_flag and pur_flag point toward property-specific development records when positive. md_flag and ed_flag must remain separate because a negative response in one column does not answer the other. codelink supplies a route to the zoning code, and last_edit_date records data maintenance rather than adoption. Read together, these values distinguish the base classification, a height clue, special-plan flags, overlay or district flags, the legal-text route, and data currency. The row is useful precisely because no single field carries all of those roles.
zonedesc, zoning_height, and codelink divide classification from standards
The Douglas-Omaha GIS flag row table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is zoneclass, which may appear as DR; R4; R3; from there, Open the corresponding Chapter 55 district. A blank in the zoneclass-to-special-approval checklist 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 |
|---|---|---|---|---|
| zoneclass field | stores the zoning classification | DR; R4; R3 | Open the corresponding Chapter 55 district. | Open exact record |
| zonedesc field | stores the zoning description | DR; R4; R3 in sampled rows | When it repeats the code, use the code text for the full description. | Open exact record |
| zoning_height field | stores a mapped zoning-height value | 35 | Check units, district standards, and exceptions before relying on it. | Open exact record |
| pud_flag field | flags Planned Unit Development status | No in sampled rows | When yes, retrieve the approved PUD plan and conditions. | Open exact record |
| pur_flag field | flags a PUR record | No in sampled rows | Treat it as a separate property-specific control when yes. | Open exact record |
| md_flag / ed_flag fields | flags MD or ED overlay/district records | No in sampled rows | Preserve each flag independently; one negative does not answer the other. | Open exact record |
| codelink field | links to the zoning code | Municode Chapter 55 link | Reopen the current destination because the stored URL can age. | Open exact record |
| last_edit_date field | provides a row-edit timestamp | 2018-05-30; 2023-02-22 | It is a data-maintenance clue, not the ordinance effective date. | Open exact record |
PUD, PUR, MD, and ED flags open supplemental approval records
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| zoneclass returns DR; R4; R3 | Compare with zonedesc, which stores the zoning description | Stop the zoneclass-to-special-approval checklist if zonedesc is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: Open the corresponding Chapter 55 district. Then test whether zonedesc changes that route. |
| zonedesc returns DR; R4; R3 in sampled rows | Compare with zoning_height, which stores a mapped zoning-height value | Stop the zoneclass-to-special-approval checklist if zoning_height is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: When it repeats the code, use the code text for the full description. Then test whether zoning_height changes that route. |
| zoning_height returns 35 | Compare with pud_flag, which flags Planned Unit Development status | Stop the zoneclass-to-special-approval checklist if pud_flag is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: Check units, district standards, and exceptions before relying on it. Then test whether pud_flag changes that route. |
| pud_flag returns No in sampled rows | Compare with pur_flag, which flags a PUR record | Stop the zoneclass-to-special-approval checklist if pur_flag is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: When yes, retrieve the approved PUD plan and conditions. Then test whether pur_flag changes that route. |
| pur_flag returns No in sampled rows | Compare with md_flag / ed_flag, which flags MD or ED overlay/district records | Stop the zoneclass-to-special-approval checklist if md_flag / ed_flag is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: Treat it as a separate property-specific control when yes. Then test whether md_flag / ed_flag changes that route. |
| md_flag / ed_flag returns No in sampled rows | Compare with codelink, which links to the zoning code | Stop the zoneclass-to-special-approval checklist if codelink is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: Preserve each flag independently; one negative does not answer the other. Then test whether codelink changes that route. |
| codelink returns Municode Chapter 55 link | Compare with last_edit_date, which provides a row-edit timestamp | Stop the zoneclass-to-special-approval checklist if last_edit_date is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: Reopen the current destination because the stored URL can age. Then test whether last_edit_date changes that route. |
| last_edit_date returns 2018-05-30; 2023-02-22 | Compare with zoneclass, which stores the zoning classification | Stop the zoneclass-to-special-approval checklist if zoneclass is missing, dated differently, or points to another record. | Continue through the Douglas-Omaha GIS flag row: It is a data-maintenance clue, not the ordinance effective date. Then test whether zoneclass changes that route. |
A reproducible route from DOGIS to the correct Chapter 55 section
- Open the Douglas-Omaha GIS flag row; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the zoneclass-to-special-approval checklist by copying zoneclass exactly as returned, including DR; R4; R3.
- Keep zonedesc in a second Douglas-Omaha GIS flag row worksheet field because it stores the zoning description.
- Test zoning_height independently, then mark its value, service layer, or documented blank in the zoneclass-to-special-approval checklist.
- Give pud_flag and every later item a separate row; never compress history, plans, and overlays into the Douglas-Omaha GIS flag row result.
- Attach the Douglas-Omaha GIS flag row lookup time to zoneclass, while preserving this separate currency clue: Compare last_edit_date with the current Chapter 55 supplement and any PUD/PUR approval date; these clocks answer different questions.
- If zoneclass and zonedesc conflict, send the zoneclass-to-special-approval checklist to Douglas-Omaha GIS and ask which PUD, PUR, height, or special-district record must be opened.
The Douglas-Omaha GIS flag row worksheet is complete only when another reader can reproduce the zoneclass-to-special-approval checklist from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record which PUD, PUR, height, or special-district record must be opened as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: Compare last_edit_date with the current Chapter 55 supplement and any PUD/PUR approval date; these clocks answer different questions.
A flagged parcel whose base zone and planned approval must both be read
Hypothetical Omaha record: imagine zoneclass and zonedesc both show R4, zoning_height is 35, pud_flag and pur_flag are No, md_flag and ed_flag are also No, and last_edit_date is 2023-02-22. Copying 'R4, height 35' as a final answer would skip the most important verification work. The reviewer should open the current Chapter 55 destination through codelink, identify what the number 35 means in that district, and look for exceptions before describing a height standard. Each No flag should be reported only as the returned field value. It does not establish that no other plan, case, or control affects the property. Because this is a constructed teaching example, it does not claim that any real Omaha parcel has this combination or that a 35-unit measure governs a proposal. It models the questions generated by the schema.
last_edit_date, code supplement, and planned approval keep three clocks
Omaha and Douglas County, Nebraska date check: Compare last_edit_date with the current Chapter 55 supplement and any PUD/PUR approval date; these clocks answer different questions.
Omaha exposes at least three clocks that should never be merged. last_edit_date states when a data row was edited. The current Chapter 55 supplement states which codified text the reader can see now. A PUD, PUR, MD, or ED record can carry its own approval or amendment date. An older row can still be correct, and a newer edit can still describe an older legal action. Record the Omaha row date without presenting it as the zoning's effective date. If a flag is positive, retrieve the corresponding approval and compare its date and conditions with the current code. If every sampled flag is negative, stay within the narrower conclusion that the service returned No for those columns. Those field values cannot certify that the current Omaha development envelope has no additional constraints.
What to retain when codelink or a district flag is stale
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | A 'No' PUD flag is treated as proof that no other plan or overlay applies. | Preserve zoning_height, the selected geometry, and both timestamps from the Douglas-Omaha GIS flag row check. | Use Douglas-Omaha GIS to settle which PUD, PUR, height, or special-district record must be opened; then Check units, district standards, and exceptions before relying on it. |
| Scenario 2 | zoning_height 35 is quoted without confirming units or district exceptions. | Preserve pud_flag, the selected geometry, and both timestamps from the Douglas-Omaha GIS flag row check. | Use Douglas-Omaha GIS to settle which PUD, PUR, height, or special-district record must be opened; then When yes, retrieve the approved PUD plan and conditions. |
When an Omaha result quotes zoning_height 35 without units or announces that all special controls are absent because pud_flag is No, reopen the row before polishing the prose. Preserve zoneclass, test zonedesc for actual descriptive content, and inspect pud_flag, pur_flag, md_flag, and ed_flag one at a time. Follow codelink to the current Chapter 55 text, then retain last_edit_date as a separate metadata value. If the meaning of 35 or a blank flag remains uncertain, contact the zoning office with the parcel and exported record. Ask: 'For this parcel and zoneclass R4, what unit and rule does zoning_height 35 represent, and do the current records identify any PUD, PUR, MD, or ED control not shown by these flag values?' The question requests a field interpretation and missing-record check, not an assurance that construction is allowed.
| Official page | What to check there | Local coverage shown |
|---|---|---|
| Douglas-Omaha GIS | parcel and map lookup | Official joint GIS portal |
| Omaha Zoning feature layer | exact zoning field schema | Official dcgis.org hosted service |
| Omaha zoning ordinance Chapter 55 | controlling code | Official codified ordinance publication linked by the GIS data |
How should zoneclass be checked in Omaha and Douglas County, Nebraska?
Open the official zoneclass record and capture the value inside the Douglas-Omaha GIS flag row. That record shows how zoneclass stores the zoning classification; one displayed form is DR; R4; R3. Place the copied value in the zoneclass-to-special-approval checklist, then follow its separate rule route: Open the corresponding Chapter 55 district.
How should zonedesc be checked in Omaha and Douglas County, Nebraska?
Open the official zonedesc record and capture the value inside the Douglas-Omaha GIS flag row. That record shows how zonedesc stores the zoning description; one displayed form is DR; R4; R3 in sampled rows. Place the copied value in the zoneclass-to-special-approval checklist, then follow its separate rule route: When it repeats the code, use the code text for the full description.
How should zoning_height be checked in Omaha and Douglas County, Nebraska?
Open the official zoning_height record and capture the value inside the Douglas-Omaha GIS flag row. That record shows how zoning_height stores a mapped zoning-height value; one displayed form is 35. Place the copied value in the zoneclass-to-special-approval checklist, then follow its separate rule route: Check units, district standards, and exceptions before relying on it.
- 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 Douglas-Omaha GIS flag 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 zoneclass-to-special-approval checklist leaves competing official results or when substantial reliance is planned. A useful request to Douglas-Omaha GIS identifies the parcel, quotes zoneclass and zonedesc, gives their source dates, and asks which PUD, PUR, height, or special-district record must be opened.
Use omaha douglas zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the zoneclass-to-special-approval checklist. The Douglas-Omaha GIS flag row evidence linked for zoneclass and zonedesc remains the local starting point.
Reviewed August 7, 2026. Recheck the Douglas-Omaha GIS flag row, its cited ordinance, and the agency procedure before relying on the saved worksheet.