Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle failed matching if at least one image has no GPS data #217

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bdholt1
Copy link
Contributor

@bdholt1 bdholt1 commented Sep 13, 2017

Fix for #198

The fix worked for me, don't see why everyone else using this library should need to apply the patch too.

@paulinus
Copy link
Member

What should we do if one image does not has GPS and match selection using GPS distance is enabled?

The current behavior is to deactivate the GPS based match selection altogether.

If I understand correctly, with this patch we would keep it on with max_distance=150. The problem is that the distances between images with GPS and images without GPS will be arbitrarily long. So we will never select matching pairs between the two groups.

Does this make sense? What behavior would you want, @bdholt1 ?

@markuswagner1
Copy link

To weigh in on this discussion as I have also had the same problem:

I consider the correct algorithmic behavior would be to include images that have invalid or missing GPS information in all matching pairs, hence, to match such an image with ALL the other images. If you have, as I do, usually a large amount of images with valid GPS information and just a few where this is missing, it would be a huge speedup compared to having all pairs evaluated.

Just had a quick glance into the code: I think it would be a rather minor patch to implement, I hope I'll have time next week to try it.

@facebook-github-bot
Copy link
Contributor

Hi @bdholt1!

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.

In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants