VANDY WATCH Vanderburgh County Property & Code Enforcement Records VANDERBURGH COUNTY / EVANSVILLE PROPERTY ENFORCEMENT Research period 2000-2026 through October 18, 2026; regular archive series 2015 onward START HERE Map.html displays all accepted address locations on one searchable map. Of 1,192 address entries, 1,119 have points (93 approximate) and 73 remain unlocated. Click an address for case history; filter by owner, year, order type or location quality. See map_notes.txt, property_locations.csv and map_validation.json. CaseStatus.html lists each CE case's latest recorded hearing action. The default view shows 2026 follow-up/demolition steps; this is not verified live open status. See case_status_notes.txt and recent_pending_cases_2026.csv. The SQLite table case_status_snapshot is additive and retains the underlying source links. For repeated owner patterns, open Owners.html. It groups named owners by distinct repair/raze case numbers with issue dates in 2015 through October 18, 2026. The report links properties, dates, source passages and possible name matches. See owner_methodology.txt before interpreting the rankings; later purchasers may appear as owners of earlier cases. owner_summary.csv and owner_cases.csv are queryable exports. The database now includes additive owner_* analysis tables. Open Search.html in a browser. No installation, account, or network connection is needed for searching the embedded data. Internet access is needed to follow the official source links. Saved original documents are in sources/ beside this file. Keep that folder in place to use the "Saved original" links. enforcement.sqlite is a standard SQLite database with FTS5 indexes. It can be queried independently of Search.html. example_queries.sql provides examples. records.csv, documents.csv, meetings.csv, coverage.csv and year_coverage.csv are exports. records.json and extracted_documents.json preserve machine-readable source data. summary.json contains final collection counts. HISTORICAL EXPANSION (2000-2024 REQUEST) The regular meeting archive reached back into 2015. Posted material from 732 selected 2015-2024 meetings, including 91 Hearing Authority entries, was collected. 2015 is partial. There is no complete recovered enforcement series for 2000-2014. Supplemental evidence includes a court passage published in 2003 describing a 2002 raze notice, and a limited abstract of a 2009 property maintenance report. These saved text files are clearly labelled research transcriptions/abstracts; their original HTML/PDF or agency notice was not recovered. They are not counted as original downloaded documents. No order issue date is guessed from a notice. Source URL, saved-file hash, limitations and source-date basis are retained. Read historical_research.txt for attempted repositories and unavailable sources. year_coverage.csv and the Coverage tab identify gaps for every requested year. Zeros describe collection gaps, not proof that no enforcement occurred. For 2022, 11 hearing agendas are listed but no hearing minutes are posted in the collected archive. Agenda observations do not establish final hearing decisions. WHAT WAS COLLECTED The official City of Evansville / Vanderburgh County Granicus archive was inspected across its five archive panels (views 12-16) and upcoming-events view 3. Meetings dated January 1, 2000 through October 18, 2026 were selected for these bodies: - Hearing Authority, including separately labelled Vanderburgh County hearings; - Board of Public Safety; - Board of County Commissioners, including special and no-drainage meetings; - Evansville and Vanderburgh County redevelopment commissions; - related budget hearings appearing in the archive selection. Available agendas and minutes were downloaded, together with linked document wrappers and relevant building, hearing, demolition, unsafe-building, ordinance, property-maintenance, and minutes attachments. Video links are catalogued in meetings; video files were not downloaded or independently transcribed. Archive entry point: https://evansville.granicus.com/ViewPublisher.php?view_id=2 WHAT "ALL" DOES AND DOES NOT MEAN This is a collection of the publicly posted documents reached by the documented archive crawl. It is NOT a certified, exhaustive export of Building Commission cases. Cases that did not reach a posted hearing, unpublished inspection files, complaints, notices, exhibits, photographs, court filings, and records held only in the office may be absent. The county and city have separate hearing labels. Full 2026 coverage is impossible before the year ends; this snapshot stops October 18. An archive omission does not establish that a meeting did not occur. January 2025's posted hearing material is a weed/trash appeal agenda. It includes some cases with no property address; these remain in the complete document text but cannot be indexed to a property. No January 2026 city structural hearing is listed in the collected archive. The October 2026 city structural hearing is not in the past-meeting collection at the cutoff. The separately listed October 14 county hearing is included. Monthly coverage uses exact body labels, so a renamed body can produce a zero under one label and a meeting under another. Each record is an OBSERVATION IN A SOURCE, not a newly committed violation. The same case can appear at multiple hearings, in an agenda and in minutes, and as separate vacate and raze orders. These are intentionally retained. Use distinct case numbers or property IDs when counting cases or properties. Some case numbers and original order dates precede the source year because they were discussed during the requested period. Do not infer a property's current condition from a historic order, a procurement request, or a hearing agenda. EXTRACTION AND PROVENANCE Original bytes, source URL, retrieval timestamp, and SHA-256 hash are retained. Native PDF, HTML, DOCX and legacy DOC text was extracted. Image-only PDF pages were OCRed with Tesseract and English tessdata_fast. OCR is a transcription and can misread names, numbers, dates, addresses, and section citations. Check the saved page or official document for material decisions. OCR metadata is in documents.extraction_method and pages.ocr. A low-text document is marked in documents.extraction_note. Property addresses normalize periods, directions, street suffixes, and range spacing. Original spellings remain in address_as_recorded and raw_text. Spelling errors, ELLIOT/ELLIOTT, and unlabelled directions are NOT silently merged. Property counts are counts of normalized address strings, not independently verified land parcels. Parcel numbers have not been inferred or joined to ownership databases. Exact ordinance citations are extracted only when explicitly present. Many hearing packets describe violations without stating the numbered ordinance. No legal section is inferred from a generic roof, structural, or trash condition. Search tags are keyword aids (roof, foundation, utilities, etc.), not statutory charges or verified findings. Full document search is available when a passage cannot be structured or associated with a property. Some packets are headed "AGENDA" but are published as minutes and contain a department report and Hearing Officer action. source_kind preserves the archive's label. decision_text extracts the passage beginning "The Hearing Officer"; it is not an independently interpreted status. A related raze page may simply say "Refer to [case] VACATE"; use the case timeline to inspect the related page. Absence of decision_text does not establish absence of a decision. meeting_date is the archive date, or publication/report date for explicitly labelled supplemental sources. document_date is the first printed month/day/year heading detected in the document and may itself contain a source typo or refer to another date. Known conflicts are listed in summary.json and can be queried. date_order_issued, file_start_date, first_appearance, and compliance_date come from explicitly labelled fields. They describe that source version of the order and may change in later documents. Other dates remain searchable in raw source text. Fines, civil penalties, and other dollar amounts remain TEXT AS RECORDED. A blank fine field is NULL, not zero. A dollar amount in a recommendation or under advisement is not necessarily an assessed or paid fine. amounts_as_recorded can contain bids, costs, bonds, or penalties; do not sum it as a monetary balance. SCHEMA metadata: scope, date boundaries, and interpretation rules. meetings: clip_id, archive_date, body, agenda URL, video URL, minutes availability. documents: meeting link, source kind/label/URL, saved original, hash, retrieval time, complete extracted text, extraction method, errors and notes. pages: source document, 1-based PDF page, extracted/OCR text, OCR flag. properties: property ID and normalized address. records: property/source/page links, case number, original address, dates, order category and text, owner as recorded, department report, hearing action, inspection count, monetary text, explicit citations, tags, full passage, and quality notes. record_ordinances: explicit citation strings associated with an observation. document_ordinances / ordinance_catalog: legal citations found in complete source documents, without asserting a property-specific charge. record_tags: keyword aids associated with an observation. coverage: exact body label and month, meetings/documents found, coverage notes. year_coverage: annual source counts, hearing counts, observations and explicit gaps. records_fts / documents_fts: SQLite FTS5 full-text indexes keyed to record/document. property_history: joined view combining records, normalized address, source URL, source kind, and meeting body. USEFUL QUERIES See example_queries.sql. Search.html provides plain word search, source and order filters, date ranges, source passages, property timelines, and filtered CSV export. Repeated records do not indicate repeated or additional violations. VALIDATION The SQLite integrity and foreign-key checks, source-file checksums, representative property/date queries, full-text searches, and browser search/filter/details flows were checked. Source fields remain automatically extracted and need source review for legal, ownership, or current-condition conclusions.