-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Places: Support sub-km distances when searching for locations #3558
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
Comments
It's an approximation due to how the query works (for maximum compatibility with all databases). Accepting a floating point number instead of an integer should still be possible to implement with reasonable effort. |
Signed-off-by: Michael Mayer <michael@photoprism.app>
Signed-off-by: Michael Mayer <michael@photoprism.app>
Signed-off-by: Michael Mayer <michael@photoprism.app>
Signed-off-by: Michael Mayer <michael@photoprism.app>
Signed-off-by: Michael Mayer <michael@photoprism.app>
@loulou91 I've started a new preview build so you can test these changes, it should be available within the next hour:
Note that our public demo at https://demo.photoprism.app/ will be updated as well if you don't want to use our preview build to test with your own pictures. |
Thanks a lot for the implementation ! |
Thank you very much for testing :)
The city search filter cannot be used in combination with dist because we do not have the city boundary coordinates. |
Present geographical search is a nice feature and works well but precision is today 1 km which may be sometimes too rough.
I tried to enter dist:0.1 but I got an error ("unable to do that").
I think dist unit is integer...
Could it be possible to increase precision using float in place of integer or to change unit km to meter?
Thanks in advance.
The text was updated successfully, but these errors were encountered: