Why not call it "Custom Feature Type"?

@mh0g Could you rebase, to avoid merge nodes in the PR?

Or "Generic128" ?

Can I ask why you chose to limit it to 128?

How would you do to get something fully dynamic?

I meant the question as in, why limit it to such a low number to begin with? I understand that there has to be a limit, but why 128?
Granted, 128 is probably more than enough for control points, but if someone would want to import en-masse matches, that would be impossible this way.

128 is for the memory size of each descriptor, not for the number of features/matches.

I see. I suppose I misunderstood then. Figured this would work the same way as the CCTAG and AprilTag marker describers, where each match is a 128 bytes block, and FF byte in the block identifies the marker ID, which limits it to 128 different markers.
Sorry for the confusion.