Roelof Daniel Jacobus Oosthuysen
1855 – 1953 · Oosthuizen line
Descends from the root couple, 2 generations up
Names
- Baptismal name
- Roelof Daniel Jacobus
- Given
- Roelof Daniel Jacobus
- Surname
- Oosthuizen
The formal baptismal name and the name a person was actually called are both kept, and neither is derived from the other. Spelling drift between records is evidence, not noise.
Immediate family
- Father
- Johannes Adriaan Oosthuizen
- Brothers and sisters
-
- 1836Ockert Almero Oosthuizen
- 1838Johanna Petronella Oosthuizen
- 1839~Anna Magdalena Oosthuizen
- 1840Cornelis Andreas Oosthuizen
- 1840Cornelis Andries Oosthuizen (b.1840)
- 1840Roelof Daniel Jacobus Oosthuizen
- 1842Jan Adriaan Oosthuizen (b.1842)
- 1844Petrus Marthinus Lodewicus Oosthuizen
- 1847Adriana Cecilia Oosthuizen (b.1847)
- 1849Susanna Catharina Oosthuizen (b.1849)
- 1852Anna Magdalena Oosthuysen
- 1856Martha Magdalena Oosthuizen
- 1861Johanna Elizabeth Eliza Oosthuizen
- 1865Anna Petronella Oosthuizen (b.1865)
- ·Adriana Oosthuizen
A life in the record
- 1855 born Born
- 1953 died Died
What we don't know
- No dated record ties this person to a specific piece of ground.
A sourced gap beats an unsourced fill. These are the open questions on this person, stated rather than papered over.
Research notes
[FamilySearch, 29 Jul 2026] Brother of PER-000005; lived to 98.
29 Jul 2026: linked to tree (matched on name + birth year during the farm-relatives pull).
These are working notes, not finished prose: they carry the reasoning, the corrections and the things still marked to verify. They are kept here so the page itself can read as what is known.
Open questions
-
Nine people carry a different FamilySearch id here and in the tree
priority 2 · LEAD-0036
For nine people the model records one FamilySearch id and the family-tree's _FID records another. Which is the live profile, and are the two ids two profiles for one person that want merging on FamilySearch itself?
What would settle it Loading each id and seeing whether it redirects.
-
Seven people carry a hand-entered FamilySearch id that the family-tree disagrees with
priority 3 · LEAD-0019
Backfilling familysearch_id from the family-tree's _FID tag agreed with the hand-entered value on 103 of 110 people and disagreed on 7. Which id is current for each - or do both resolve to the same person after a merge?
What would settle it A redirect proves a merge and the survivor id is the one to keep. Two live, distinct profiles means one of them is the wrong person, and the vitals decide which.
Elders
FamilySearch profile GCMK-22K