rsid
The variant identifier. Rows beginning with a public rs identifier or an imported-provider “i” identifier are accepted; the literal header value “rsid” is skipped.
Aquest contingut encara no està disponible en català. El mostrem en anglès.
Already downloaded your AncestryDNA data?
Turn the original AncestryDNA text export into a report that distinguishes clinical records, genotype-specific medication evidence and research associations. The importer understands Ancestry’s split allele columns, skips its no-calls and reports the coverage this particular file supports instead of assuming every consumer chip is equivalent.
The tested input is a tab-separated text file with one variant per row. DNA Info Lab recognises an AncestryDNA banner, the words “Ancestry DNA”, or a tab-separated allele1 header near the start of the file. Recognition is based on the file’s observable structure, not its filename alone.
The variant identifier. Rows beginning with a public rs identifier or an imported-provider “i” identifier are accepted; the literal header value “rsid” is skipped.
The chromosome label supplied by AncestryDNA. It is stored with the imported variant rather than reclassified by the parser.
The integer coordinate in the export. A row with a missing or non-numeric position is not imported.
The first reported allele. DNA Info Lab trims the field and requires a non-zero value.
The second reported allele. The parser trims line endings, validates the value and joins allele1 plus allele2 into the stored genotype.
If either allele column is empty or contains “0”, that row is skipped. A 0 is not a reference allele and it is not evidence that the person lacks a variant: it means the array did not return a usable call for that position.
AncestryDNA raw data comes from microarray genotyping: selected genomic positions are measured and written as allele pairs. The export is not a whole-genome sequence, an exome sequence or a clinical laboratory report.
This is especially important when interpreting an empty result. A position can be absent because the array design did not include it, because the chip returned 0 at one or both alleles, or because DNA Info Lab’s current filtered catalogues contain no supported record for that rsID.
The importer cannot recover unmeasured positions or infer rare variants between array markers. The report describes matches in the supplied file and keeps missing coverage visible; it never treats missing rows as favourable genetic evidence.
The parser retains the chromosome and numeric position that AncestryDNA wrote, then uses rsID as the catalogue identity. It does not infer the reference build from row count, convert coordinates between genome builds or change allele orientation.
Matching by rsID prevents a coordinate alone from being mistaken for a different build, but alleles still matter. GWAS dosage and PharmGKB genotype matches use the imported allele pair, so a manually converted or strand-flipped file can change downstream matching.
Use the untouched provider download. The checker and report can describe the observed format; neither currently certifies a genome build or array generation that is not explicitly and reliably present in the file.
Usable AncestryDNA genotypes are compared with three evidence catalogues. A match in one source is not silently promoted into another kind of claim.
Shared rsIDs can surface imported ClinVar classifications, condition records, review status and provenance. Consumer array calls can be wrong, so a potentially important match needs accredited clinical confirmation.
A medication annotation is shown only when the rsID and combined allele1/allele2 genotype match the imported PharmGKB record. It is context for a professional conversation, not a prescribing instruction.
A genotype can contribute to research associations when it contains the catalogue’s effect allele. DNA Info Lab shows the trait, study, effect unit and population context and does not convert that association into a diagnosis.
AncestryDNA has used different array designs over time, and valid exports need not contain identical marker sets. Coverage is therefore calculated from the positions actually imported, not from a provider-wide promise or a hard-coded marketing total.
The number of physical positions is also different from the number of studies, clinical condition records or medicines. One rsID can be linked to several studies or ClinVar conditions, while many imported positions may have no entry in the filtered sources. The report labels each unit explicitly.
DNA Info Lab does not promise that an AncestryDNA file will reproduce a report generated from 23andMe or MyHeritage. Provider, array design, no-call rate and catalogue version all affect overlap. An honest empty area is a valid result, not a reason to fill it with weaker claims.
The public raw-file example renders and downloads the five-column AncestryDNA shape from one shared source: rsid, chromosome, position, allele1 and allele2, including a synthetic 0/0 no-call. The rows are invented for education and contain nobody’s DNA.
Open the annotated raw-file example →Use AncestryDNA’s data settings to request the original raw-data archive. Upload its TXT or recognised ZIP without opening and resaving it in spreadsheet software, which can alter tabs, identifiers and long numeric values.
How to download AncestryDNA raw data →DNA Info Lab parses the original AncestryDNA file in server memory and discards that original upload. Extracted variants and derived report results remain on the service’s EU infrastructure so the account can revisit the analysis, until deletion or an applicable retention rule removes them.
A usable row has rsid, chromosome, position, allele1 and allele2 separated by tabs. Comment and header rows are skipped.
It is a no-call: the array did not produce a usable allele at that position. DNA Info Lab skips the whole row rather than treating 0 as a biological allele.
Yes. After validation, allele1 and allele2 are joined in their file order into the genotype used by the report.
No. It recognises the file structure, retains the supplied coordinates and matches by rsID. It does not infer array generation, certify a build, lift coordinates or flip strands.
Not necessarily. Different arrays measure different marker sets, and no-calls and catalogue overlap differ. Each report states coverage from its own imported positions.
No. DNA Info Lab does not calculate ancestry percentages, identify relatives or reconstruct family trees. Its report cross-references the supplied genotypes with scientific catalogues.
Yes. The annotated public example is synthetic, and the file checker performs its initial structural check locally in the browser.
No. Processing and the defined free findings are shown before the optional one-time purchase of the complete report.
Upload the untouched raw-data file, review its real coverage and free findings, then decide whether the complete sourced report is useful to you.
Analyse my AncestryDNA file →