opencv / opencv/opencv

Exposing more Keypoint and Feature2d C++ functions to Java API.

Open
#4,352 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-transferred category: java bindings feature priority: normal
Dominant language
C++
Stars
90.9k
Forks
57k
Avg merge
2d 15h
Merged PRs (30d)
112

Description

Transferred from http://code.opencv.org/issues/1866

|| Rui Marques on 2012-04-30 11:16
|| Priority: Normal
|| Affected: None
|| Category: java bindings
|| Tracker: Feature
|| Difficulty: None
|| PR: None
|| Platform: None / None

Exposing more Keypoint and Feature2d C++ functions to Java API.

I think it would be helpful to expose more functions, for example:

KeyPointsFilter::retainBest (ok this one can probably be already used indirectly by using ORB's nFeatures parameter)

KeyPoint::overlap (this might help as ORB, for example, returns a lot of keypoints that are close to each other and i think all those extra kpts won't help much to find an homography)

History

Alexander Shishkov on 2012-05-02 19:01
-   Target version set to 2.4.1
-   Assignee set to Andrey Pavlenko
-   Category set to java bindings
Alexander Shishkov on 2012-05-02 19:06
-   Target version changed from 2.4.1 to 3.0
Arjan Somers on 2012-05-10 08:48
I don´t know if the author also means setting the paramaters to the different keypoint detectors/extractors?

Currently the only way to set parameters (such as number of octaves etc) is only possible by writing a yaml file wich describes these settings and then load them from file. (Examples of this can be seen in the unit tests).

It would be nice to be able to set these parameters in a less hack-isch way.

Is this part of this feature feature request or should i make a new request?
Rui Marques on 2012-05-10 09:51
I was aware of the yaml method to set the parameters.
This particular feature request was about exposing more methods to Java but a better way to set the parameters would also be nice.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing Java bindings for the feature2d and keypoint APIs, then compare their available functions with KeyPointsFilter::retainBest and KeyPoint::overlap. Clarify which additional functions and detector or extractor parameters are in scope; done means the agreed C++ functionality is exposed through the Java API.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, java
Domain
api, computer-vision
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.