---
title: "How to get your Global25 coordinates, from any DNA test"
description: "Where Global25 coordinates come from, how to get them whether you tested with 23andMe, AncestryDNA, MyHeritage, FamilyTreeDNA, LivingDNA or a whole-genome sequencer, what every route costs, and how to tell a real coordinate row from a simulated one."
canonical: https://www.ancestrify.io/blog/how-to-get-global25-coordinates
date: 2026-08-24
updated: 2026-10-10
author: "Andi Thomaj"
---

# How to get your Global25 coordinates, from any DNA test

**The short answer:** there are two ways to get official Global25 coordinates, and both end at
the same source. The first is to order [Ancestry Map](/get-g25-coordinates), our Global25 analysis
(€29.99), and upload your raw DNA file instead of pasting a row: with your consent we obtain the
official coordinates for you from Davidski's independent Eurogenes G25 Requests portal (+€15, a
pass-through of the portal's per-kit fee), our analyst builds your calculator around them once they
arrive, and the row is yours to keep and reuse anywhere. The second is to order the row yourself at
[g25requests.app](https://g25requests.app/): upload the raw file from 23andMe, AncestryDNA,
MyHeritage, FamilyTreeDNA or LivingDNA (`.txt`, `.zip` or `.gz`), pay their €15 per-kit fee, and
receive the row; their site states 2 to 7 days. No testing company produces coordinates, and
neither do we: Ancestrify never computes or simulates them. Anything that claims to compute
coordinates instantly from your file is a simulation, not an official row.

The rest of this guide is the practical detail: what a coordinate is, what to do with the raw DNA
file from each testing company (and from a whole-genome sequencer), how the done-for-you route
works, every place that sells or simulates a row, and how to avoid the two mistakes that quietly
ruin every downstream result. It replaced the six vendor-by-vendor guides, the concierge
announcement and the coordinate buying directory on 2026-09-24, so one page holds everything.

## What a coordinate actually is

A Global25 coordinate is a single line of text: a label, then 25 numbers.

```
MyKit,0.121791,0.179749,0.026021,-0.069445,0.074783, ... ,0.010418
```

Those 25 values place one genome in a reference space built from ancient and modern samples. Every
distance ranking, admixture model and PCA plot you have seen built on G25 is arithmetic over rows
like that one.

Two consequences worth internalising before you go looking for yours:

- **A coordinate is not an ancestry result.** It is a position. It only means something relative to
  the other positions you compare it against.
- **Everything downstream inherits the row's quality.** A rounded, converted or simulated coordinate
  produces clean-looking rankings that describe the conversion rather than your genome.

## Where coordinates come from

This is the part that surprises people: **Global25 is not produced by the testing companies, and it
is not produced by us.**

Coordinates come from the independent Eurogenes Global25 service, the G25 Requests portal run by
Davidski, the author of the Eurogenes blog. You send a raw DNA file; you receive a coordinate row. It
is a separate service with its own process and its own charges, and nobody else can issue an
*official* Global25 coordinate for your genome.

That single fact answers most of the questions people arrive with:

- **Can my testing company give me my G25 coordinates?** No. None of them produce Global25.
- **Can Ancestrify generate them from my raw DNA?** Not generate (nobody but the Global25 service
  can), but we can **obtain** them for you. Order [Ancestry Map](/g25), upload your raw
  DNA file instead of pasting a row, and with your consent we handle the request to the official
  service on your behalf for a €15 fee; our analyst starts on your calculator the moment your
  coordinates arrive.
  [How that works, in detail](/get-g25-coordinates). If you would rather analyse the raw file
  directly, that is [Ancient Ancestry](/qpadm), our qpAdm analysis, a different method entirely.
- **Is there a free way?** There are third-party tools that *simulate* or convert coordinates from
  other calculators' output. They are not the same thing; see the buying directory below.

## Step one: get your raw DNA file

Whatever route you take, it starts with the raw data export from wherever you tested. Every major
company provides one; the wording differs, and so does what the file holds. Before you send any file
anywhere, our free [raw DNA file check](/lab/file-check) parses it, reports the format it detected,
counts usable markers per chromosome and tells you which analyses can read it. Nothing is ordered and
nothing is stored.

### 23andMe

In your 23andMe account, look under your profile for *Resources, Browse Raw Data, Download*. The
site asks you to confirm, then hands you a `.zip` holding a single `.txt` file, one genotyped position
per line. Downstream services accept the file zipped or unzipped; what matters is that you keep it.

23andMe has shipped several chip generations, and the generation decides your coverage. The current
v5 chip (in use since 2017, based on Illumina's Global Screening Array) reads roughly 640,000
positions with good autosomal coverage, the part Global25 is computed from, plus a useful set of
Y-chromosome and mitochondrial positions, which is why a 23andMe file also works in our free
[Y-DNA clade finder](/lab/clade-finder) and [mtDNA haplogroup finder](/lab/mt-finder). Older v3 and
v4 files still work but cover different marker sets.

### AncestryDNA

On your DNA results page, go to *Settings, Download DNA Data*. Unlike most vendors, **Ancestry does
not hand you the file immediately**: it emails a confirmation link first, and the download is only
released after you follow it. If nothing arrives, check spam before assuming the request failed; the
whole flow silently stalls on that one email. The download is a `.zip` holding a `.txt` file of
genotype calls.

AncestryDNA's chip reads roughly 650,000 to 700,000 positions with strong autosomal coverage, which is
exactly what a coordinate needs. The file also works in our free [Y-DNA clade finder](/lab/clade-finder),
with the caveat that consumer chips test a limited set of Y positions, so the depth you can reach is
set by the markers the file happens to contain.

### MyHeritage

Go to *DNA, Manage DNA kits, Download kit*. Like AncestryDNA (and unlike 23andMe), the file is not
handed over immediately: MyHeritage emails the download rather than serving it on the spot, so expect
a short wait and check spam if nothing arrives. The export is a `.zip` holding a `.csv` of genotype
calls.

One caveat is unique to MyHeritage and regularly surprises people. Its standard chip test covers
autosomes plus a set of Y-chromosome and mitochondrial positions. Its **low-pass whole-genome
product is different: the export carries autosomes and X only, no Y-chromosome rows and no
mitochondrial rows at all.** For Global25 this does not matter, because the coordinate is computed
from autosomal data. But if you also wanted a paternal or maternal haplogroup, a low-pass MyHeritage
kind of file you have.

### FamilyTreeDNA

In your FTDNA account, open *Family Finder, Download Raw Data* and choose the **autosomal build**
export. FTDNA publishes the same genotypes against two reference builds, Build 37 and Build 38, each
in a concatenated form that holds every chromosome in one file. **Prefer the Build 37 concatenated
export**: most third-party ancestry tools grew up on build 37 positions, and a build 38 file can be
misread by software that assumes the older coordinates. The file arrives as a compressed `.csv.gz`,
and the portal takes it as delivered, so there is no need to decompress it. FTDNA may ask you to
confirm your password before the files are released; if the option is missing altogether, the usual
reason is that the kit is a Y-DNA or mtDNA only order, or that Family Finder results have not yet
completed.

One point of frequent confusion: FTDNA sells several distinct products, and only **Family Finder**
produces the autosomal file this route needs. A Y-DNA or mtDNA product (Y-37, Big Y, mtFull) tests a
different part of the genome and its exports cannot become a Global25 coordinate. Those products
answer lineage questions instead, which is a different (and complementary) thing.

The Family Finder export is a comma-separated text file with a header row and four columns: RSID,
CHROMOSOME, POSITION and RESULT, one marker per line. Kits processed since around 2019 run on an
Illumina Global Screening Array based chip, older kits on an earlier array with a different marker
selection. Both produce valid raw files, but their overlap with the set the Global25 service projects
on differs, which shows up as slightly different fit quality rather than as different ancestry.

### LivingDNA

In your LivingDNA account, look under *Your account, Download raw data*: sign in, open your profile
(your name or the person icon at the top of the page), and look for a *Download raw data* entry either
directly under the profile menu or inside the account settings. LivingDNA asks you to confirm the
request, and the download itself is a zipped text file. Keep the `.zip` as delivered: the Global25
service accepts zipped files, and unzipping only creates a second copy to keep track of. If you manage
several kits in one account, check which profile is selected before you download.

LivingDNA genotypes on a Global Screening Array based chip customised for its own product, so the
23andMe-style text, with a comparatively generous set of Y-chromosome and mitochondrial positions
(haplogroups are a headline feature of their product). Note that a GSA-based export shares fewer
positions with the set the service projects on than a 23andMe v5 file does, so expect fit distances
in the [admixture calculator](/lab/admixture) to come out slightly larger than they would for the same
person tested on a chip with more overlap, and the last few dimensions to carry a little more noise.
The coordinate is still an official projection and every comparison remains valid; the effect is a
property of the input, not an error.

### Whole-genome sequencing

Whole-genome sequencing reads essentially every position; a genotyping chip reads under a million. So
it surprises people that turning a WGS result into coordinates takes *more* steps than starting from
a 23andMe file, not fewer. The reason is format: the coordinate pipeline was built around chip-style
raw files, and a WGS deliverable (VCF, BAM, CRAM, sometimes FASTQ) has to become chip-shaped
somewhere along the way. There are two honest routes, and one trap.

**Know what file you actually have.** WGS providers deliver some mix of FASTQ (raw reads), BAM or
CRAM (reads aligned to a reference genome) and VCF (called variants). For coordinate purposes the
aligned or called forms are the useful ones. Two things to check before anything else: which
*reference build* your files use (GRCh37/hg19 versus GRCh38; conversions must match, and a build
mismatch is the classic silent failure), and whether your provider's VCF includes reference calls or
only variants. A variants-only VCF must be handled as such or every unlisted position gets misread as
missing.

**Route one: let the coordinate service convert it.** The G25 Requests portal accepts WGS deliverables
directly, at a stated surcharge for the conversion work: their posting lists VCF, BAM, CRAM and FASTQ
handling at roughly €30 to €50 *on top of* the standard €15 per kit, depending on the case. You send
the file, they extract a chip-style genotype set, compute the official row, and return scaled and
unscaled forms as usual. This is the lowest-effort route and the numbers are theirs to set; its cost
profile makes most sense for BAM and CRAM inputs, where the extraction genuinely takes work.

**Route two: convert it yourself, then order normally.** The free community tool WGSExtract takes a
BAM or CRAM and emits chip-format raw files, including a 23andMe-style text file, which the portal
then accepts at the ordinary €15 rate, exactly as if a chip had produced it. The catches are real but
manageable: you need the disk space and patience for BAM processing, you must feed it the right
reference build, and the output should be sanity-checked before ordering. Run it through the
[file check](/lab/file-check) and confirm the marker counts per chromosome look like a dense chip file
rather than a sparse extraction. A well-made WGS extraction typically *beats* a real chip file on call
quality: fewer no-calls, no chip-batch artefacts. If your provider gave you only a VCF, conversion is
still possible but the variants-only issue above decides everything; when in doubt, route one exists
precisely for these cases.

**The trap: "G25 from VCF" converters.** Tools that promise instant G25 coordinates computed *from*
your file, skipping the official service, produce simulated rows: numbers shaped like a coordinate
that describe the conversion, not a projection into the actual Global25 space.

**Where the WGS actually shines.** A whole genome is overkill for the coordinate itself; the
projection uses chip-scale markers either way. Where the extra coverage pays is everywhere else: a
WGS-derived file supports deep [Y-DNA](/lab/clade-finder) and [mtDNA](/lab/mt-finder) haplogroup
calls, and our [Ancient Ancestry](/qpadm) and [Ancient Matches](/ancient-matches) analyses accept whole-genome
VCFs directly (a €10 add-on covers the heavier processing,
[details here](/blog/upload-whole-genome-vcf-ancestry)), where the added markers genuinely tighten
standard errors. So the sensible WGS plan is usually: coordinates once via either route above, and the
raw power spent on the analyses that can use it.

## Step two: request the coordinates

Submit the raw file to Davidski's G25 Requests portal at [g25requests.app](https://g25requests.app/)
and follow its current instructions. Their site states a €15 fee per kit and delivery in 2 to 7 days;
the process and terms are the service's own and have changed more than once, so the operator's own
posting is the only authority worth trusting on the details.

**Submitting the file.** Upload the file as the vendor delivered it (zipped is fine), pay the per-kit
fee on their hosted checkout, and wait for the email with your row. Give the kit a label you will
recognise, because it becomes the first field of the coordinate row and travels with it into every
tool you paste it into.

**If the file is rejected.** A rejection at upload is nearly always packaging, not genotype. Work
through these in order: make sure you uploaded the file the vendor delivered rather than a copy
re-saved from a spreadsheet or text editor, which can strip the header, change the delimiter or the
line endings; make sure it is the raw data export and not a results report or a PDF; for FTDNA, make
sure it is the concatenated Family Finder file rather than a per-chromosome or a Y-DNA export, and try
the Build 37 file if you uploaded Build 38; a file far smaller than a normal export is an interrupted
download, so download it again. Past that, the portal's own posting is the authority on what it
currently accepts.

Two practical notes that survive every change of terms:

- **You will get scaled and unscaled forms.** Keep both, keep them labelled, and never mix them in
  one comparison (see below).
- **Store the row somewhere stable.** It is a line of text that took real effort to obtain, and every
  tool you use later wants it again.

When the row arrives, check it before building on it:

## The Coordinate Concierge

Prefer not to handle the request yourself? Order [Ancestry Map](/g25) and choose **Upload raw
file** instead of pasting coordinates. Hand us the raw data export you already have from 23andMe,
AncestryDNA, MyHeritage, FamilyTreeDNA, LivingDNA or a similar company: the same file, no new test.

With your explicit consent, asked plainly at checkout, never assumed and never pre-ticked, we pass
your file securely to the official Global25 provider, who produces your personal coordinates by hand,
typically within a few days depending on their queue. The moment they arrive, our analyst starts
building your calculator around them, and once a person has approved it your report opens: ranked
distances, admixture models and an individual-sample PCA across six eras, and we email you when it
is ready. The service costs **€15 on top of the €29.99 analysis**, a pass-through
of the provider's own per-kit fee, which exists whichever route you take. There is no markup on it.

**What you upload.** The standard autosomal raw-data export from a consumer array test, as a `.txt`,
`.zip` or `.gz` up to 50 MB, exactly as the vendor delivered it. A whole-genome VCF is not accepted on
this route (use one of the WGS routes above first), and an unreadable, truncated or edited file is
refused at checkout, before any payment.

**While your coordinates are pending.** After checkout the order does not sit in a queue of ours; it
waits for the provider. The order shows an awaiting-coordinates state on your dashboard, and it stays
there until the official row arrives. Nothing is computed in the meantime, because there is nothing
yet to compute from. You do not need to check back: the moment the row is recorded against your order
our analyst starts building your calculator, and we email you when the report is ready.

**The row is the real thing, and it is yours.** We never compute coordinates ourselves; nobody but
the Global25 service can. What you receive is the same official row enthusiasts order directly, not a
simulation and not a conversion. It appears in your report, and you can reuse it anywhere Global25
coordinates are accepted, including every one of [our free G25 tools](/lab) and any later order, where
pasting it costs nothing extra. The €15 covers obtaining the coordinates once and is never charged
again for the same row. Your file moves only with your consent: the disclosure to the provider is a
separate, explicit checkbox at checkout, distinct from the consent that covers our own processing.

| | Do it yourself | Coordinates done for you |
| --- | --- | --- |
| Where the row comes from | The independent Eurogenes G25 Requests portal | The same portal, with the request placed by us |
| What you handle | Download, upload to the portal, payment, waiting, then pasting the row into an order | Upload the raw file once at checkout and consent to the disclosure |
| Cost of the row | €15 per kit, as stated on their site | +€15 on the €29.99 analysis, a pass-through of the same fee |
| Wait | Their site states 2 to 7 days | The same provider, so the same kind of wait; our analyst starts on your calculator the moment the row arrives |
| Your data | You send the file to the portal yourself | Your file is shared with the provider only after your explicit checkout consent |
| What you end up with | The official scaled and unscaled rows | The official row, shown in your report, plus the full six-era analysis |

Both routes end at the same service and produce the same row. The concierge exists for people who
would rather not manage the detour, not because it produces anything different. And if you already
have your coordinate row, nothing changes: paste it as always, at €29.99, and our analyst builds
your calculator around it.

## Step three: use the coordinate

Once you have a row, everything else is fast. You can, entirely free and without an account:

- Rank your closest reference populations across six eras in the
  [G25 distance calculator](/lab/g25-distance).
- Model your ancestry as a mixture of sources in the
  [admixture calculator](/lab/admixture).
- Plot yourself on ancient-DNA PCA views in the [G25 PCA viewer](/lab/g25-pca).
- Average several rows into a population coordinate with [Average G25](/lab/average-g25).
- Audit a row's numeric fingerprint with the
  [authenticity check](/lab/g25-authenticity).

And if you want the full report (distances, admixture and PCA across six eras with cinematic
exports), that is [Ancestry Map](/g25).

## The two mistakes that ruin results

**Mixing scaled and unscaled coordinates.** The scaled form weights each dimension by its share of
the variance; the unscaled form treats all 25 equally. Comparing a scaled row against an unscaled
panel produces distances that are pure noise, and the numbers still come out looking perfectly
reasonable. Nothing will warn you. Check which form your row is before you compare it against
anything.

**Treating a simulated coordinate as a real one.** Several free tools convert output from other
calculators (K36 and similar) into something shaped like a Global25 row. These are useful for play
and useless for conclusions: the result describes the conversion's assumptions, not your genome, and
its precision is often visibly degraded. If you did not obtain the row from the Global25 service
itself, say so whenever you share a result. Our [authenticity check](/lab/g25-authenticity) reads the
numeric signature (precision loss, out-of-range values, editing patterns), though it audits the
numbers, not the provenance: it cannot prove a row is yours.

## Where to buy G25 coordinates

There is exactly one source of official Global25 coordinates, and it is not a testing company and it
is not us. Every other route either obtains the official row from that source on your behalf, computes
a different row in a space of its own, or simulates one from a calculator's percentages. Those three
things are sold under the same four words, so this directory keeps them apart. I run one of the
services below, [Ancestry Map](/g25), Ancestrify's Global25 analysis, so every competitor entry is kept to what
is readable on the competitor's own site, with "not stated on their site" where it is not. Facts were
read on each site on 2026-09-01 and may have changed since.

**The official row.** A single line of 25 numbers produced by projecting your raw DNA file into the
Global25 reference space. That space is private to its author, Davidski of the Eurogenes project, so
only his G25 Requests portal can place a new sample into it. This is the row every tool in the hobby
was built for.

**A derived row.** Some services compute coordinates from your file in a space of their own
construction and call the result G25 coordinates. The numbers look the same, and they work inside
that service's own tools, but they are not the official row and will not land where the official row
lands against the public reference spreadsheets.

**A simulated row.** Converter tools take the percentages a calculator produced (a GEDmatch K36 run,
for instance) and manufacture a 25-number row from them. The row describes the calculator's output,
not your genome. It is free, and it is the most common reason a beginner's distances make no sense.

| Route | Official row | Price | Turnaround | What you receive |
| --- | --- | --- | --- | --- |
| G25 Requests portal, g25requests.app | Yes | 15 EUR per kit, as stated on their site | Their site states results by email within seven days | The official scaled and unscaled rows; payment on Stripe's hosted checkout; the file is deleted after processing |
| Ancestrify Coordinate Concierge | Yes, the same portal | 15 EUR on a 29.99 EUR analysis, a pass-through of the same fee | Typically two to five days, then our analyst builds your calculator | The same official row, shown in your report, plus the full six-era analysis on [a calculator built around it](/blog/personalized-g25-calculator) |
| DNAGENICS | No, derived | 14 EUR one-time, as stated on their site | Not stated on their site | Genome-wide scaled and unscaled coordinates plus per-chromosome rows, computed by their own projection for their own G25 Studio tools |
| Genoplot | No, simulated | Free on the Free tier; paid tiers add a yearly allowance | Not stated | A Geno25 coordinate simulation; their own name for it is the honest tell |
| ExploreYourDNA and converters such as Allelocator | No, simulated | Free | Immediate | A row manufactured from a K36 or similar calculator run; ExploreYourDNA's own site sends people to the official portal for the real thing, and so do we |

The first two rows are the same coordinate through two doors. The third we list because people ask;
it is the cheapest row here and a reasonable one if you intend to stay inside their studio, but it is
not the official row, and the difference shows the moment you compare against the public reference
spreadsheets. The last two are fine for play and unfit for any conclusion you would repeat to someone
else.

A checklist for choosing:

1. **Do you need the official row?** If you will use Vahaduo, our Lab, or any tool calibrated on the
   public reference spreadsheets, yes. A derived or simulated row will mislead every one of them.
2. **Do you want only the row, or the row and an analysis?** Only the row: the portal, 15 EUR. Both:
   the Concierge route, where the 15 EUR is the same fee passed through and the analysis is ready when
   the row is.
3. **Check the file first.** The [free file check](/lab/file-check) tells you whether your export can
   support coordinates before anyone charges you.
4. **Check the row afterwards.** Ten seconds in the [authenticity check](/lab/g25-authenticity) is
   cheaper than an evening reading distances a rounded paste produced.

## Questions people ask on Reddit and forums

The same handful of questions come up every week on r/23andme, r/Genealogy, Anthrogenica's
successors and the Eurogenes comment threads. We answer them here in one place, plainly, and we
will keep this section current as the service's terms change.

**Is g25requests.app legitimate?** Yes. It is the request portal for Davidski's Eurogenes
Global25 service, the same service that has issued Global25 coordinates since 2019 and whose
reference rows every G25 calculator and spreadsheet on the internet is built from. The portal is
where you upload your raw file, pay the per-kit fee and receive your row. It is an independent
one-person service, not a company with a support desk, and its terms have changed more than once,
so the page itself is the only authority on what it currently charges and how it wants files sent.
We have no affiliation with it beyond being a customer on your behalf when you ask us to be.

**Is there a free way to get G25 coordinates?** Not an official one. What the free tools offer is
a *simulated* row: they take the output of another calculator, usually a K36 or similar admixture
breakdown, and convert it into 25 numbers shaped like a Global25 coordinate. The result describes
the conversion's assumptions, not your genome. Simulated rows also carry a numeric fingerprint,
typically reduced precision and values that sit in ranges real rows do not, and our free
[authenticity check](/lab/g25-authenticity) will usually flag one as converted rather than
computed. If you want a coordinate that means something in a comparison, there is no free route;
the only issuer is the service above.

**How long does it take?** Their site states 2 to 7 days from upload to delivery. That figure is
theirs, not ours, and it has varied with demand; the request portal is the place to check the
current statement before you plan around it.

**Can anyone compute the coordinates from my file?** No. The Global25 PCA is defined by a
private reference set held by the service, and a row is only "official" if it was projected onto
that exact space by the service itself. Someone with your raw file and a copy of the public
reference rows can produce something that looks like a coordinate, but it is not one. Ancestrify
never computes Global25 coordinates. What we can do, with your consent, is obtain the official row
for you: add the 15 EUR concierge option to an Ancestry Map order at
[/get-g25-coordinates](/get-g25-coordinates), upload the raw file, and our analyst starts on your
calculator the moment the service returns your row. The row is yours to keep and reuse anywhere.

**What does a real row look like?** A label, then 25 comma-separated decimal numbers, on a single
line. Something like `MyKit,0.1234,0.0521,-0.0087,...` continuing to the twenty-fifth value. You
receive two versions of the same row: **scaled**, in which each dimension is weighted by the
share of the variance it explains, and **unscaled**, in which all 25 dimensions carry equal weight.
Both are correct; they are simply for different comparisons, and every tool and spreadsheet
expects one or the other. Keep both, keep them labelled, and never place a scaled row against an
unscaled panel. The distances will still come out looking reasonable, and they will be meaningless.

**Do I need to convert my raw file first?** No. The service reads the standard exports from
23andMe, AncestryDNA, MyHeritage, FamilyTreeDNA and LivingDNA as they come; the vendor-specific
steps are in step one above. Only a whole-genome deliverable needs converting, and the portal will
do that for a surcharge if you would rather not.

**Will a new test give me different coordinates?** Slightly, if the chip differs, because the
overlap with the service's marker set changes and a few dimensions will move in the third or
fourth decimal place. A LivingDNA row and a 23andMe row for the same person are both official;
treat the differences as the noise floor of the method rather than as a disagreement about your
ancestry. The row is not a fixed property of you in the way a haplogroup is; it is a projection of
whichever genotypes the file carried.

**Can I use my FamilyTreeDNA or LivingDNA file in the free haplogroup finders?** Not at present.
The free [Y-DNA clade finder](/lab/clade-finder) and [mtDNA finder](/lab/mt-finder) read 23andMe,
AncestryDNA and MyHeritage exports (the clade finder also takes a VCF); Family Finder and LivingDNA
files are not among the supported formats, and both companies already report haplogroups in their
own results.

## A note on what coordinates cannot do

A coordinate fit always returns percentages, has no p-value and cannot reject a model. That is a
property of the method, not a flaw in any particular tool. If you need an answer that can come back
negative, a test rather than a fit, the method for that is qpAdm, and the difference is worth
understanding before you over-read a breakdown:
[qpAdm vs Global25](/blog/qpadm-vs-global25).

Terms used here are defined in the [glossary](/glossary).