Import Results Page

< Minimum cMs

Number of DNA segments skipped with fewer than the minimum cMs as set in Preferences

< Minimum X cMs

Number of DNA segments skipped that were less than the minimum X cMs as set in Preferences

< Minimum SNPs

Number of DNA segments skipped with fewer than the minimum SNPs as set in Preferences

Anonymous

The number of entries skipped with “Anonymous” as the name.

Name Blank

The number of entries skipped having been interpreted to have no name recorded.
Look at the log file and investigate what might be wrong. You can edit the source spreadsheet and try loading it again until this error goes away. Sometimes it is a hidden character that you can’t see. The solution for this is to just manually re-enter.
Sometimes the issue is within the record before the "Name Blank" relative, possibly within the location field.

False Positive Region

A count of the number of DNA segments that fell into the false positive region that will be entered and were skipped. See False Positive Regions for more information.

Added

Number of Relatives or DNA segments added in this import

Updated

Number of Relatives or DNA segments updated

Match Merged

Record being imported was identified as already existing in the database and information was merged

Skipped Other Relative

Refers to data that involves a merged relative key not the same as the primary relative record. These can be toggled off and on in the lower right hand corner of the Relative Notes view.

ICW Not Shared

Refers to ICW data that does not connect with a segment shared between the profile and a relative. Only applies when the associated setting has been set in Import Criteria to True.

End Point Missing

For DNA segments, a valid base pair end point could not be found.
Typically if “1” it is safe to ignore.
If this number is high, check for issues in the Log File. You may have used the wrong template for the import data and source.

Key Fields Blank

The key fields are blank in the import file, you will need to investigate the download method for that file. The will be nothing in log file to work with.

Kit 1 Relative Not Found / Kit 2 Relative Not Found

Typically seen when a triangulation record cannot be entered because the associated Relative record could not be found.
Examination of the Log File can indicate if there is an actual problem or not.

Title Row

Can be safely ignored.

Triangulation Added

Number of Triangulation based data points added.

Triangulation Updated

Number of Triangulation data points updated.

Segment Skipped

Segment data found in triangulation imports that is ignored when existing data for that relative is found.

Too Few Columns

Indicates that a row in the input data file has fewer columns than required for the data import template.
A low number can usually be safely ignored, although this can also be an indication of an invalid character, such as a line break, being present in your import file. Review the results and act accordingly.
If the value is very high it can be an indication that the wrong option was potentially selected when importing data.
However, if you are importing a Gedmatch Tier 1 Triangulation, it is common to have a very high number here. Check that the “Added” and “Updated” values are also very high, and if they are, then you should be fine.

Unknown Relative Key

Only seen when importing an ahnentafel or tree file and indicates that the Relative record could not be found. Check the log file to see why these might have been flagged.

Invalid Ahnentafel Seq #

Only seen when importing an ahnentafel or tree file. Check the log file to see why these might have been flagged.