CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Kerk-Avezaath

farm village in the Netherlands

Architectural plans, a scale model, maps and brass measuring instruments
Places and architectureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 24, 2026
Entity authorityQ3112527 ↗
Source-derived summary

Kerk-Avezaath is a village in the Dutch province of Gelderland. It is a part of the municipality of Buren, and lies about 3 km west of Tiel.

A small part of the village (not counted in the statistics above) is part of the municipality of Tiel, and consists of about 60 houses.

History

It was first mentioned in 850 as Auansati, and means "church at the house of Avo (person)". The village developed along two parallel roads on a stream, and a stretched esdorp developed. The tower of the Dutch Reformed Church dates from 1640 and has an 11th century base. The church dates from 1861 and has 14th century elements. In 1840, it was home to 449 people.

Editorial summary

“Kerk-Avezaath” enters the record as farm village in the Netherlands. Crown Archives preserves that source wording while asking what Kerk-Avezaath, farm and village can confirm, complicate or overturn.

Editorial reviewA strong orientation record where physical form, institutional use and historical geography need to be read together. The current lead gives the account dated anchors—1640, 1861, 1840—that can be checked directly. The selected authority fields contribute no independent date. Its strongest next move is a source search built around Kerk-Avezaath, farm and village.
Editorial analysis

Why this record matters

“Kerk-Avezaath” is worth following because a concise public description often conceals a longer documentary argument. Here, Kerk-Avezaath, farm and village provides the most credible route into that argument.

Evidence profile

Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Sep 24, 2026. The linked authority identifier is Q3112527. The first chronological checks are 1640, 1861 and 1840.

Critical limits

Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.

Best used for
  • Historic place names
  • Jurisdictional context
  • Routes into maps and plans
Verify next

Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.

Three-step research path

  1. Establish the record: confirm the title “Kerk-Avezaath”, its source revision and the description used here.
  2. Expand the search: follow Kerk-Avezaath primary sources, Kerk-Avezaath archive and Kerk-Avezaath research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Kerk-Avezaath”?
  2. What physical evidence or contemporary plan supports the description?
  3. Which earlier names or jurisdictions may reveal additional records?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Kerk-Avezaath” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.