Cleveland’s compact notation has to be decomposed because use, area, and height symbols route to different rules while PRO and Urban Form overlays add another path. The composite legend explains syntax, but the selected polygon and effective map-change ordinance establish the record under review. It is not an approval.
Last checked: August 7, 2026.
Begin the three-part-symbol-to-overlay route at Cleveland City Planning GIS maps, which supplies official viewer and layer inventory. Cross-check the selected geometry through Cleveland zoning guidance, the route used for code interpretation and use table. Before copying Use District, verify clevelandohio.gov CPC map page and official ZoningLegend.pdf; those markers keep the Cleveland composite legend tied to the intended jurisdiction and record period.
The 2F-B1 string must be separated before any rule is opened
Cleveland's composite label 2F-B1 is a compact instruction to conduct three different code checks. The Use District is 2F, meaning Two Family in the legend; the Area District is B; and the Height District is 1, which the legend associates with 35 feet. The hyphens preserve that Use-Area-Height order. A PRO Urban Overlay or Urban Form Overlay District adds another independent layer and must not be inferred from the composite code. The use prefix directs the user to the use-district chapter and table. The letter controls residential area or floor-area relationships rather than use. The final number directs the height inquiry and its exceptions. Cleveland analysis is therefore a decoding exercise followed by overlay screening; treating 2F-B1 as one undefined token would hide the regulatory question answered by each component.
The Cleveland composite legend table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is Use District, which may appear as 2F means Two Family; LR means Local Retail; from there, Match the prefix to the use-district chapter and use table. A blank in the three-part-symbol-to-overlay route 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 |
|---|---|---|---|---|
| Use District code component | states the mapped land-use district | 2F means Two Family; LR means Local Retail | Match the prefix to the use-district chapter and use table. | Open exact record |
| Area District code component | sets residential lot-area or floor-area relationships | B in 2F-B1 | The City notes area districts apply to residential components; do not apply B as a use code. | Open exact record |
| Height District code component | sets the numbered height tier | 1 means 35 feet; 2 means 60 feet | Check the height chapter and exceptions after decoding the number. | Open exact record |
| PRO Urban Overlay overlay | adds Pedestrian Retail Overlay standards | legend label: PRO Urban Overlay | Apply it in addition to the composite base code. | Open exact record |
| Urban Form Overlay District overlay | adds form-first siting and public-realm standards | official City label: Urban Form Overlay | Read its applicability and design provisions separately from the use table. | Open exact record |
| 2F-B1 worked code | shows the order Use-Area-Height | 2F / B / 1 | Preserve hyphenation so the three regulatory questions are not collapsed. | Open exact record |
Use, area, and height districts send the reader to different provisions
- Open the Cleveland composite legend; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the three-part-symbol-to-overlay route by copying Use District exactly as returned, including 2F means Two Family; LR means Local Retail.
- Keep Area District in a second Cleveland composite legend worksheet field because it sets residential lot-area or floor-area relationships.
- Test Height District independently, then mark its value, service layer, or documented blank in the three-part-symbol-to-overlay route.
- Give PRO Urban Overlay and every later item a separate row; never compress history, plans, and overlays into the Cleveland composite legend result.
- Attach the Cleveland composite legend lookup time to Use District, while preserving this separate currency clue: Record the viewer lookup date and then check the effective map-change ordinance; the legend explains the syntax but does not establish that a particular polygon has not changed.
- If Use District and Area District conflict, send the three-part-symbol-to-overlay route to Cleveland City Planning GIS maps and ask which use, area, height, and overlay provisions must be combined.
The Cleveland composite legend worksheet is complete only when another reader can reproduce the three-part-symbol-to-overlay route from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record which use, area, height, and overlay provisions must be combined as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: Record the viewer lookup date and then check the effective map-change ordinance; the legend explains the syntax but does not establish that a particular polygon has not changed.
PRO and Urban Form overlays add rules without rewriting the base syntax
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| Use District returns 2F means Two Family; LR means Local Retail | Compare with Area District, which sets residential lot-area or floor-area relationships | Stop the three-part-symbol-to-overlay route if Area District is missing, dated differently, or points to another record. | Continue through the Cleveland composite legend: Match the prefix to the use-district chapter and use table. Then test whether Area District changes that route. |
| Area District returns B in 2F-B1 | Compare with Height District, which sets the numbered height tier | Stop the three-part-symbol-to-overlay route if Height District is missing, dated differently, or points to another record. | Continue through the Cleveland composite legend: The City notes area districts apply to residential components; do not apply B as a use code. Then test whether Height District changes that route. |
| Height District returns 1 means 35 feet; 2 means 60 feet | Compare with PRO Urban Overlay, which adds Pedestrian Retail Overlay standards | Stop the three-part-symbol-to-overlay route if PRO Urban Overlay is missing, dated differently, or points to another record. | Continue through the Cleveland composite legend: Check the height chapter and exceptions after decoding the number. Then test whether PRO Urban Overlay changes that route. |
| PRO Urban Overlay returns legend label: PRO Urban Overlay | Compare with Urban Form Overlay District, which adds form-first siting and public-realm standards | Stop the three-part-symbol-to-overlay route if Urban Form Overlay District is missing, dated differently, or points to another record. | Continue through the Cleveland composite legend: Apply it in addition to the composite base code. Then test whether Urban Form Overlay District changes that route. |
| Urban Form Overlay District returns official City label: Urban Form Overlay | Compare with 2F-B1, which shows the order Use-Area-Height | Stop the three-part-symbol-to-overlay route if 2F-B1 is missing, dated differently, or points to another record. | Continue through the Cleveland composite legend: Read its applicability and design provisions separately from the use table. Then test whether 2F-B1 changes that route. |
| 2F-B1 returns 2F / B / 1 | Compare with Use District, which states the mapped land-use district | Stop the three-part-symbol-to-overlay route if Use District is missing, dated differently, or points to another record. | Continue through the Cleveland composite legend: Preserve hyphenation so the three regulatory questions are not collapsed. Then test whether Use District changes that route. |
Work a Cleveland legend string from left to right
Suppose a hypothetical Cleveland parcel displays 2F-B1 and also intersects the PRO Urban Overlay. The researcher copies the label with both hyphens, then separates 2F, B, and 1 into worksheet columns. The 2F prefix is matched to the Two Family use rules. B is checked under the area-district provisions and is not treated as a commercial or other use code. The final 1 is checked under the height district material, where the legend gives 35 feet, subject to the governing chapter and exceptions. PRO is then opened as the Pedestrian Retail Overlay and applied in addition to the base composite. If Urban Form Overlay is also present, its applicability and design standards are reviewed separately. The hypothetical does not conclude that the displayed height is an approval or that the base use table answers overlay-driven siting questions.
A correct legend can still be attached to an outdated polygon
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | The final numeral in 2F-B1 is read as part of the use code instead of the height district. | Preserve Height District, the selected geometry, and both timestamps from the Cleveland composite legend check. | Use Cleveland City Planning GIS maps to settle which use, area, height, and overlay provisions must be combined; then Check the height chapter and exceptions after decoding the number. |
| Scenario 2 | An Urban Form or PRO overlay is ignored because the base code already appears to answer the use question. | Preserve PRO Urban Overlay, the selected geometry, and both timestamps from the Cleveland composite legend check. | Use Cleveland City Planning GIS maps to settle which use, area, height, and overlay provisions must be combined; then Apply it in addition to the composite base code. |
If the final numeral in 2F-B1 was read as part of 2F, correct the record by restoring three columns: Use District 2F, Area District B, and Height District 1. Reopen the relevant use, area, and height provisions independently. If a PRO Urban Overlay or Urban Form Overlay was ignored because the base code looked complete, rerun the overlay layers for the same parcel geometry and add the named overlay provisions to the analysis. Preserve the viewer date and any effective map-change ordinance found. A precise question for Cleveland is: Does this parcel's current map designation remain 2F-B1, which PRO or Urban Form overlay boundaries apply, and which effective map action supports those results? Quoting the composite label and overlay names lets the agency resolve the actual record conflict without being asked to approve a use or design.
Cleveland, Ohio date check: Record the viewer lookup date and then check the effective map-change ordinance; the legend explains the syntax but does not establish that a particular polygon has not changed.
Cleveland City Planning's GIS maps establish the official viewer and layer inventory, the City zoning guidance provides the interpretation path, and the Zoning Map Legend defines the exact composite syntax. The legend can show that 1 means 35 feet or that 2 means 60 feet, but it cannot prove that the selected parcel has never been changed by a later map action. Save the viewer lookup date and retrieve the effective map-change ordinance for the polygon before material reliance. Overlay status needs the same date discipline because PRO Urban Overlay and Urban Form Overlay are not encoded inside 2F-B1. The scope boundary is also semantic: the legend explains how to parse the label, while the ordinance supplies the operative standards and exceptions. Do not let a clear legend key substitute for a current parcel-specific map determination.
The CPC map, legend PDF, and zoning guidance answer three separate questions
| Official page | What to check there | Local coverage shown |
|---|---|---|
| Cleveland City Planning GIS maps | official viewer and layer inventory | City page says the Zoning Viewer contains use, height, area, and overlays |
| Cleveland zoning guidance | code interpretation and use table | City planning zoning page explains composite codes |
| Cleveland Zoning Map Legend | exact code legend | Official City PDF gives the 2F-B1 example and district categories |
How should Use District be checked in Cleveland, Ohio?
Open the official Use District record and capture the value inside the Cleveland composite legend. That record shows how Use District states the mapped land-use district; one displayed form is 2F means Two Family; LR means Local Retail. Place the copied value in the three-part-symbol-to-overlay route, then follow its separate rule route: Match the prefix to the use-district chapter and use table.
How should Area District be checked in Cleveland, Ohio?
Open the official Area District record and capture the value inside the Cleveland composite legend. That record shows how Area District sets residential lot-area or floor-area relationships; one displayed form is B in 2F-B1. Place the copied value in the three-part-symbol-to-overlay route, then follow its separate rule route: The City notes area districts apply to residential components; do not apply B as a use code.
How should Height District be checked in Cleveland, Ohio?
Open the official Height District record and capture the value inside the Cleveland composite legend. That record shows how Height District sets the numbered height tier; one displayed form is 1 means 35 feet; 2 means 60 feet. Place the copied value in the three-part-symbol-to-overlay route, then follow its separate rule route: Check the height chapter and exceptions after decoding the number.
How to ask the zoning office about an unresolved component
- 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 Cleveland composite legend does not decide title, survey boundaries, private restrictions, vested rights, building-code compliance, utilities, licensing, or permit issuance. Request a written response when the three-part-symbol-to-overlay route leaves competing official results or when substantial reliance is planned. A useful request to Cleveland City Planning GIS maps identifies the parcel, quotes Use District and Area District, gives their source dates, and asks which use, area, height, and overlay provisions must be combined.
Use cleveland zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the three-part-symbol-to-overlay route. The Cleveland composite legend evidence linked for Use District and Area District remains the local starting point.
Reviewed August 7, 2026. Recheck the Cleveland composite legend, its cited ordinance, and the agency procedure before relying on the saved worksheet.