Built from draft minutes printed in an agenda packet — no AI-written textBriefing final
The City's record
What the City's record shows
Draft minutes printed in the City's agenda packet of 2026-10-07, pp. 8–12; approval not found in the records on file (the meeting that received these draft minutes was 2026-10-07).
Built only from this meeting's draft minutes (2537_10_07_2026_Agenda_Packet.pdf, packet pp. 8–12). Page numbers are the minutes' own. Discussion is in the minutes' text; it is not summarised here.
Attendance (the roll call)
Listed present when the roll was taken: Marcus Wheeler, Tamisha Findlay, Susan Milhoan, Victoria Jones, Russell Sengel, Todd Anderson, Aleck Greenwood, Richard Cravens
(Checked against the ballots and the printed roll lines; no independent membership list of this board is available to confirm that the roll is complete.)
Listed absent: Wesley Park, Ron Chabot
Also listed as present (staff and other roles): Kristin Eick (City Attorney), Luci Ribeiro (City Planner), Breanna Earley (Recording Secretary)
Named on at least one ballot later in the meeting: Anderson, Cravens, Findlay, Greenwood, Jones, Milhoan, Sengel, Wheeler (participation, which can differ from the roll: arrivals and departures are in the minutes' text)
Adopted actions (5)
to APPROVE THE SEPTEMBER 2, 2026 AGENDA AND THE MINUTES OF AUGUST 5, 2026 AS WRITTEN (moved by JONES, seconded by ANDERSON); PASSED 8-0; ayes: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens; nays: none — the draft minutes, packet pp. 8–12
to POSTPONE BOTH ITEMS TO A DATE CERTAIN OF OCTOBER 7, 2026, AT 6PM AT 65 STONE STREET, COCOA, FL 32922 (moved by WHEELER, seconded by JONES); PASSED 8-0; ayes: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens; nays: none — the draft minutes, packet pp. 8–12
to APPROVE WITH STAFF RECOMMENDATIONS (moved by ANDERSON, seconded by GREENWOOD); PASSED 8-0; ayes: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens; nays: none — the draft minutes, packet pp. 8–12
to APPROVE WITH STAFF RECOMMENDATIONS (moved by FINDLAY, seconded by ALTERNATE MEMBER GREENWOOD); PASSED 8-0; ayes: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens; nays: none — the draft minutes, packet pp. 8–12
to ADJOURN THE MEETING (moved by ANDERSON, seconded by FINDLAY); PASSED 8-0; ayes: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens; nays: none — the draft minutes, packet pp. 8–12
Draft minutes, as printed in a later agenda packet
Draft minutes printed in the City's agenda packet of 2026-10-07, pp. 8–12; approval not found in the records on file (the meeting that received these draft minutes was 2026-10-07).
MINUTES
CITY OF COCOA
PLANNING & ZONING BOARD/ LOCAL PLANNING AGENCY
REGULAR MEETING
September 2, 2026
A Regular meeting of the Planning & Zoning Board Local Planning Agency
was held on September 2, 2026, at City Hall, 65 Stone Street, Cocoa, FL, as
publicly noted.
I. CALL TO ORDER:
Vice Chair Wheeler called the meeting to order at 6:00 PM.
ROLL CALL:
Wesley Park Chairperson
Marcus Wheeler Vice Chairperson
Ron Chabot Board Member
Tamisha Findlay Board Member
Susan Milhoan Board Member
Victoria Jones Board Member
Russell Sengel Board Member
Todd Anderson Board Member
Aleck Greenwood Alternate Board Member
Richard Cravens Alternate Board Member
Kristin Eick City Attorney
PRESENT:
Marcus Wheeler Vice Chairperson
Tamisha Findlay Board Member
Susan Milhoan Board Member
Victoria Jones Board Member
Russell Sengel Board Member
Todd Anderson Board Member
Aleck Greenwood Alternate Board Member
Richard Cravens Alternate Board Member
Kristin Eick City Attorney
ABSENT:
Wesley Park Chairperson
Ron Chabot Board Member
STAFF PRESENT:
Luci Ribeiro, City Planner; and Breanna Earley, Recording Secretary.
Planning & Zoning Board
Regular Meeting
September 2, 2026
Page 2 of 5
Vice Chair Wheeler led the assembly in the Pledge of Allegiance.
II. Approval of Agenda and Minutes:
1. Agenda: Regular Meeting of September 2, 2026
2. Minutes: Regular Meeting of August 5, 2026
* MOTION BY BOARD MEMBER JONES ; SECONDED BY BOARD MEMBER
ANDERSON TO APPROVE THE SEPTEMBER 2, 2026 AGENDA AND THE
MINUTES OF AUGUST 5, 2026 AS WRITTEN.
AYES: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens
MOTION PASSED UNANIMOUSLY (8-0).
III. Old Business:
IV. New Business:
1. PZ 25 -00500006 Ord No. 05 -2026 Small -Scale Comp Plan Amendment 3600 Grissom
Parkway (POSTPONED)
2. PZ 25 -00900014 Ord No. 06 -2026 Zoning Map Amendment 3600 Grissom Parkway
(POSTPONED)
* MOTION BY VICE CHAIR WHEELER ; SECONDED BY BOARD MEMBER
JONES TO POSTPONE BOTH ITEMS TO A DATE CERTAIN OF OCTOBER 7,
2026, AT 6PM AT 65 STONE STREET, COCOA, FL 32922.
AYES: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens
MOTION PASSED UNANIMOUSLY (8-0).
1. PZ 26-00200003 Ordinance No. 13-2026, Zoning Text Amendment Sec. 5 – RU-2-15,
Multiple-Family Dwelling District.
Ms. Ribeiro provided a presentation for Ordinance No. 13-20261.
Board Member Sengel asked if this would create unconforming use.
Ms. Ribeiro clarified that it would not change use.
1 Exhibit A: PZ 26-00200003 Ordinance No. 13-2026, Zoning Text Amendment Presentation
Planning & Zoning Board
Regular Meeting
September 2, 2026
Page 3 of 5
Board Member Sengel stated that if there is a piece of property that is nonconforming, it
should be brought to the Board’s attention.
Ms. Ribeiro stated there are properties that have a density issue.
Vice Chair Wheeler asked if there are any current plans being reviewed.
Alternate Member Greenwood inquired about a townhome project on Dixon Blvd.
Board Attorney Eick clarified they are single family homes.
* MOTION BY BOARD MEMBER ANDERSON ; SECONDED BY BOARD
MEMBER GREENWOOD TO APPROVE WITH STAFF
RECOMMENDATIONS.
AYES: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens
MOTION PASSED UNANIMOUSLY (8-0).
2. PZ 26-00500004 Ordinance No. 14-2026 – Comp Plan Amendment Amending Figure
FLU-1
Ms. Ribeiro provided a presentation for Ordinance 14-2026.2
Board member Anderson asked for clarification on the item.
Ms. Ribeiro explained this would remove an inconsistency.
Alternate Member Cravens asked about height restrictions in RU-225.
City Attorney Eick noted it was four stories.
Board Member Sengel asked about nonconforming properties being created.
In response, Ms. Ribeiro stated that in her research she found nonconformities with density
issues but this would not alleviate or create any more issues.
* MOTION BY BOARD MEMBER FINDLAY ; SECONDED BY ALTERNATE
MEMBER GREENWOOD TO APPROVE WITH STAFF
RECOMMENDATIONS.
AYES: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens
2 Exhibit B: PZ 26-00500004 Ordinance No. 14-2026 – Comp Plan Amendment Presentation
Planning & Zoning Board
Regular Meeting
September 2, 2026
Page 4 of 5
MOTION PASSED UNANIMOUSLY (8-0).
V. Tree Board:
Alternate Member Greenwood asked if there was an update on the trees that were removed.
Ms. Ribeiro explained that she needed to investigate it and that staff was reviewing.
A discussion on the removed trees was held.
Ms. Ribeiro detailed city code and process.
Alternate Member Greenwood asked about a site plan for the property.
Ms. Ribeiro stated that to her knowledge, the trees were on private property.
Board Attorney Eick stated it is the Code Enforcement Board’s responsibility to levy fines
for violations.
Board Member Jones asked if the owners were aware there was a violation.
Ms. Ribeiro explained that the owners came forward to try and comply.
Board Member Jones asked if information is provided to property owners to ensure they’re
following city code.
Ms. Ribeiro stated no.
Board Member Milhoan wanted clarification on the process of tree removal.
Board Attorney Eick explained if the trees are mitigated, their permit would be approved.
VI. Next Meeting Date: Wednesday, October 7, 2026, at 6:00pm, at 65 Stone Street, Cocoa,
FL 32922.
VII. Adjournment:
* MOTION BY BOARD MEMBER ANDERSON ; SECONDED BY BOARD
MEMBER FINDLAY TO ADJOURN THE MEETING.
AYES: Wheeler, Findlay, Jones, Sengel, Anderson, Milhoan, Greenwood, Cravens
MOTION PASSED UNANIMOUSLY (8-0).
MEETING ADJOURNED AT 6:55 PM.
______________________________
Wesley Park, Chairperson
Planning & Zoning Board
Regular Meeting
September 2, 2026
Page 5 of 5
Respectfully Submitted By:
______________________________________
Breanna Earley, Recording Secretary
Agenda (the City's wording)
Time links are automatic matches to the machine transcript and may be off.
An item without a time link may still have been discussed; the link is only added when the automatic match is strong.
I. Opening Matters
1. Call to Order
2. Invocation
3. Pledge of Allegiance
4. Roll Call
II. Approval of Agenda and Minutes
1. Agenda: Regular Meeting of September 2, 2026.
2. Minutes: Regular Meeting of August 5, 2026.
III. Old Business
IV. New Business
1. 3600 Grissom Prkwy Rezoning (POSTPONED)
2. 3600 Grissom Pkway Comp Plan Amendment (POSTPONED)
3. Ordinance 13-2026 - City Initiated Zoning Text Amendment - RU 2-15
4. Ordinance 14-2026 - Large-Scale Comp Plan Text Amendment to amend Figure FLU-1 — 00:23:36
V. Tree Board
VI. Other Business
VII. Next Meeting Date: Wednesday, October 7th, 2026, at 6:00 pm at 65 Stone Street in Cocoa, FL.
VIII. Adjournment
Transcript Partial transcript
Machine transcription of the meeting recording. The words are the recognizer's, except where a passage is marked as corrected or machine re-recognized; most have
not been checked against the audio, so words, numbers and names can be misheard.
It describes what was said. It cannot establish who voted how, an amount or an outcome — the City's
minutes do that (above).
A time links to its passage, and “Copy link” copies that link. “▶ Play” opens the recording at that moment, as the City's file, in a new tab.
224 suspect passage(s) marked in place.
How this transcript was made. New machine transcription of the whole recording, with 10 voices separated from the audio.
18 short machine repair(s) (20 word(s)) are labelled in place, with the original words beside them: an ordinary word was replaced only where two further machine readings agreed on a different one.
Checks run on this transcript: the recognizer's own warning signs, whether a voice was detected where the words are and a language review for likely mishearings.
A second, independent machine reading was compared with it word by word: the same words for 90.8% of 7,460 content words.
Dotted words (166 places) are ordinary wording differences: hover or tap to see the other reading.
224 passages (29% of the words) are marked suspect: their words are not shown ("unclear audio") and support no statement: numbers, amounts, negation or names differ; the language review questioned them; or no voice was detected there.
Agreement between two machine readings is not verification.
Speakers were separated by voice. A plain name rests on evidence tied to that voice; “provisional” is a name from an earlier text-only pass and is not verified; “Speaker N” is an unidentified voice.
All right. It is now 6 o'clock p.m. If we're ready to call this meeting to order. So if we could please, we have line ‸ item number two, which is normally not on our agenda item, which is the
Flag: words were replaced by a machine repair · 00:00:31–00:00:32 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
before we begin our meeting today, we fall to acknowledge your goodness and our dependence on you. Grant the leaders in this room, wisdom, discernment, and a deep sense of justice. Help us to serve our community with humility and compassion. We ask these things in your almighty name. Amen. ‸ If
Flag: words were replaced by a machine repair · 00:00:56–00:00:56 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
pledge allegiance to the flag of the United States of America and to the republic for which it stands, one nation, under God, indivisible, with liberty and justice for all.
Flag: numbers, amounts, negation or names differ between the machine readings · 00:01:28–00:01:29 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:01:34–00:01:35 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:01:54–00:01:57 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:02:12–00:02:15 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:02:16–00:02:17 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:02:18–00:02:20 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:02:33–00:02:35 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: the recognizer flagged its own output; a language review questioned the wording · 00:02:50–00:02:52 · unresolved: the words are not shown (unclear audio); listen to the recording
we have a motion. We have a second. So we'll call it. All in favor? Aye. Moving on to old business, as we don't have any existing old business, we will move on to item number four. Item number four is new business.
Flag: numbers, amounts, negation or names differ between the machine readings · 00:03:15–00:03:17 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:03:17–00:03:18 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:03:18–00:03:21 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:03:25–00:03:26 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:03:55–00:04:23 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:04:28–00:04:30 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: words were replaced by a machine repair · 00:04:31–00:04:31 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings · 00:04:34–00:04:37 · unresolved: the words are not shown (unclear audio); listen to the recording
to make certain clarifying amendments related to townhome residential divisions, providing the repeal prior inconsistency ordinance and resolutions. So there are two issues being addressed tonight. The first issue
Flag: numbers, amounts, negation or names differ between the machine readings · 00:04:54–00:04:58 · unresolved: the words are not shown (unclear audio); listen to the recording
in paragraph BB that remain after the city consolidated its landscaping and tree regulations in 2020. Also, it removes ambiguity caused by the RU225 district cross-reference to the RU215 townhouse provisions when a project is located within the waterfront overlay. So this amendment clarifies which standards apply and avoids project by project interpretation, does not change the underlying zoning, future lane use designation, or allowable density. This is a city initiated housekeeping item and coordination amendment.
Flag: numbers, amounts, negation or names differ between the machine readings · 00:05:48–00:05:53 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:05:55–00:05:57 · unresolved: the words are not shown (unclear audio); listen to the recording
a single contagious area, but is distributed across several locations throughout the city. The map properties are primarily located along or near the US1 North Cocoa Boulevard corridor
Flag: numbers, amounts, negation or names differ between the machine readings · 00:06:09–00:06:11 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:06:12–00:06:17 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:06:24–00:06:27 · unresolved: the words are not shown (unclear audio); listen to the recording
including areas near University Lane and North Cocoa Boulevard. Under the Cocoa Waterfront Overlay District, the underlying RU225 zoning is located in the Uptown neighborhood area
south of the village. So when we look at the land development, we consider the zoning classification of a parcel, the future lane use designation, and the applicable overlay sub-district. The underlying zoning remains in place, but the waterfront overlay forms-based standards controls where applicable. So this table from the Cocoa Waterfront Overlay District shows the permitted uses by sub-district andunderlaying zoning district. The highlighted column showed that
within portions of the waterfront overlay, including the Uptown neighborhood and south of the village sub-districts, as mentioned. Under the residential section of the table, single-family attached dwellings or townhomes are permitted
Flag: numbers, amounts, negation or names differ between the machine readings · 00:07:33–00:07:35 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:07:46–00:07:50 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:07:50–00:07:58 · unresolved: the words are not shown (unclear audio); listen to the recording
Unlike a conventional zoning district that primarily regulates development through uses and standard dimensional requirements, the Waterfront Overlay uses a form-based approach. The regulating plan identifies the types and forms of building appropriate for each sub-district, based on the desired development pattern. As shown here, the overlay includes a specific townhouse building type, and
Flag: words were replaced by a machine repair · 00:08:37–00:08:37 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
are identified as an allowable building form in several sub-districts, including Heart of Cocoa, King Wheeler Corridor, Uptown Neighborhood, South of the Village,
Flag: numbers, amounts, negation or names differ between the machine readings · 00:08:48–00:08:50 · unresolved: the words are not shown (unclear audio); listen to the recording
This is relevant to Ordinance 13-2026 because the Waterfront Overlay does not simply identify townhouses as a permitted residential use. It also establishes a specific form-based framework for how the townhome development is intended to occur.
Flag: numbers, amounts, negation or names differ between the machine readings · 00:09:07–00:09:13 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:09:13–00:09:16 · unresolved: the words are not shown (unclear audio); listen to the recording
alongside these overlay requirements can create two distinct regulatory frameworks for the same development. Ordinance 13-2026 clarifies that within the Waterfront Overlay, the overlays adopted form-based standards governs the townhome townhouse building type, rather than also applying the conventional townhouse
Flag: numbers, amounts, negation or names differ between the machine readings · 00:09:40–00:09:44 · unresolved: the words are not shown (unclear audio); listen to the recording
That cross-reference is why the RU-215 townhouse provisions are relevant in RU-225. And it is also the regulatory overlap that Ordinance 13-2026 is intended to clarify.
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:10:14–00:10:22 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:10:29–00:10:38 · unresolved: the words are not shown (unclear audio); listen to the recording
for two different sets of development standards to apply on the same property or development. So to help illustrate, this table compares the conventional townhouse standards
Flag: numbers, amounts, negation or names differ between the machine readings · 00:10:55–00:10:59 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:11:00–00:11:04 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:11:10–00:11:12 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:11:23–00:11:29 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:11:30–00:11:32 · unresolved: the words are not shown (unclear audio); listen to the recording
a comparable one acre minimum. The conventional standards also generally require larger lots with lots areas between 2,000 and 2,400 square feet and lots width between 20 and 28 feet. The overlay allows smaller townhouse lots, beginning approximately 16 square feet and 15 feet in width. There are also differences in setbacks
Flag: words were replaced by a machine repair · 00:11:59–00:11:59 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: words were replaced by a machine repair · 00:12:05–00:12:06 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
a 25-foot rear setback. The overlay allows a zero-foot side setback for attached units and a 15-foot rear setback, which supports the compact development pattern intended for the Waterfront Overlay. Lot coverage is another significant difference. The RU-215 townhouse standards allow a maximum lot coverage of 40% while the Waterfront Overlay allows up to 60%. The two systems also regulate height in parking differently. RU-215 establishes a maximum height of 35 feet
Flag: numbers, amounts, negation or names differ between the machine readings · 00:12:44–00:12:46 · unresolved: the words are not shown (unclear audio); listen to the recording
unit. The overlay regulates height by building type and places greater emphasis on the location of parking within the site. So the issue is not that one set of standards is ‸ necessarily better than the other. The issue is that applying both set of standards to the same townhouse development can create conflicting requirements. Ordinance 13-2026 resolves the conflict by clarifying that within the Cocoa Waterfront overlay, the overlay's form-based townhouse standards
Flag: numbers, amounts, negation or names differ between the machine readings · 00:13:18–00:13:23 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:13:28–00:13:30 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:13:51–00:13:54 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:13:57–00:14:03 · unresolved: the words are not shown (unclear audio); listen to the recording
consolidated ‸ its landscaping, tree protection, replacement, and mitigation ‸ requirements through ordinance 12-2020. This amendment removes that obsolete and potentially duplicated language. The second issue is the regulatory overlap
Flag: numbers, amounts, negation or names differ between the machine readings · 00:14:25–00:14:29 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:14:30–00:14:34 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:14:35–00:14:38 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:14:47–00:14:49 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:15:13–00:15:17 · unresolved: the words are not shown (unclear audio); listen to the recording
In addition to the overlay standards could interfere with that intent development pattern, and in some cases prevent townhouse developments on parcels where the overlay specifically allowed that building type. within the waterfront overlay,
Flag: numbers, amounts, negation or names differ between the machine readings · 00:15:37–00:15:40 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:15:40–00:15:45 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:15:55–00:15:58 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:16:03–00:16:07 · unresolved: the words are not shown (unclear audio); listen to the recording
where it currently exists. The amendment also does not change any future land use designation or increase density. All development remains subject to the applicable comprehensive plan density limits and other requirements of the zoning ordinance. For this reason, staff finds that the amendment is justified because it removes obsolete language, eliminates regulatory ambiguity, and allows the waterfront overlays adopted
Flag: words were replaced by a machine repair · 00:16:41–00:16:42 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings · 00:17:27–00:17:31 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:17:31–00:17:40 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:17:44–00:17:47 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:18:13–00:18:14 · unresolved: the words are not shown (unclear audio); listen to the recording
Yeah, in general, it relaxes things versus, you know, being more constrained in the overlaying district is what I'm getting out of this. And that's correct.
I'm just, I just want to go on record that if there's, if there's a piece of property or something out there that is nonconforming, we should know about that ahead of time. And so we don't run into the issues like we
Flag: numbers, amounts, negation or names differ between the machine readings · 00:18:34–00:18:36 · unresolved: the words are not shown (unclear audio); listen to the recording
so ‸ the next item ordinance 14, 2026 is actually to fix this inconsistency because there is an inconsistency in the south of the village between the future lane use and the zoning. And I'm going to address that on the next item.
it could affect is just the density. So the density for that area is going to be cap of 15 dwelling units and I'm, you're going to see on my next PowerPoint presentation. So for right now, development cannot occur because of the future
Flag: words were replaced by a machine repair · 00:19:16–00:19:16 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
use conflict. So this is, is just not only, um, we're not proposing only to fix that conflict between the future lane use and the zoning, but also clean some of the language in the conflict between the zoning regulation and the overlay regulation. Okay.
Okay. Um, and then just to add, since we were talking about that, there are properties under the south of the village that do have a density issue. So it's not going to fix their problem, but it's just going to allow for new redevelopment for the vacant lots.
And I'll ask, are there any current plans currently presented before the city regarding these existing, um, I would just say properties that were presented to us?
Flag: words were replaced by a machine repair · 00:20:32–00:20:32 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
just because we're being nice. We're doing it because there has to be some attachment to it to make relevant sense. So that's, that's the behind the curtain view. So now that we know the behind the curtain, there is something that is, that is prevalent. That's pushing this. What we're trying to do is just remove ‸ inconsistency. So this project has the potential to move forward.
Thank you. Um, this is a simple question. It's a reference to the project that's being planned on the corner of Dixon and River Road. The group of townhomes that are supposed to be built there. Is that still on and going?
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:21:33–00:21:34 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:21:36–00:21:36 · unresolved: the words are not shown (unclear audio); listen to the recording
misunderstood from the drawings, I thought, because it's been a while and I was just curious. My question was going to be if ‸ this, the changes here would affect that project and obviously it's not.
Flag: words were replaced by a machine repair · 00:22:08–00:22:08 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings · 00:22:18–00:22:19 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:22:19–00:22:21 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:22:22–00:22:24 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output; a language review questioned the wording · 00:22:29–00:22:38 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output; a language review questioned the wording · 00:22:40–00:22:54 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:22:57–00:23:08 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:23:17–00:23:22 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:23:22–00:23:26 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:23:49–00:23:53 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:23:53–00:24:01 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:24:28–00:24:34 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:24:38–00:24:42 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:24:54–00:24:59 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:25:14–00:25:21 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:25:24–00:25:28 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:25:29–00:25:34 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:25:44–00:25:50 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:25:51–00:25:56 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:26:04–00:26:16 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:26:23–00:26:27 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:26:40–00:26:46 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:26:50–00:26:55 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: words were replaced by a machine repair · 00:26:56–00:26:56 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
changes As I showed before as you can see under the waterfront overlay sub districts There are you two to five it is an allow zoning district for the uptown neighborhood as well as for the south of the village So just to give a little bit of a background for the waterfront redevelopment framework
walk about walkability riverfront connectivity and neighborhood character The plan recommended a farm base overlay tailored to different waterfront sub districts
Flag: numbers, amounts, negation or names differ between the machine readings · 00:27:39–00:27:46 · unresolved: the words are not shown (unclear audio); listen to the recording
sub district The over the overlay regulates development through a regulating plan and building types writer than conventional zoning standards alone as
Flag: numbers, amounts, negation or names differ between the machine readings · 00:27:57–00:28:00 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:28:00–00:28:05 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:28:15–00:28:19 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: words were replaced by a machine repair · 00:28:20–00:28:20 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:28:27–00:28:43 · unresolved: the words are not shown (unclear audio); listen to the recording
the applicable goals objectives and policies of the comprehensive plan So just to be clear Every new development still has to go through a review process
Flag: numbers, amounts, negation or names differ between the machine readings · 00:29:28–00:29:33 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: words were replaced by a machine repair · 00:29:35–00:29:36 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: words were replaced by a machine repair · 00:29:41–00:29:41 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:29:41–00:29:50 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:30:04–00:30:19 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:30:19–00:30:20 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:30:21–00:30:29 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:30:54–00:30:56 · unresolved: the words are not shown (unclear audio); listen to the recording
I wouldn't say give it the option but it's just to fix the inconsistency. Because now we cannot approve site plan development for that area because of the inconsistency.
or redevelopment, we have to check, we use the future land use element under the comp plan as a reference for zoning, what is permitted under the future land use designation. And now that area with the south of
Flag: numbers, amounts, negation or names differ between the machine readings · 00:31:31–00:31:34 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:31:42–00:31:46 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:31:46–00:31:49 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:31:49–00:31:58 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:32:03–00:32:08 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:32:15–00:32:16 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:32:21–00:32:26 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:32:32–00:32:39 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:32:47–00:32:50 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:32:54–00:32:59 · unresolved: the words are not shown (unclear audio); listen to the recording
Well so to go back to that topic so the properties there are a few properties because I did I did a research on that area and there are a few properties that do have a density issue. So they are nonconforming with our code, but this is not going to solve or make their issue even worse.
Flag: numbers, amounts, negation or names differ between the machine readings · 00:33:42–00:33:42 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:33:44–00:33:49 · unresolved: the words are not shown (unclear audio); listen to the recording
‸ Yes because of the density and also now I'm thinking that there are a few properties that have some unique layout. They have like multi-family buildings in a single family in the same lot. So they're like, the code does not even allow that type of development. So there are some nonconformities in that area, but with this amendment, is not going to solve or or make the issue worse than what it is right now.
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:34:49–00:34:53 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output · 00:34:56–00:35:00 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:35:30–00:35:31 · unresolved: the words are not shown (unclear audio); listen to the recording
Alec made the motion the last time he made a motion there was an issue because he's an alternate. He can't make the motion. ‸ I remember. Well we have two board members missing. So he can do it now? Okay. Yeah. Okay.
Flag: numbers, amounts, negation or names differ between the machine readings · 00:36:11–00:36:11 · unresolved: the words are not shown (unclear audio); listen to the recording
right. Any opposed? So the motion passes unanimously. All right, let's get back to our next line item. So we're now to our most prolific item of the night.
Flag: the recognized words and the detected speech do not line up · 00:36:11–00:36:24 · gap filled by a machine re-reading (not checked by a person)
Flag: the recognized words and the detected speech do not line up · 00:36:25–00:36:30 · unresolved: the words are not shown (unclear audio); listen to the recording
the recognition. I had a simple question if there's anything new we can bring up in reference to the abundance of oak trees that were cut down, on, 520 one of the businesses there. Is anything else has developed?
Well, it's not so much the inches I was just curious if they're still in the process of trying to correct the removal of the trees that were not done for the permit
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:37:19–00:37:28 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:37:40–00:37:43 · unresolved: the words are not shown (unclear audio); listen to the recording
business came forward. He did submit an application and after the fat application for a tree removal So now it's just matter of me issuing the report for them and the code enforcement and then to see what the next steps are
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:38:01–00:38:05 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:38:11–00:38:13 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: words were replaced by a machine repair · 00:38:19–00:38:19 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings · 00:38:45–00:38:46 · unresolved: the words are not shown (unclear audio); listen to the recording
they are in violation because they're all especially trees. So they are in violation. So Actually would it be the opposite if the trees were in the right-of-way
yeah Well in our code we do have language that exempt single-family residential So if there is an existing single-family home in a lot they are allowed to cut the trees without ‸ our permission But if he's a
Flag: numbers, amounts, negation or names differ between the machine readings · 00:39:41–00:39:45 · unresolved: the words are not shown (unclear audio); listen to the recording
to build a single-family home Then they will have to comply with our code and mitigate those trees on site before they build a home But after that that home is already, you know
Flag: numbers, amounts, negation or names differ between the machine readings · 00:39:56–00:39:59 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:40:15–00:40:18 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:40:19–00:40:21 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:40:28–00:40:32 · unresolved: the words are not shown (unclear audio); listen to the recording
there's no Now is an after-the-fact permit. There's already a violation established, right? So the permit is an after-the-fact they still have to pay fines.
It depends what they're proposing because they are required to mitigate those trees So they have to replant so when someone proposes to remove on a specimen tree or oak tree or They have to show How what is the plan for replacement?
so and then if there is no For some reason there's no space on site, you know on the on the property There's no location for those trees for some reason then they have to pay into the arbor mitigation fund They will make a payment a contribution Before they can get a permit
Okay, so this is just like going in reverse they're ‸ gonna ‸ end up doing all that anyways They were there there's a process in which they could take those trees down. I'm not saying yes or no I'm just saying that there is a process
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:42:01–00:42:06 · unresolved: the words are not shown (unclear audio); listen to the recording
know, the city's property and they were And that's I think that's why we are all in an uproar about the size of these trees and how many were taken down Okay, I understand it better now
Flag: numbers, amounts, negation or names differ between the machine readings · 00:42:26–00:42:29 · unresolved: the words are not shown (unclear audio); listen to the recording
anything like that because I think that'll satisfy the concern that Russell had brought up because I I remember the city planting those trees So I'd like to see a survey or something Because there's a conflict here Whether it's a
Flag: numbers, amounts, negation or names differ between the machine readings · 00:43:08–00:43:11 · unresolved: the words are not shown (unclear audio); listen to the recording
it's D.O.T The city has an ordinance D.O.T. don't they have to sort of work with the city ordinance as well on On the the guidelines of how we want the landscaping along our major arteries?
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output; a language review questioned the wording · 00:43:34–00:43:38 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:44:11–00:44:17 · unresolved: the words are not shown (unclear audio); listen to the recording
I mean, I'll just say that the the Code enforcement board is the board that really has the jurisdiction to deal with the violation. So right, I mean I suppose that we could present it But again, you know this this board is not going to impose penalties or anything like that So well,
Flag: the recognizer flagged its own output; a language review questioned the wording · 00:44:58–00:45:02 · unresolved: the words are not shown (unclear audio); listen to the recording
were at present The reality is this they're gone. We've identified that to be the first fact The second fact that we've not identified is that we as this board being the tree board We did go through a fervent conversation in our last meeting to
Flag: numbers, amounts, negation or names differ between the machine readings · 00:45:39–00:45:42 · unresolved: the words are not shown (unclear audio); listen to the recording
the circumference of these trees would be will be the findings towards What these types of scopes would be towards whether they would be mitigated and what these fines ‸ would be
ordinance and and what we have the ability to do towards finding It's not going to change it at this point. So it's well fortunate But the reality is all they're going to do is mitigate the trees or
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:46:32–00:46:35 · unresolved: the words are not shown (unclear audio); listen to the recording
My question was Were the owners aware that they were committing a violation like it was there a part of like a response or anything like that once they were notified
Flag: words were replaced by a machine repair · 00:46:51–00:46:51 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
for compliance to try to comply But the only thing that I know is that the trees were causing damage to the cars. That was the reason given so If they were aware of our I'm not ‸ I'm not sure ‸ they knew
now is there any types of notices or information that is sent out to uh business owners Especially if they own property to let them know about these sorts of ordinances So if you have new businesses that come and they may want to Remove a tree that's on their property
Flag: numbers, amounts, negation or names differ between the machine readings · 00:47:36–00:47:39 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:47:56–00:47:59 · unresolved: the words are not shown (unclear audio); listen to the recording
them ‸ all the regulations that we have Normally, we try to make them aware of basic Regulations when they submit for a business tax receipt because then we have to review those But it's not every business that applies for one
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:48:21–00:48:26 · unresolved: the words are not shown (unclear audio); listen to the recording
put something out that the public can see so that this information is readily available? And so we're being proactive instead of reactive Everybody's in the uproar because they're hearing different versions of this story um
regardless of how people feel about the trees So I think if we can do something to make sure that the public has the information in advance It would stop a lot of confusion. That's just my little two cents. Thank you so much. Thank
‸ clarification. Someone asked if they had submitted a request Before taking the trees down would it have been approved could it be denied if it was approved They would just have to replace The trees somewhere on the property or
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:49:37–00:49:40 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:49:41–00:49:42 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:49:44–00:49:47 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:50:01–00:50:03 · unresolved: the words are not shown (unclear audio); listen to the recording
wherever there was a tree that was removed incorrectly We received a site plan showing where the tree is at and pictures to give us an idea of what that was involving and That's what I was wondering if I if we were ever going ‸ to Get additional information showing where the trees were and and the ones that were removed right now. It's strictly verbiage I know that we're moving on going to the future at this point
And I didn't know if you all were ‸ going to provide it for this This particular case or not because right now I I'd have to look up the site plan and try to Understand it myself.
‸ I was just trying to explain that those violations when the curve they are handled by the code enforcement board And we do have language in our codes that dictates that
that's what's causing the confusion because Whenever we had an issue with the tree being removed we would get additional information to show with pictures where it was located the subdivision, the name of the subdivision, where it's located in the subdivision. And that's why i'm confused because i thought that that was coming So if if it's not required then we just need to drop it
Yeah, maybe i can clarify that a little bit in the past there have been agenda items that have been brought to the tree board When someone wants to remove a tree an oak tree specifically in the city right of way Those are the only times that agenda items are brought to this board for recommendations on whether that tree can be removed and what the replacements would be.
and that's the reason that we have had You know as you said pictures and things like that brought those were for requests to remove trees. I remember yeah,
Flag: words were replaced by a machine repair · 00:53:06–00:53:07 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings · 00:53:11–00:53:14 · unresolved: the words are not shown (unclear audio); listen to the recording
It would again be a code enforcement matter if it was in the state right of way That is not something that this board oversees either right the only time is if it's in city right of way like a city road um And ‸ that's yeah, I understand it was
All right excellent. So if not, we will now move on to item agenda item number six other business or if we'd like to phrase it Any open conversations that we would typically have at this time Everyone's hushed today All right, we'll move on then so we'll close it up for uh other business
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:54:21–00:54:24 · unresolved: the words are not shown (unclear audio); listen to the recording
Now in homage to our chair who is not here. He always typically likes to bring something forward As to the next up-and-coming events, so we actually have three on the u.s calendar So the next I wish you all
Flag: words were replaced by a machine repair · 00:54:39–00:54:39 · machine repair: words replaced where two further machine readings agreed (not checked by a person)
Flag: numbers, amounts, negation or names differ between the machine readings; a language review questioned the wording · 00:54:41–00:54:45 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:54:57–00:54:59 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings · 00:55:13–00:55:14 · unresolved: the words are not shown (unclear audio); listen to the recording
Flag: numbers, amounts, negation or names differ between the machine readings; the recognizer flagged its own output; a language review questioned the wording · 00:55:14–00:55:15 · unresolved: the words are not shown (unclear audio); listen to the recording