nextcloud / nextcloud/maps

Don't automatically "zoom & split" photo groups in maps

Open
#1,461 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: 🖼 photos
Dominant language
JavaScript
Stars
598
Forks
113
PR merge metrics
No merged PRs in 30d

Description

Let's say you have 60 photos on New York. At high-level scales, they appear as a single folder. Then you click them, and you get automatically zoomed in and see 40 photos on Manhattan and 20 on Brooklyn. You click those in Manhattan, and see 30 of them on the 5th Avenue and 10 on Central Park.. and so on, until you get your photos of your New York holidays spread on too many different locations, sometimes inconsistent, due to GPS inaccuracy,

My proposal is that when you are on a high level zoom and click on some photos "folder", you get a gallery of all of them, and it is the user, if he/she wish to get more "accurate" spatial grouping of the photos, that first he/she zoom and then select the more precise location.

By the way, I find the possibility to search photos for spatial location on a map awesome. It would be even nicer to be able to combine all the 3 elements of searching/look up (who/what, e.g. faces , time ranges and space/maps) in a single interface...

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

No files or tests are named. Start by reproducing the map photo-group click behavior at high zoom levels and trace the entry point that performs automatic zooming and spatial splitting. Done should mean selecting a high-level group opens all its photos in a gallery, while finer spatial grouping happens only after the user zooms and selects a more precise location.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.