HelpDatabase Reference › Ancestry_SharedBirthLocations

Ancestry_SharedBirthLocations Table

The Ancestry_SharedBirthLocations table records ancestral birth locations that a test kit shares with a match — places where ancestors on both sides were born. Each row is one shared location for one test-and-match pair. The locationId column joins to Ancestry_Locations, which holds the place name and coordinates.

Column Reference

ColumnTypeSourceDescription
Idint (PK)AutoAuto-incrementing primary key
testGuidstringMatch CompareThe test kit GUID (your kit, stored uppercase)
matchGuidstringMatch CompareThe matched person’s GUID (stored uppercase)
locationIdintMatch CompareLocation identifier — joins to Ancestry_Locations.Id
samplePeoplestringMatch CompareComma-separated person IDs from your tree born at this location
matchPeoplestringMatch CompareComma-separated person IDs from the match’s tree born at this location
personCountintMatch CompareCount of people associated with this shared location
loginUsernamestringAppDNAGedcom username who gathered this data
syncstringAppSync status flag
A unique index on (testGuid, matchGuid, locationId) keeps a shared location from being duplicated for a pair. The app skips inserting a row that already exists for that combination.

How It’s Populated

This data comes from the match’s linked tree on its compare page, so it is only gathered when tree or ICW gathering is enabled. For each shared birth location, the place name and coordinates are resolved to a row in Ancestry_Locations (created if new), and that location’s ID is stored here along with the sample and match person lists.

Related Tables

  • Ancestry_Locations — place-name and coordinate lookup referenced by locationId.
  • Ancestry_matchGroups — the parent match record, keyed by matchGuid.
  • Ancestry_SharedJourneys — the related shared migration-journey data captured on the same compare page.