Update faqs 20250922 Geographic metadata FAQ & fix typos#14
Open
DeondeJager wants to merge 4 commits intomasterfrom
Open
Update faqs 20250922 Geographic metadata FAQ & fix typos#14DeondeJager wants to merge 4 commits intomasterfrom
DeondeJager wants to merge 4 commits intomasterfrom
Conversation
- Filled-in geographic metadata FAQ. - Fixed a couple of typos.
jfy133
reviewed
Nov 17, 2025
Contributor
jfy133
left a comment
jfy133
left a comment
There was a problem hiding this comment.
Looks good as first pass! Mostly maybe consider removing a bit of the detail that is already in the term itself, and give examples with the aDNA specific implementation
Updated geography FAQ by removing some details and adding an example.
jfy133
reviewed
Jan 12, 2026
Contributor
jfy133
left a comment
jfy133
left a comment
There was a problem hiding this comment.
Additional minor comments
| _TODO_ | ||
|
|
||
| ## How to fill in geographic metadata | ||
| There are two primary ways of providing the geographic location of a sample with existing MIxS terms: `Geographic location (latitude and longitude)` and `Geographic location (country and/or sea,region)`. Both of these are required fields and we suggest filling in at both terms with as precise information as possible. There is also a third term that is specific to the ancient DNA MInAS checklist, `Name of site or location where sample was originated`, which should be used to record the name of the archaeological/palaeontological site. |
Contributor
There was a problem hiding this comment.
Suggested change
| There are two primary ways of providing the geographic location of a sample with existing MIxS terms: `Geographic location (latitude and longitude)` and `Geographic location (country and/or sea,region)`. Both of these are required fields and we suggest filling in at both terms with as precise information as possible. There is also a third term that is specific to the ancient DNA MInAS checklist, `Name of site or location where sample was originated`, which should be used to record the name of the archaeological/palaeontological site. | |
| There are two primary ways of providing the geographic location of a sample with existing MIxS terms: `Geographic location (latitude and longitude)` and `Geographic location (country and/or sea,region)`. | |
| Both of these are required fields and we suggest filling in at both terms with as precise information as possible. | |
| There is also a third term that is specific to the ancient DNA MInAS checklist, `Name of site or location where sample was originated`, which should be used to record the name of the archaeological/palaeontological site. |
|
|
||
| _TODO_ | ||
| - **Geographic location (latitude and longitude)**: | ||
| - The MIxS term [`Geographic location (latitude and longitude)`](https://genomicsstandardsconsortium.github.io/mixs/0000009/) is used to record the coordinates in decimal degrees, limited to 8 decimal points and separated by a single whitespace (e.g. `-39.27774231 175.61028236`). While limited to 8 decimal points, you will rarely need such precision, unless you've extracted DNA from a [specific grain of sand](https://xkcd.com/2170/). See [here](https://en.wikipedia.org/wiki/Decimal_degrees) to guide your decision on the appropriate level of precision to report. |
Contributor
There was a problem hiding this comment.
The grain of sand thing should maybe go as a footnote using [^1] and [^1]: description syntax
Need to rewrite this FAQ once site location terms have been added (see MIxS-MInAS/extension-ancient#45 (comment))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.