Glasgow Surname Project

Individual research record

James Glasgow

c. 1640 – ?

Glasgow-3337 · 1 mapped association

Edinburgh, ScotlandDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
4Close relations
2Evidence items
18Candidate leads
Birth
c. 1640 · Edinburgh, Scotland
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
Annapill (Glessie) Glasgow
Children
James GlasgowRobert GlasgowThomas Glasgow
Gender
Male
WikiTree
Glasgow-3337
Research clusters
Scotland One-Tree profile leads
Mapped descendants
3

Comparison context

These child positions and checks are the subject details used to rank possible parents below.

Naming sequence used by the parentage model

Paternal grandfather positionJames Glasgow (1661)
Maternal grandfather positionThomas Glasgow (1663)
Maternal grandmother positionNot identifiable from dated child profiles
Paternal grandmother positionNot identifiable from dated child profiles

Known-position checks: 0 support · 1 conflict. Ordinals retain unnamed children and recognise reused names.

Relationship comparison

Potential parents or duplicates

Compare scored leads with the subject details above—not proof.

Higher-signal leadReview carefullyWeak lead

Possible fathers5 leads

Automated fit25/100
Weak Lead
Dates1627–?Generationnominally 13 years; approximate dates permit about 16–23 years age gapRecorded placesEdinburgh, Midlothian, Scotland · EdinburghIndependent clue breadth · 6Age · Household · Local Sibling Birth · Spouse · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • the nominal 13-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–23 years) (+4)
  • known spouse Catherine (Weir) Glasgow had a bounded, possibly plausible maternal age (15) at the subject's birth (+3)

parentage requires the approximate birth estimate to be early enough (no deduction)

Show complete scoring
  • the nominal 13-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–23 years) (+4)
  • candidate's birth is 34 years before the subject's earliest dated child (1661), a marginal two-generation interval (+1)
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • same research cluster (+0; grouping is not kinship evidence)
  • a known child was born within 4 years of the subject (+1)
  • candidate has another child, Margaret Glasgow, born 4 years from the subject in the same specific birth locality (+6; possible sibling-household clue)
  • known spouse Catherine (Weir) Glasgow had a bounded, possibly plausible maternal age (15) at the subject's birth (+3)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction)

Automated fit20/100
Weak Lead
Dates1626–?Generationnominally 14 years; approximate dates permit about 16–34 years age gapRecorded placesInveresk and Musselburgh, Midlothian, Scotland · Musselburgh / InvereskIndependent clue breadth · 7Age · Indirect Multi-Factor Convergence · Mapped Proximity · Same-Sex Generational Naming · Sex-Aware Ordered Naming · Tradition Validation · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • 3 independent unlinked-profile clue types converge (+5): household chronology, locality, naming
  • the nominal 14-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–34 years) (+4)
  • candidate's birth is 35 years before the subject's earliest dated child (1661), a marginal two-generation interval (+1)

parentage requires the approximate birth estimate to be early enough (no deduction)

Show complete scoring
  • the nominal 14-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–34 years) (+4)
  • candidate's birth is 35 years before the subject's earliest dated child (1661), a marginal two-generation interval (+1)
  • mapped Musselburgh / Inveresk is 8.5 km from the subject's birth-period Edinburgh (+2; one or both placements are unproved)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)
  • candidate's name matches the first dated son James Glasgow, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)
  • family naming controls: 0 supporting and 1 conflicting known positions (already reflected in naming weight)
  • 3 independent unlinked-profile clue types converge (+5): household chronology, locality, naming

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction)

Show 3 lower-scoring possible fathers
Automated fit13/100
Weak Lead
Dates1627–?Generationnominally 13 years; approximate dates permit about 16–23 years age gapRecorded placesInveresk and Musselburgh, Midlothian, Scotland · Saint Cuthberts, Edinburgh, Midlothian, Scotland · Musselburgh / InvereskIndependent clue breadth · 4Age · Local Sibling Birth · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate has only broad or undated birth-locality overlap: edinburgh (+6)
  • the nominal 13-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–23 years) (+4)
  • candidate's birth is 34 years before the subject's earliest dated child (1661), a marginal two-generation interval (+1)

parentage requires the approximate birth estimate to be early enough (no deduction)

Show complete scoring
  • the nominal 13-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–23 years) (+4)
  • candidate's birth is 34 years before the subject's earliest dated child (1661), a marginal two-generation interval (+1)
  • candidate has only broad or undated birth-locality overlap: edinburgh (+6)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate has another child, Eupham Glasgow, born 11 years from the subject in the same specific birth locality (+2; possible sibling-household clue)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction)

Automated fit0/100
Weak Lead
Dates1634–?Generationnominally 6 years; approximate dates permit about 16–26 years age gapRecorded placesBiggar, Lanarkshire, Scotland · Biggar — LanarkshireIndependent clue breadth · 5Age · Household · Same-Sex Generational Naming · Sex-Aware Ordered Naming · Tradition ValidationCurrent relationshipNot currently linked as parent
Strongest signals
  • the nominal 6-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–26 years) (+4)
  • a known child was born within 8 years of the subject (+1)
  • same research cluster (+0; grouping is not kinship evidence)

parentage requires the approximate birth estimate to be early enough (no deduction); candidate-to-earliest-child interval of 27 years is implausible for two generations (−8); same country, but no indexed locality overlap (−10)

Show complete scoring
  • the nominal 6-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–26 years) (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • a known child was born within 8 years of the subject (+1)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)
  • candidate's name matches the first dated son James Glasgow, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)
  • family naming controls: 0 supporting and 1 conflicting known positions (already reflected in naming weight)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction); candidate-to-earliest-child interval of 27 years is implausible for two generations (−8); same country, but no indexed locality overlap (−10)

Automated fit25/100
Chronology-Only Fallback
Dates1618–1662Generation22 years age gapRecorded placesSouth Leith, Midlothian, Scotland · South LeithIndependent clue breadth · 3Age · Mapped Proximity · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 43 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • mapped South Leith is 2.7 km from the subject's birth-period Edinburgh (+3; one or both placements are unproved)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 43 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • mapped South Leith is 2.7 km from the subject's birth-period Edinburgh (+3; one or both placements are unproved)
  • same research cluster (+0; grouping is not kinship evidence)

Deductions and cautions: No indexed conflict; documentary proof still required

Possible mothers5 leads

Automated fit41/100
Moderate Lead
Dates1617–?Generation23 years age gapRecorded placesEdinburghIndependent clue breadth · 5Age · Household · Local Sibling Birth · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 23-year parent-child age gap (+18)
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • candidate's birth is 44 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 23-year parent-child age gap (+18)
  • candidate's birth is 44 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • same research cluster (+0; grouping is not kinship evidence)
  • a known child was born within 3 years of the subject (+3)
  • candidate has another child, Issobell Glasgow, born 3 years from the subject in the same specific birth locality (+6; possible sibling-household clue)

Deductions and cautions: No indexed conflict; documentary proof still required

Automated fit31/100
Weak Lead
Dates1606–?Generation34 years age gapRecorded placesMid Calder, Midlothian, Scotland · Mid CalderIndependent clue breadth · 5Age · Indirect Multi-Factor Convergence · Mapped Proximity · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 34-year parent-child age gap (+18)
  • 3 independent unlinked-profile clue types converge (+5): household chronology, locality, naming
  • candidate's birth is 55 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 34-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • mapped Mid Calder is 19.5 km from the subject's birth-period Edinburgh (+1; one or both placements are unproved)
  • same research cluster (+0; grouping is not kinship evidence)
  • a candidate spouse matches the first dated son James Glasgow, the expected father position (+3; James in 224 profiles)
  • 3 independent unlinked-profile clue types converge (+5): household chronology, locality, naming

Deductions and cautions: No indexed conflict; documentary proof still required

Show 3 lower-scoring possible mothers
Automated fit25/100
Weak Lead
Dates1631–?Generationnominally 9 years; approximate dates permit about 15–19 years age gapRecorded placesEdinburghIndependent clue breadth · 6Age · Indirect Multi-Factor Convergence · Local Sibling Birth · Sex-Aware Ordered Naming · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • 3 independent unlinked-profile clue types converge (+5): household chronology, locality, naming
  • the nominal 9-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–19 years) (+4)

parentage requires the approximate birth estimate to be early enough (no deduction)

Show complete scoring
  • the nominal 9-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–19 years) (+4)
  • candidate's birth is 30 years before the subject's earliest dated child (1661), a marginal two-generation interval (+1)
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate has another child, Helen Glasgow, born 11 years from the subject in the same specific birth locality (+2; possible sibling-household clue)
  • a candidate spouse matches the first dated son James Glasgow, the expected father position (+3; James in 224 profiles)
  • 3 independent unlinked-profile clue types converge (+5): household chronology, locality, naming

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction)

Automated fit15/100
Weak Lead
Dates1613–?Generation27 years age gapRecorded placesSaltcoats, Ayrshire, Scotland · Saltcoats — AyrshireIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 27-year parent-child age gap (+18)
  • candidate's birth is 48 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 27-year parent-child age gap (+18)
  • candidate's birth is 48 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • a candidate spouse matches the first dated son James Glasgow, the expected father position (+3; James in 224 profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Automated fit15/100
Weak Lead
Dates1610–?Generation30 years age gapRecorded placesGlasgow, Lanarkshire, Scotland · GlasgowIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 30-year parent-child age gap (+18)
  • candidate's birth is 51 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 30-year parent-child age gap (+18)
  • candidate's birth is 51 years before the subject's earliest dated child (1661), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • a candidate spouse matches the first dated son James Glasgow, the expected father position (+3; James in 224 profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

How parent leads are calculated

Automated leads use birth surnames—not married surnames—as parental eligibility, role-specific biological age limits, bounded and approximate-date uncertainty, household chronology, specific time-aware localities, mapped distance, tenancy succession, migration destinations and sex-aware Scottish naming positions across generations. People already attached as the subject's parents stay in the identity summary and are excluded from this alternative-candidate list, regardless of relationship confidence. The main calibration uses clues available on disconnected profiles; existing parent and sibling links are retained as comparison context rather than treated as transferable evidence. Common ordered names and grandparent-to-child echoes receive a small non-zero weight, so a John or James match can support several independent criteria without producing a lead alone. Rare names, repeated bearers and bundles across otherwise distinct branches receive substantially more weight according to catalogue frequency. An exact migration place is weighted by its rarity and repetition across both branches; a shared destination country is worth only one point. Extra weight is added only when at least three independent clue types converge: naming, locality, specific migration, household chronology or collateral networks. Sparse profiles retain a clearly labelled chronology-only fallback instead of disappearing. Countries, states, counties and research clusters do not count as a shared locality, and fallback, broad representative or kin-inferred coordinates are excluded from distance scoring. Shared descendant profiles are removed before branch-name comparison. A candidate already recorded as a parent-in-law is excluded. A confident or independently supported parent is treated as settled; uncertain and unassessed attachments remain open to alternative comparison. A different linked parent, an uncle/aunt or grandparent path, and a matching existing child profile prevent an alternative from being classified as a strong direct-parent lead until the underlying tree conflict or duplicate is resolved. Familiar forms such as Bessie are normalised. Surname remains an eligibility filter worth zero points.

Naming customs, shared farms and occupations are circumstantial. Children, spouses and collateral relatives may be missing, and tree-derived family networks are not independent evidence. Scores rank research leads; they do not prove parentage.

Same-name candidate

James GlasgowGlasgow-3077

Automated fit68/100
Similar Person
Dates1640–?PlacesSaint Cuthberts, Edinburgh, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)
  • shared recorded place (+20)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)
  • shared recorded place (+20)

Conflicts: No indexed conflict

Same-name candidate

James GlasgowGlasgow-3103

Automated fit52/100
Similar Person
Dates1679–?PlacesEdinburgh, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • shared recorded place (+20)
  • matching child name: Robert Glasgow

record-derived birth estimates differ by 39; retained without deduction

Full comparison detail
  • same first and last name (+18)
  • shared recorded place (+20)
  • matching child name: Robert Glasgow

Conflicts: record-derived birth estimates differ by 39; retained without deduction

Same-name candidate

James GlasgowGlasgow-3107

Automated fit50/100
Similar Person
Dates1645–?PlacesGordon, Berwickshire, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 5 (+18)
  • matching child name: Robert Glasgow

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 5 (+18)
  • matching child name: Robert Glasgow

Conflicts: No indexed conflict

Same-name candidate

James GlasgowGlasgow-3172

Automated fit48/100
Similar Person
Dates1640–1686PlacesScotland → Belfast, IrelandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)

Conflicts: No indexed conflict

Show 4 lower-scoring duplicate lead(s)

Same-name candidate

James GlasgowGlasgow-1496

Automated fit42/100
Similar Person
Dates1650–?PlacesCampbeltown, Argyll, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 10 (+10)
  • matching child name: Robert Glasgow

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 10 (+10)
  • matching child name: Robert Glasgow

Conflicts: No indexed conflict

Same-name candidate

James GlasgowGlasgow-1150

Automated fit40/100
Similar Person
Dates1620–?PlacesInveresk and Musselburgh, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 20 (+2)
  • matching child names: James Glasgow, Robert Glasgow

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 20 (+2)
  • matching child names: James Glasgow, Robert Glasgow

Conflicts: No indexed conflict

Same-name candidate

James GlasgowGlasgow-2682

Automated fit40/100
Similar Person
Dates1655–?PlacesMidlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 15 (+2)
  • matching child names: James Glasgow, Thomas Glasgow

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 15 (+2)
  • matching child names: James Glasgow, Thomas Glasgow

Conflicts: No indexed conflict

Same-name candidate

James GlasgowGlasgow-1376

Automated fit40/100
Similar Person
Dates1657–?PlacesEdinburgh, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 17 (+2)
  • shared recorded place (+20)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 17 (+2)
  • shared recorded place (+20)

Conflicts: No indexed conflict

How duplicate leads are calculated

Dates are eligibility gates, not merely deductions: chronologically impossible people are excluded. Dates, places, spouses, parent certainty and children's profiles and names are then compared. A high score is a prompt to inspect records, not a merge recommendation.

Open only what you need

Research & records

Latest case researchThe current conclusion from the durable research case file.Updated

Conclusion

Glasgow-3337

This profile represents the father James in the St Cuthbert's family associated with Annapill or Anabell Glessie/Glass and children in 1661, 1663 and 1665. Its about 1640 birth is only an estimate from parenthood; the 1661 index is a child's event, not James's birth.

Glasgow-3077, who had a daughter with Helen Clerk at St Cuthbert's in 1658, is a strong same-person candidate. One widower with consecutive wives is plausible, but not yet proved.

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1640

Profile-stated birthplace: Edinburgh, Scotland

Edinburgh

One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links.

One-Tree profile leadunknown
Source and mapping detail

WikiTree profile export for Glasgow-3337

No sufficiently specific citation match found.

Precision: Settlement centrepoint

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.5 claims
1Derivative
1Tree Only

Documented or strongly supported

No claims in this category have been formally assessed.

Working hypotheses and conflicts

No claims in this category have been formally assessed.

Research questionsOpen problems, missing bridges and the next records to inspect.0 open

No formal open question is recorded for this person.

Case-file priorities and cautions

Recommended update

Glasgow-3337

  • Change birth to before about 1641 and retain Edinburgh as an explicitly

uncertain estimate from the children's parish records until better evidence supplies a replacement.

  • Explain that FamilySearch F316-KWL concerns son James in 1661.
  • Retain Annapill and the three children as the working record-defined family.
  • Hold the Glasgow-3077 merge until Helen's death or a second marriage is found.

Applied live on 19 August 2026. The three baptism-recorded child-parent links and the co-parent relationship with Annapill are confident; the possible identity with Glasgow-3077 remains unresolved.

See the graph-claim audit.

Sources and provenanceStructured citations and source-quality classifications.2 sources
Technical profile and raw captureDataset metadata, machine dossier and captured WikiTree biography.Advanced

WikiTree profile information

Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20

Machine-readable dossier

WikiTree biography, citations and relationship snapshot

Glasgow-3337 was captured 2026-08-18T15:04:41+00:00; WikiTree profile revision 2025-04-22.

Profile location claims

EventDateLocationStatus
birthEdinburgh, ScotlandWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenJames GlasgowGlasgow-30761661-03-03 · Saint Cuthberts, Edinburgh, Midlothian, Scotland · 0000-00-00
ChildrenThomas GlasgowGlasgow-30911663-09-09 · Saint Cuthberts, Edinburgh, Scotland · 0000-00-00
ChildrenRobert GlasgowGlasgow-33381665-05-28 · Saint Cuthberts, Edinburgh, Midlothian, Scotland · 0000-00-00
SpousesAnnapill GlasgowGlessie-11640-00-00 · Saint Cuthberts, Edinburgh, Midlothian, Scotland · 0000-00-00

Record-bearing passages

Profile source citations

  1. "Scotland Births and Baptisms, 1564-1950", database, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:F316-KWL : 16 September 2021), James Glesgow, 1661. source link 1
Full captured biography text
Biography
James was born about 1640. 
Sources
* "Scotland Births and Baptisms, 1564-1950", database, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:F316-KWL : 16 September 2021), James Glesgow, 1661.
Raw WikiTree biography markup
== Biography ==

James was born about 1640. 


== Sources ==
<references />

* "Scotland Births and Baptisms, 1564-1950", database, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:F316-KWL : 16 September 2021), James Glesgow, 1661.