Individual Page


Family
Marriage: Children:
  1. Bethia Noble: Birth: 20 APR 1721 in Westfield, Hampden, Massachusetts, United States. Death: 02 JUL 1787 in Westfield, Hampden, Massachusetts, United States

  2. Joanna Noble: Birth: 03 DEC 1722 in Westfield, Hampden, Massachusetts, USA. Death: 18 NOV 1809 in Westfield, Hampden, Massachusetts, USA

  3. Constantine Noble: Birth: 08 OCT 1725 in Westfield, Hampden, Massachusetts, USA. Death: in Sheffield, Berkshire, Massachusetts, USA

  4. Gideon Noble: Birth: 06 MAR 1727 in Westfield, Hampden, Massachusetts, USA. Death: 06 NOV 1792 in Willington, Tolland, Connecticut, USA

  5. Rhoda Noble: Birth: 28 AUG 1732 in Westfield, Hampden, Massachusetts, USA. Death: MAR 1777

  6. Matthew Noble: Birth: 27 JUL 1736 in Westfield, Hampden, Massachusetts, USA. Death: 30 AUG 1804 in Westfield, Hampden, Massachusetts, USA

  7. Paul Noble: Birth: 14 JAN 1739.


Family
Children:
  1. Gideon Noble: Birth: 06 MAR 1727 in Westfield, Hampden, Massachusetts, USA. Death: 06 NOV 1792 in Willington, Tolland, Connecticut, USA


Sources
1. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
2. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
3. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
4. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
5. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
6. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
7. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
8. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
9. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
10. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
11. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com
12. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
13. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
14. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
15. Title:   Ancestry Family Trees
Page:   Database online.
Publication:   Name: Name: Online publication - Provo, UT, USA: Ancestry.com. Originaldata: Family Tree files submitted by Ancestry members.;;
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R2
Address:   http://www.Ancestry.com
Note continued:   This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
16. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA;Date:2006;;;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R1
Link:   http://www.ancestry.com



RootsWeb.com is NOT responsible for the content of the GEDCOMs uploaded through the WorldConnect Program. The creator of each GEDCOM is solely responsible for its content.