{"id":6657,"date":"2021-09-02T14:50:00","date_gmt":"2021-09-02T18:50:00","guid":{"rendered":"https:\/\/ncbiinsights.ncbi.nlm.nih.gov\/?p=6657"},"modified":"2021-09-07T11:48:44","modified_gmt":"2021-09-07T15:48:44","slug":"64-bit-gis","status":"publish","type":"post","link":"https:\/\/ncbiinsights.ncbi.nlm.nih.gov\/2021\/09\/02\/64-bit-gis\/","title":{"rendered":"NCBI’s GI sequence identifiers will soon exceed 32-bit numbers. Are you and your software ready?"},"content":{"rendered":"

In 2016, NCBI\u00a0announced<\/a> that it was curtailing its display of its numeric ‘GI’ in popular sequence data formats such as FASTA and GenBank flatfiles. Due to the continued growth of GenBank, NCBI will soon begin assigning GIs exceeding the signed 32-bit threshold of 2,147,483,647 for those remaining sequence types that still receive these identifiers.<\/p>\n

NCBI has updated products including\u00a0Entrez system<\/a>,\u00a0GenBank<\/a>\u00a0(Nucleotide<\/a>),\u00a0BLAST\u2122<\/a>\u00a0and the\u00a0C++ Toolkit<\/a> to prepare for that moment by upgrading GI-related code and APIs to accept 64-bit integers. This change over is projected for late 2021. Stay tuned for additional communications from NCBI and take note of the following information if you think you may be impacted.<\/p>\n

For a seamless transition, all organizations and developers using our products should review software for any remaining reliance on GIs and compatibility with these larger identifiers.\u00a0Note that this update requires no changes to submission procedures or assignment of accessions.<\/em>\u00a0<\/p>\n

Software developers and organizations with specialty software built to interface with NCBI data and consume a sequence database UID (i.e. GI), process the GI from an ASN1 or XML product, or process the GI from\u00a0any<\/em>\u00a0tabular product on\u00a0FTP<\/a>, should review all code to ensure that the new, longer GIs will be handled properly. Alternatively, software developers can make updates to use accession.version identifiers instead of GIs as described in a\u00a0previous post<\/a>. We also recommend checking any JSONs in libraries if you have large numeric IDs converted to strings.<\/p>\n

We encourage all our customers to update to the latest versions of a variety of NCBI-provided programmatic and command line tools and also check certain web tools as described below.<\/p>\n