Rietfontein

Gedeelte: subdiv of 169
Distrik: Prince Albert

Hierdie perseel het geen gepaste opmetingspoligoon nie, en kan dus nie op die kaart geteken word nie. Dit is 'n gaping in die kadasterpassing, nie 'n afwesigheid uit die rekord nie.

Waarom hierdie plaas hier is

'n Stuk van 'n plaas wat reeds in hierdie model is. Nog nie op die kaart geplaas nie.

perseel Uitgesny uit Middelwater

Wat die rekord hou, in volgorde

undated boundary change subdivision: from Middelwater

Navorsingsnotas

subdivision of Middelwater [TO VERIFY - probably wrong]. [29 Jul 2026, verification pass] The only support for this parcel is one unsourced legacy line ("20th c. - subdivided; a portion became Rietfontein", F01 prose) and PLK-000002 (no document). DOC-0039 (the 1883 verso) lists NO Rietfontein deduction from farm 169, and the modern cadastre has none. This looks like the two-Middelwaters trap run in reverse: the documented relation is Rietfontein (Zeekoegat district, PAR-000052) subdivided into a SECOND Middelwater - not our No.169 subdivided into a Rietfontein. Cadastre match stripped 29 Jul 2026: the record it wore (Ptn 38 of farm 56) belongs to Rietfontein No.56 south of Leeu-Gamka, unrelated to farm 169. Parcel kept pending

HE IS RIGHT, AND IT IS WORSE THAN A DUPLICATE. Both rows were still carrying the SAME cadastre key W052C061000000000056000380 and the SAME centroid -32.880993, 21.889268, which is Ptn 38 of RIETFONTEIN No. 56, south of Leeu-Gamka. The 29 Jul verification pass recorded that this match had been stripped; the note said so and the columns did not. So the two rows were not the same farm, they were two different farms wearing a THIRD farm's polygon, and the index showed both as 38/56. Key, centroid, area and match method cleared on both. Neither is pinned now, per 5: an unresolved place gets no pin. Whether these two rows should be one row is a separate question and is LEAD-0058.

[1 Aug 2026] NO-POLYGON SET, because clearing the key was not enough. Both rows have no farm number, so match_cadastre.py fell back to matching on NAME and put them straight back onto Ptn 38 of Rietfontein No. 56 near Leeu-Gamka - a third farm, and the same wrong pin they carried before. The sentinel is the only thing that stops a name match re-deriving it on the next run.

Werknotas, hier gewys omdat dit 'n private navorsingsbou is.

Die werksnotas op hierdie werf word in Engels gehou en word nie vertaal nie. Hulle verander met elke navorsingsessie, en 'n vertaling sou uit pas raak met die oorspronklike. Alles anders — die stories, die getranskribeerde dokumente en die koppelvlak — is in Afrikaans.

Oop vrae

match_cadastre.py no longer reproduces the geometry on disk prioriteit 1 · LEAD-0017
Re-running match_cadastre.py against the current CSVs changes 11 parcels and does not reproduce what is in parcels.csv. Which is right?

Wat dit sou uitmaak Deciding per parcel whether the script's match or the hand entry is correct, then either fixing the script's name-matching or recording the hand values as deliberate.
141 people are on this site linked to nothing prioriteit 1 · LEAD-0074
Which parcels and people exist on the site as dead ends - reachable by a list, but linked to no document, story, owner or neighbour?

Wat dit sou uitmaak For the 106 tree-derived rows, a parentage pass merged from the family-tree on tree id - which 6 already names as the direction of travel and which would connect them wholesale rather than one at a time. For the three floating names, find the document each came from and link it.
Two Rietfontein rows: one farm, or one farm and a phantom? prioriteit 2 · LEAD-0058
Should PAR-000010 "Rietfontein" and PAR-000052 "Rietfontein (Zeekoegat district)" be one row, and does PAR-000010 describe a farm that ever existed?

Wat dit sou uitmaak Either a Middelwater deduction table naming a Rietfontein, which would make PAR-000010 real and separate, or the absence of one across the full set, which would retire it into PAR-000052.
Three farms carry the same name twice or three times, and ten story links are held back because of it prioriteit 2 · LEAD-0080
Which Rietfontein, which De Claar Stroom, and is Sleutelfontein (Groot and Klein) a real parcel or a composite of two?

Wat dit sou uitmaak For each mention, which parcel the sentence means. For Sleutelfontein, whether PAR-000098 should exist at all given PAR-000071/072.

Wat die rekord kortkom

Nobody is on record as ever having held this third order · B8 never-held
Rietfontein is in the model, and carries no ownership record of any kind, not a grant, not a transfer, not an occupation.

What would settle it The Surveyor-General's diagram for the farm number names the grantee and the date; the deed reference on it opens the transfer chain.

Found by breaks.py reading the model against itself, not written by hand, each one is a shape of missing record, not a fault in the data. The whole set is on the questions page.