jrock's profile - activity

Is there any reason why the API for chamfer matching is limited to the single function chamerMatching(img,img,...) which [sortof] returns the n-best matches. It seems like a good idea to make the actual ChamferMatching object available to someone so inclined. It's an easy enough change to add a header file to the contrib/include.

Just a heads up, I'm not asking someone to do this for me, I've already done it on a local fork, I'm just curious if this is something that I would be accepted if I put in a pull request.