Trail Edit / Waypoints from photos: prevent creating different waypoints for near-by locations (#457)
* trail edit / waypoints from photos: prevent creating different waypoints for near-by locations * remove not necessary imports * remove changes from gitignore * patch gitignore * waypoint merge radius as category property * change datamodel for merge radius (use more generic settings field for future implementations) * fix npm run check issues * several improvements/fixes * fix * move geo cluster code to db * fix compile issue * fix docker issue * merge with existing waypoints --------- Co-authored-by: Christian Beutel <> Co-authored-by: Flomp <Flomp@users.noreply.github.com>
This commit is contained in:
@@ -2,6 +2,10 @@
|
||||
title: Changelog
|
||||
description: What changed in the last patch?
|
||||
---
|
||||
## Unreleased
|
||||
### Features
|
||||
- Geotagged waypoint photos are now grouped into one waypoint when they are within the category's waypoint merge radius. Existing categories are initialized with waypoint merging enabled and a 50m merge radius; set `settings.wp_merge_enabled` to `false` on a category to keep creating one waypoint per photo.
|
||||
|
||||
## v0.18.5
|
||||
### Security
|
||||
- Fixes CVE-2022-39299 via xmldom upgrade
|
||||
@@ -682,4 +686,4 @@ This version updates the index pattern of the meilisearch index. Please delete o
|
||||
- updated the docs to include BODY_SIZE_LIMIT
|
||||
|
||||
## v0.1.0
|
||||
- Initial release
|
||||
- Initial release
|
||||
|
||||
@@ -16,3 +16,24 @@ All existing categories will be listed here.
|
||||
To edit one simply click on the row, edit the data you want to change, and click "Save".
|
||||
To delete a category check the box at the beginning of the row and click "Delete selected".
|
||||
To create a new category click the "New record" button in the top right corner, give your new category a name and a background image, and click "Save".
|
||||
|
||||
## Category settings
|
||||
|
||||
Categories can optionally define additional settings in the `settings` JSON field.
|
||||
This field may be left empty.
|
||||
When no settings are configured, <span class="-tracking-[0.075em]">wanderer</span> uses the built-in defaults.
|
||||
|
||||
Currently, the following setting is supported:
|
||||
|
||||
```json
|
||||
{
|
||||
"wp_merge_enabled": true,
|
||||
"wp_merge_radius": 50
|
||||
}
|
||||
```
|
||||
|
||||
`wp_merge_enabled` controls whether geotagged photos are grouped into waypoint clusters.
|
||||
Set it to `false` to create one waypoint per photo.
|
||||
|
||||
`wp_merge_radius` controls how close geotagged photos have to be to each other, in meters, before they are grouped into the same waypoint when adding waypoint photos to a trail.
|
||||
Set it to `0` to only merge photos with the exact same coordinates, or increase the value to merge photos across a wider area.
|
||||
|
||||
Reference in New Issue
Block a user