mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
Allow lon keyword as an alternative for longitude #1994
Labels
No labels
ai
android
api
auth
awesome
bug
bug
ci
cli
config
database
declined
deprecated
docker
docs 📚
documents
duplicate
easy
enhancement
enhancement
enhancement
epic
faces
feedback wanted
frontend
hacktoberfest
help wanted
idea
in-progress
incomplete
index
invalid
ios
labels
live
live
low-priority
macos
member-feature
metadata
mobile
nas
needs-analysis
no-coding-required
no-coding-required
observability
performance
places
please-test
plus-feature
priority
pro-feature
question
raspberry-pi
raw
released
released
released
research
resolved
security
sharing
tested
tests
third-party-issue
thumbnails
upgrade
upstream-issue
ux
vector
video
waiting
won't fix
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism#1994
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @khaytsus on GitHub (Dec 31, 2023).
Describe what problem this solves and why this would be valuable to many users
In almost every context I've ever seen, the short way to say latitude longitude is lat lon. So every time I search in PhotoPrism I always wind up trying lat:NN lon:NN and it doesn't work. Could lon be added as a secondary search token? Not suggesting changing lng, just adding a secondary way to do it.
Describe the solution you'd like
Just allow lon:NNN as a way to search by longitude.
@lastzero commented on GitHub (Dec 31, 2023):
The search filter to use for longitude is
lng, see the following overview:@khaytsus commented on GitHub (Dec 31, 2023):
Well, yes, I'm aware :) Which is why I mentioned "lng" several times.
@lastzero commented on GitHub (Dec 31, 2023):
Oh, I just read "an alternative for longitude" and then thought you also tried "lng". I think if we have both, that could be confusing too, at least if it's officially documented...
@lastzero commented on GitHub (Dec 31, 2023):
Note that we want to have some kind of autocomplete for the search filters at some point, but we haven't had time to implement that ourselves yet, and no one else has contributed it either. Supporting all possible variants of filter names is a workaround we'd like to avoid.