Method, and what to be careful about
Where the data came from
A resident built this page with an AI model (Claude) doing the extraction, the tagging, the checks, and the page itself, under a person’s direction and review. Everything on it was extracted from the Village’s published PDF: the 1,459 comments from the table on pages 34 to 102 of the report (pages 36 to 104 of the PDF file), the chart values from the report’s own labels, and the response-count tables that sit under each chart as images. Counts were checked two ways: each table’s answers must add up to its total, and the average computed from the counts must match the average printed on the chart to within 0.1. Where the report’s own numbers did not line up, the notes below say so.
How the comments were tagged
Each comment was read by an AI model (Claude) and tagged with up to several topics from a fixed list of 41, a stance on 13 contested questions where the comment clearly takes a side, and an overall tone. A person directed the work, set the topic list and the tagging rules, and reviewed the output. The topic tags were then cross-checked against keyword searches (for example, every comment containing “meter” was compared with the comments tagged “metered parking”) and the differences reviewed. Some subjects are split across themes on purpose: a comment about taxes may sit under “Property tax levels,” “Willing to pay,” “Fees on the utility bill,” or “Spending & fiscal management” depending on its point, so searching the word “tax” finds more comments than any one theme holds.
What that means for reading the counts. Topics with concrete words behind them, such as parking meters, the DPW facility, the Oakland lot, or leaf pickup, are the most dependable. Tone is a judgment about the comment as a whole, and a comment that praises one thing and criticizes another may land in “mixed” or in either camp. Stance is recorded only where a comment plainly takes a side, so stance counts understate how many people care about a question. No formal accuracy audit has been done, so read a count of 164 as “about 164,” and read the comments behind any number before quoting it.
The map, and the Census comparison
Street and park geometry comes from OpenStreetMap. The eight survey sections were redrawn by hand from the report’s map, so their edges are approximate. Place mentions are found by matching names in the comment text (for example “Oakland” or “Atwater”), and the matching rule is shown when you tap a place. The Census comparison uses the American Community Survey 5-year estimates for the Village of Shorewood, with the table numbers listed under the chart; age is compared among adults only, since only adults answered the survey.
Names
The Village published all comments verbatim, including a few that name individual residents, staff, and officials. Here, personal names are replaced with a role in brackets, such as “[a trustee]”. Business names, streets, and public figures in the media are unchanged.
Where the report’s own numbers don’t line up
While extracting the data, a few places turned up where the report’s charts, tables, and labels disagree with each other. They may be layout or labeling slips in the report rather than problems with the survey itself. They are listed here because they affect a few numbers on this page and explain some choices made in building it.
Show the six notes ›
- Communication charts. The 2026 “very / somewhat / not at all valuable” shares add up to the share of respondents aware of each channel, while 2019 and 2023 add up to 100%. This page rescales 2026 to the same base, which shrinks most of the declines the report describes.
- Accessibility for persons with disabilities. The chart shows 2.4; the response table under it computes to 2.76. This page uses the table.
- Two charts repeat another chart’s bars. The 2019 night-time parking convenience bars match the 2023 day-time parking bars, and the Village Notify Me chart matches the Village Website chart in all three years.
- Two tables disagree with themselves. In “Inclusion of diverse populations” the counts and the percentages differ; this page follows the percentages. In “Atwater Park & Lake Bluff restoration” the fair and poor counts look swapped.
- The metered-parking pie adds up to 89%. The remaining 11% is not shown.
- Some trends are not shown. Community Events, the Beach, and the Senior Resource Center Newsletter have no 2019 value, and the budget question was reworded in 2026.
What people wrote about
Each comment was tagged with the topics it raises (most touch more than one). Tap a topic to read every comment behind the number. Counts are comments, not people: one respondent could write in all eight comment boxes.
How to use this page: anything in blue, and anything marked ›, is tappable. It opens the comments behind that number in the reader further down. Bars and dots in the charts are tappable too.
Tone, by survey section tap a segment to read
Each comment was read for its overall tone toward the Village. Comments that only make a suggestion or answer a question are “neutral.” Tap a segment to read.