Answers.Body: <p>This question has gone through some iterations and commentary, so I've decided to just answer it, though it's more of a &quot;homework&quot; question. What you need to do is to look at the VCF file, the main thing you want is already in there.</p>
  <p>Go to the VCF of interest. I chose the <a href="https://storage.googleapis.com/gcp-public-data--gnomad/release/3.1/vcf/genomes/gnomad.genomes.v3.1.sites.chrM.vcf.bgz" rel="nofollow noreferrer">mtDNA</a> because it's smaller and more convenient. You can <code>zless</code> into the bgz file to see what it looks like, but if you want uncompressed you can run this (head -1000 just to be a tractable example):</p>
  <pre><code>gzip -dc gnomad.genomes.v3.1.sites.chrM.vcf.bgz | grep -v intergenic | head -1000 &gt; mt.vcf
  </code></pre>
  <p>I <code>grep -v intergenic</code> because one of the first things that pops up is that most of the first variants in the file are specifically annotated as <code>intergenic_variant</code>, so that answers part of your question. For those variants you can just run a <a href="https://bedtools.readthedocs.io/en/latest/content/tools/closest.html" rel="nofollow noreferrer">bedtools closest</a> against the right GFF3 version, if you think the nearest gene will be informative.</p>
  <p>For variants in genes, what you want is already in the VCF. See the entry for this variant:</p>
  <pre><code>chrM    1492    .       A       C       .       npg     filters=npg;variant_colla
  psed=A1492C;vep=C|non_coding_transcript_exon_variant|MODIFIER|MT-RNR1|ENSG0000021
  1459|Transcript|ENST00000389680|Mt_rRNA|1/1||ENST00000389680.2:n.845A&gt;C||845|||||
  1||1|SNV||HGNC|HGNC:7470|YES||||||||1||||||||||||;base_qual_hist=0|0|0|0|0|0|0|0|
  0|0;position_hist=0|0|0|0|0|0|0|0|0|0;strand_bias_hist=0|0|0|0|0|0|0|0|0|0;weak_e
  vidence_hist=0|0|0|0|0|0|0|0|0|0;contamination_hist=0|0|0|0|0|0|0|0|0|0;heteropla
  smy_below_min_het_threshold_hist=2|0|0|0|0|0|0|0|0|0;excluded_AC=2;AN=56432;AC_ho
  m=0;AC_het=0;hl_hist=0|0|0|0|0|0|0|0|0|0;dp_mean=2976.53;mq_mean=.;tlod_mean=.;AF
  _hom=0.00000;AF_het=0.00000;max_hl=0.00000;hap_AN=2680|1537|868|603|34|282|91|147
  83|701|934|3144|2732|663|2977|4724|5672|126|1|1298|366|7|393|3079|6037|1234|819|5
  46|12|89;hap_AC_het=0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0;hap
  _AC_hom=0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0;hap_AF_hom=0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00;hap_AF_het=0.00000e+00|0.00000e+00|0.00 ...
  # this is of course a very long line!!! it goes on but all the interesting stuff already happened.
  </code></pre>
  <p>You can see that this variant lies within the <em>RNR1</em> rRNA gene of the mitochondrial genome (<code>MT-RNR1</code> in the file). Granted it mangles it a little bit by describing a variant in a non-protein-coding gene as a <code>non_coding_transcript_exon_variant</code>, but that's the kind of thing that you can work around.</p>
  <p>Indeed, if you look at the header of the file, you can see that quite extensive annotations are included (where available):</p>
  <pre><code>##INFO=&lt;ID=vep,Number=.,Type=String,Description=&quot;Consequence annotations from Ensembl VEP; note that the SINGLE_EXON flag and END_TRUNC filters have been removed from the LOFTEE annotations to avoid misinterpretation in context of the mitochondrial genome. Format: Allele|Consequence|IMPACT|SYMBOL|Gene|Feature_type|Feature|BIOTYPE|EXON|INTRON|HGVSc|HGVSp|cDNA_position|CDS_position|Protein_position|Amino_acids|Codons|ALLELE_NUM|DISTANCE|STRAND|VARIANT_CLASS|MINIMISED|SYMBOL_SOURCE|HGNC_ID|CANONICAL|TSL|APPRIS|CCDS|ENSP|SWISSPROT|TREMBL|UNIPARC|GENE_PHENO|SIFT|PolyPhen|DOMAINS|HGVS_OFFSET|MOTIF_NAME|MOTIF_POS|HIGH_INF_POS|MOTIF_SCORE_CHANGE|LoF|LoF_filter|LoF_flags|LoF_info&quot;&gt;
  </code></pre>
  <p>In conclusion, <strong>look at your data</strong>!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-27T08:07:47.337Z
Answers.LastActivityDate: 2022-12-27T08:07:47.337Z
Answers.UserDisplayName: Maximilian Press
Body: <p>I was wondering does the gnomad genome data that is downloaded in the vcf format on variants contain information on what is the nearest gene and is the genomic location available exome/intron?</p>
  <p>if yes then what are the columns that contain this data? Is it the INFO column?</p>
  <p>I have a list of SNPs  with chromosome position and the reference and alternative allele information and for each, I would like to know what is he nearest gene and the location:exome/intron.</p>
  <p>example data</p>
  <p><a href="https://i.sstatic.net/QcvkZ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/QcvkZ.png" alt="enter image description here" /></a></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-27T07:49:16.500Z
Comments.Text: We would need to see all the columns of the gnomad VCF, see e.g. [here](https://storage.googleapis.com/gcp-public-data--gnomad/release/3.1/vcf/genomes/gnomad.genomes.v3.1.sites.chrM.vcf.bgz) the mtDNA VCF (the smallest file), the information you are looking for should be described in the header. As stated on the other question, if you want to know the nearest gene, the [intersect operation via bedtools](https://bedtools.readthedocs.io/en/latest/content/tools/intersect.html) is pretty trivial to combine this VCF with a human genome GFF3 file (of the appropriate genome build).
Comments.UserDisplayName: Maximilian Press
Tags: <vcf><genome><gene><exon><gnomad>
Title: Availability of information on genes in Gnomad VCF data
ThreadText: # Availability of information on genes in Gnomad VCF data
  
  (Asked by: username_0 on 2022-12-26)
  
  I was wondering does the gnomad genome data that is downloaded in the vcf format on variants contain information on what is the nearest gene and is the genomic location available exome/intron?
  
  if yes then what are the columns that contain this data? Is it the INFO column?
  
  I have a list of SNPs with chromosome position and the reference and alternative allele information and for each, I would like to know what is he nearest gene and the location:exome/intron.
  
  example data
  
  [![enter image description here](https://i.sstatic.net/QcvkZ.png)](https://i.sstatic.net/QcvkZ.png)
  
  **Tags:** vcf, genome, gene, exon, gnomad
  
  > **Comments:**
  > **username_1**: We would need to see all the columns of the gnomad VCF, see e.g. [here](https://storage.googleapis.com/gcp-public-data--gnomad/release/3.1/vcf/genomes/gnomad.genomes.v3.1.sites.chrM.vcf.bgz) the mtDNA VCF (the smallest file), the information you are looking for should be described in the header. As stated on the other question, if you want to know the nearest gene, the [intersect operation via bedtools](https://bedtools.readthedocs.io/en/latest/content/tools/intersect.html) is pretty trivial to combine this VCF with a human genome GFF3 file (of the appropriate genome build).  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-12-27. Score: 4 | Accepted answer
  
  This question has gone through some iterations and commentary, so I've decided to just answer it, though it's more of a "homework" question. What you need to do is to look at the VCF file, the main thing you want is already in there.
  
  Go to the VCF of interest. I chose the [mtDNA](https://storage.googleapis.com/gcp-public-data--gnomad/release/3.1/vcf/genomes/gnomad.genomes.v3.1.sites.chrM.vcf.bgz) because it's smaller and more convenient. You can `zless` into the bgz file to see what it looks like, but if you want uncompressed you can run this (head -1000 just to be a tractable example):
  
  ```
  gzip -dc gnomad.genomes.v3.1.sites.chrM.vcf.bgz | grep -v intergenic | head -1000 > mt.vcf
  
  ```
  
  I `grep -v intergenic` because one of the first things that pops up is that most of the first variants in the file are specifically annotated as `intergenic_variant`, so that answers part of your question. For those variants you can just run a [bedtools closest](https://bedtools.readthedocs.io/en/latest/content/tools/closest.html) against the right GFF3 version, if you think the nearest gene will be informative.
  
  For variants in genes, what you want is already in the VCF. See the entry for this variant:
  
  ```
  chrM    1492    .       A       C       .       npg     filters=npg;variant_colla
  psed=A1492C;vep=C|non_coding_transcript_exon_variant|MODIFIER|MT-RNR1|ENSG0000021
  1459|Transcript|ENST00000389680|Mt_rRNA|1/1||ENST00000389680.2:n.845A>C||845|||||
  1||1|SNV||HGNC|HGNC:7470|YES||||||||1||||||||||||;base_qual_hist=0|0|0|0|0|0|0|0|
  0|0;position_hist=0|0|0|0|0|0|0|0|0|0;strand_bias_hist=0|0|0|0|0|0|0|0|0|0;weak_e
  vidence_hist=0|0|0|0|0|0|0|0|0|0;contamination_hist=0|0|0|0|0|0|0|0|0|0;heteropla
  smy_below_min_het_threshold_hist=2|0|0|0|0|0|0|0|0|0;excluded_AC=2;AN=56432;AC_ho
  m=0;AC_het=0;hl_hist=0|0|0|0|0|0|0|0|0|0;dp_mean=2976.53;mq_mean=.;tlod_mean=.;AF
  _hom=0.00000;AF_het=0.00000;max_hl=0.00000;hap_AN=2680|1537|868|603|34|282|91|147
  83|701|934|3144|2732|663|2977|4724|5672|126|1|1298|366|7|393|3079|6037|1234|819|5
  46|12|89;hap_AC_het=0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0;hap
  _AC_hom=0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0;hap_AF_hom=0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00|0.00000e+00;hap_AF_het=0.00000e+00|0.00000e+00|0.00 ...
  # this is of course a very long line!!! it goes on but all the interesting stuff already happened.
  
  ```
  
  You can see that this variant lies within the *RNR1* rRNA gene of the mitochondrial genome (`MT-RNR1` in the file). Granted it mangles it a little bit by describing a variant in a non-protein-coding gene as a `non_coding_transcript_exon_variant`, but that's the kind of thing that you can work around.
  
  Indeed, if you look at the header of the file, you can see that quite extensive annotations are included (where available):
  
  ```
  ##INFO=<ID=vep,Number=.,Type=String,Description="Consequence annotations from Ensembl VEP; note that the SINGLE_EXON flag and END_TRUNC filters have been removed from the LOFTEE annotations to avoid misinterpretation in context of the mitochondrial genome. Format: Allele|Consequence|IMPACT|SYMBOL|Gene|Feature_type|Feature|BIOTYPE|EXON|INTRON|HGVSc|HGVSp|cDNA_position|CDS_position|Protein_position|Amino_acids|Codons|ALLELE_NUM|DISTANCE|STRAND|VARIANT_CLASS|MINIMISED|SYMBOL_SOURCE|HGNC_ID|CANONICAL|TSL|APPRIS|CCDS|ENSP|SWISSPROT|TREMBL|UNIPARC|GENE_PHENO|SIFT|PolyPhen|DOMAINS|HGVS_OFFSET|MOTIF_NAME|MOTIF_POS|HIGH_INF_POS|MOTIF_SCORE_CHANGE|LoF|LoF_filter|LoF_flags|LoF_info">
  
  ```
  
  In conclusion, **look at your data**!
  
  
  ---
  
  