mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
API: GET /api/v1/photos should also return face information #2211
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#2211
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 @DrDonoso on GitHub (Nov 6, 2024).
Describe what problem this solves and why this would be valuable to many users
I'm using the api to return a random photo at api/v1/photos. I would like to see the faces appearing in the photo.
When seeing the API, the faces are not returned in the response.
I can see the call at api/v1/photos/{uid} return faces, but it returns a number instead of the faces object.
It would be nice to return an array with the faces detected.
Thanks for your great effort! 😊
Describe the solution you'd like
Improve /api/v1/photos and /api/v1/photos/{uid} to return the faces object.
Describe alternatives you've considered
Additional context
@lastzero commented on GitHub (Nov 6, 2024):
We probably won't be able to do this for performance reasons, as it would most likely require at least one additional query for each result - unless you just want the comma-separated names?
@DrDonoso commented on GitHub (Nov 6, 2024):
I understand; comma-separated names would be nice if it's possible and don't have any impact in performance.