Removed fragments

Fragment removal, a part of algorithm transparency, is the last filter applied to traced skeleton after tail removal. Fragments are short isolated ridges (or valleys in case of valley skeleton). They are usually created by errors in prior stages of the algorithm.

KeywordSuffixZip
ridges-removed-fragments.json054-ridges-removed-fragments.json
ridges-removed-fragments.dat055-ridges-removed-fragments.dat
valleys-removed-fragments.json070-valleys-removed-fragments.json
valleys-removed-fragments.dat071-valleys-removed-fragments.dat

Visualization

Visualization of skeleton after fragment removal was constructed by comparing this stage's json and binary data to skeleton with tails removed. Visualization itself is not part of transparency data.

Fingerprint skeleton with fragments removed and changes marked red
Fingerprint skeleton after fragment removal. Removals, if any, are marked red.

Binary data

Binary data has the same structure as for traced skeleton.

Example: 055-ridges-removed-fragments.dat

Json

Structure of json data is the same as for traced skeleton.

Example: 054-ridges-removed-fragments.json

{
  "width": 388,
  "height": 374,
  "minutiae": [
    {
      "x": 76,
      "y": 268
    },
    {
      "x": 223,
      "y": 326
    },
    {
      "x": 80,
      "y": 156
    },
    {
      "x": 308,
      "y": 256
    },
    {
      "x": 241,
      "y": 286
    },
    {
      "x": 142,
      "y": 304
    },
    {
      "x": 78,

... skipped 735 lines ...

      "end": 83,
      "length": 4
    },
    {
      "start": 85,
      "end": 94,
      "length": 138
    },
    {
      "start": 87,
      "end": 96,
      "length": 318
    },
    {
      "start": 88,
      "end": 83,
      "length": 54
    },
    {
      "start": 93,
      "end": 89,
      "length": 186
    },
    {
      "start": 97,
      "end": 69,
      "length": 130
    }
  ]
}