Lanxmeer
human settlement in the Netherlands
Lanxmeer is the name of an ecological neighbourhood (240 houses) built from 1994 to 2009 in the town of Culemborg in the Netherlands. It is an environmentally friendly housing development.
It was initiated by Marleen Kaptein, who was looking for a more sustainable way of building housing in urban areas. The project was a strong partnership between future inhabitants and the city of Culemborg, consultants and other people.
It incorporates many of the principles of high environmental quality and eco-towns, but its principal originality is the promotion of the constant participation of the inhabitants. Indeed, this neighbourhood (except for its masterplan) was designed and conducted with representatives of future residents in a creative process (bottom-up; from bottom to top and not imposed by management or administration), and is often regarded as a model in several areas (for example in Europe by Energie-Cités and in France by the Department of Ecology, Energy, Sustainable Development and Sea). It has therefore become an international reference, regularly visited by architects, urbans planners, developers, futurists or groups interested in sustainability, from European countries, and sometimes the United States, Japan, etc..
Creation of the project
In 1990, Marleen Kaptein believed that creating neighbourhoods with the inhabitants was both possible and necessary.
She gathered a group of people motivated to create the project. She thought that a critical threshold
of 200 to 400 houses must be reached.
The public source identifies “Lanxmeer” as human settlement in the Netherlands. This brief keeps that definition visible, then builds a research path around Lanxmeer, human and settlement.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Lanxmeer”, the useful work is to connect “human settlement in the Netherlands” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jan 12, 2025. The linked authority identifier is Q2638675. Authority coordinates are 51.948, 5.233. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1994, 2009 and 1990.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. 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
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Lanxmeer”, its source revision and the description used here.
- Expand the search: follow Lanxmeer primary sources, Lanxmeer archive and Lanxmeer research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Lanxmeer”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Lanxmeer” 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.