-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Add option to restrict scan to certain folder (recursively) #270
Comments
Would something like work #228? |
It would be much better design to restrict the scanning itself and not needing to control it via an additional file. I can think of a bunch of constellations where folders containing images are created automatically without user interaction. Think of project directories with media assets or think of external storage where you have only read-access. |
Well let's stay consistent with other apps like photos. Let's also merge #271 to this discussion as it addresses the same issue or? |
what about |
We have a very related issue in the Photos app at: We should probably coordinate and make sure the Maps app can take the same location that is specified in the Photos app. (At least for photos, tracks etc are separate.) cc @skjnldsv @Mikescops for Photos |
I came here looking for this option. I think it would be useful to be able to have several folders scanned as I have photographs and images in several album folders. Some I would want to show on the map, but not others. I hope that's clear. I'll try and clarify further if not. I should add that this is a fantastic addition to Nextcloud, I love it!! Thanks for developing it. |
Maps scanned my external storage, where a large number of material photos of games are stored.🤣 |
The maps:scan-photos command actually runs through all the user files which is definitely not wanted when you have not only photos in your userspace. An option to restrict the scan to a certain folder ist needed. This is true for maps:scan-tracks also (because .gpx is not unique to .gpx Tracks, but also to GuitarPro files for example).
The text was updated successfully, but these errors were encountered: