Where the guide’s facts come from

What was verified

Three advertised iCalendar endpoints returned recognizable calendar payloads during bounded project-container checks. The municipality audit parsed zero event items, reviewed zero terms or reuse permissions, and approved zero recurring fetches. A later one-time adapter check parsed a Parkesburg ICS response and a County RSS response in memory; those observations did not authorize ongoing ingestion or publication.

“Feed container verified” means the response had a syntactically recognizable feed signature. It does not mean individual dates, source rights or the adapter’s production behavior were verified. Every record below is a point-in-time observation. Follow its official link for current facts.

Municipality-by-municipality audit

Showing all 73 municipalities.

Live publishing and freshness

The public calendar reads an approved, versioned publication. A source failure does not turn an old publication into a new source check. See the current source health summary, including the last successful check and coverage state recorded by the local operator system.

Places, history and traditions use dated editorial catalogs with claim-level source IDs and review states. The original logo and illustration are project-owned assets; third-party photographs and maps have not been rehosted.