NIST Biometric Image Software
Current Release:
NBIS Non-Export Control : Rel 2.0.0
NBIS Export Control : Rel 2.0.0
About
The NIST Biometric Image Software (NBIS) distribution is developed by the National Institute of Standards and
Technology (NIST) for the Federal Bureau of Investigation (FBI) and Department of Homeland Security (DHS). The
NBIS software is organized in two categories: Non-Export Control and Export Control. The Non-Export Control
NBIS software is organized into five major packages: 1. PCASYS is a neural network based fingerprint pattern
classification system; 2. MINDTCT is a fingerprint minutiae detector; 3. NFIQ is a neural network based
fingerprint image quality algorithm, 4. AN2K7 is a reference implementation of the ANSI/NIST-ITL 1-2007
"Data Format for the Interchange of Fingerprint, Facial, Scar Mark & Tattoo (SMT) Information" standard; and
5. IMGTOOLS is a collection of image utilities, including encoders and decoders for Baseline and Lossless JPEG
and the FBI's WSQ specification. The Export Control NBIS software is organized into two major packages:
1. NFSEG is a fingerprint segmentation system useful for segmenting four-finger plain impressions, 2. BOZORTH3
is a minutiae based fingerprint matching system. The Non-Export Control NBIS software is managed using Perforce*
source code management system on the NIST image Group Open Source Sever (NIGOS). The Export Control NBIS source
code is only available on CD-ROM upon request. For detail information on how to obtain the latest version of
NBIS Non-Export Control source code or how to request the NBIS Export Control source code, please visit
http://fingerprint.nist.gov/NBIS/index.html.
How to Contribute to the NBIS Project
The NIST Image Group appreciates all technical contributions to the NBIS project. If you are interested on contributing to the NBIS project, you are welcome to become a developer. As a developer, you will have your own NBIS development branch within Perforce, which allows you to manage your own NBIS development source code. To become a NBIS project developer, please send an email to nbis@nist.gov with the following information: Name, Organization, Contact Information and a brief description of your goals as an NBIS project developer. After we have received your request, we will contact you for further information.
Terms and conditions:
There is no guarantee that your contributions will be included in the NBIS Main development branch; the integration of outside changes is at the sole discretion of the NIST Image Group. However, any changes that are integrated will fall under the same licensing terms as the original software.
Perforce licenses are a limited resource; if you do not make changes to your development branch within any 180-day period, we may ask you to return the license to us, and your account will be deleted. However, we will make all reasonable attempts at contacting you before deleting your account.
Support
Thank you for your interest in using the NBIS software. Unfortunately, we do not have the resources to provide individual support for this software, but do welcome comments for improvement. At the present time we only provide the source code for download.
License
This software was developed at the National Institute of Standards
and Technology (NIST) by employees of the Federal Government in the
course of their official duties. Pursuant to Title 17 Section 105 of the United States Code,
this software is not subject to copyright protection and is in the
public domain. NIST assumes no responsibility whatsoever for use by
other parties of its source code or open source server, and makes no
guarantees, expressed or implied, about its quality, reliability, or
any other characteristic.
Disclaimer
* Specific software products identified here are used in order to perform the code management tasks at hand.
However, in no case does identification of any commercial product, trade name, or vendor, imply recommendation
or endorsement by the National Institute of Standards and Technology, nor does it imply that the products and equipment
identified are necessarily the best available for the purpose.