06-reference/research

tampa ord 2026 49 height definition check

2026-10-24·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
home-buildtampa-zoningrs-75building-heightordinance-verification

No - Ord. No. 2026-49 Leaves the Sec. 27-43 Height Definition and the RS-75 Height Cell Untouched, So the 35-ft-From-Finished-Floor Verdict Stands

The question

"Does Tampa Ord. No. 2026-49 (adopted 2026-06-04) alter the Sec. 27-43 Height definition or the Sec. 27-156 RS-75 height cell?"

Context: [[2026-10-21-tampa-rs75-height-limit-datum]] concluded that the 35-ft RS-75 cap runs from the required finished floor (a flood-derived datum), giving the ~33 ft Sterling ridge roughly 4.5-5.5 ft of slack instead of 2.0 ft. That verdict rests entirely on the Sec. 27-43 "Height" definition as currently codified, and Municode badges both Sec. 27-43 and Sec. 27-156 as amended by an ordinance whose body it does not expose. This brief reads the ordinance body.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Direct answer: no. Ord. No. 2026-49 did not alter the Sec. 27-43 "Height" definition and did not alter the Sec. 27-156 RS-75 maximum-height cell. Its Sec. 27-43 amendment is additive by its own operative words ("amended by adding the underlined language"), and the single thing it adds is a definition of "certified recovery residence." Its Sec. 27-156 amendment operates on Table 4-1, the use schedule, while the 35 ft lives in Table 4-2, the area/height/bulk/placement schedule - two different tables inside the same code section, which is precisely the ambiguity that made the Municode caption alone insufficient. The ordinance does change a maximum height, which is why this question deserved an answer rather than an assumption, but that change is in Sec. 27-199 Table 19-2 and reaches only Channel District CD-1 and CD-2.

The parent brief's verdict survives unchanged, and no recomputation is needed. The 35 ft still runs from the required finished floor; the ~33 ft Sterling ridge still clears with roughly 4.5-5.5 ft of slack under the correct datum and 2.0 ft under the incorrect grade reading; height still is not a design constraint on this plan. The one substantive upgrade is to the verdict's confidence rather than its content: the parent brief carried an explicit conditional ("the amended text itself could not be read"), and that condition is now discharged against the ordinance body rather than its caption. The downstream recommendation is unaffected - still no redesign, still add the datum question to the Zoning Verification Letter list.

Two side effects of this ordinance do matter to the home build, neither of them about height. First, and worth the founder knowing because it changes what can be built next door rather than what he can build: Table 4-1 as amended makes certified recovery residences a permitted principal use (X) in RS-75 - by right, not by special use, subject to the new reasonable-accommodation procedure in Sec. 27-282.31, which includes a sixty-day deemed-approval default if the zoning administrator does not issue a written determination. That is a neighborhood-character fact about Sunset Park, not a constraint on 1212 S Suffolk, and it is the kind of thing that surfaces later as a surprise if nobody files it now. Second, Section 3 repeals Sec. 27-160, Special Street Setbacks, in its entirety - the whole street-by-street setback-from-centerline table is struck. A repeal can only relax a setback, never tighten one, so it cannot hurt the build; whether it helps depends on whether any street bounding the parcel was on that list, which is worth a glance when the survey is in hand. A third change, the striking of the Sec. 27-283.12(l) "EV Capable" parking requirement, applies only to developments over 50 parking spaces and is irrelevant to a single-family house.

The method lesson is the transferable part. The parent brief did the right thing by flagging the caption as insufficient instead of treating it as dispositive, and the flag was worth about forty minutes of retrieval to clear. The retrieval route that worked is worth recording: Municode 403s both WebFetch and curl and exposes ordinance captions only, but the Tampa City Council meeting record mirrors the full attachment set - agenda item, Planning Commission resolution, per-section Technical Coordinating Committee packets with underline/strikethrough, and the City Attorney's substitute-ordinance memo carrying the operative body. The amendment clauses in that body ("amended by adding the underlined language," "amended by adding underlined language and deleting the stricken language," "repealed in its entirety," "created to read as follows") are the evidence, because they state the operation performed on each section. Several of those pages were image scans with no text layer, so the sequence that worked was: download, pdftotext to map which pages carry text, render the scanned remainder to PNG, and read the images - with the bulk page-reading delegated to a sub-agent so that ten pages of scanned legal text never entered the parent context.

Why this is in the vault

This discharges the second open follow-up in [[2026-10-21-tampa-rs75-height-limit-datum]] and converts that brief's height verdict from conditional to verified, which removes the last reason the Sunset Park architect brief would need to budget for a height redesign. It also puts two previously unrecorded facts about RS-75 into the home-build file: certified recovery residences are now a by-right principal use in the district, and the Sec. 27-160 special street setbacks are repealed.

Open follow-ups

Related

Sources