New feature: Partial sequence deletion in Mapillary web frontend
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or implementation entry point, and this repository is described as command-line tools. First locate the Mapillary web frontend and its sequence-deletion flow, then confirm whether this repository contains the relevant code. Done means supporting deletion from the current image to either sequence boundary without deleting the retained portion.
Written by the indexing model from the issue text.
Description
Background
- As an contributor, I typically try to upload GoPro timelapse videos.
- After data ingestion, I typically inspect the imagery in the Mapillary web frontend.
- When a complete video is uploaded it can happen that unnecessray images are logged, e.g. maneuvering on a parking lot or video logging while taking a break.
- In such cases the web frontend offers to delete individual images which can be a tedious procedure. Deleteing the whoel sequence is available today but would also drop the portions of the sequence that should be retained.
It would be helpful to have more granular options to delete portions of the sequence.
New feature proporsal
- The Mapillary webfront end should provide an option to delete all the images of a sequence from the current image until the end of the sequence.
- The Mapillary webfront end should provide an option to delete all the images of a sequence from the beginning of the sequence to the current image.
- Dominant language
- Python
- Stars
- 316
- Forks
- 145
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapillary/mapillary_tools
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
mapillary/mapillary_tools#844 ·
Maintainers usually reply within 4 days
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
mapillary/mapillary_tools#827 ·
Maintainers usually reply within 4 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
mapillary/mapillary_tools#819 · 2 comments ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mapillary/mapillary_tools#783 · 3 comments ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
mapillary/mapillary_tools#748 · 2 comments ·
Maintainers usually reply within 4 days
All issues in mapillary/mapillary_tools
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
debpalash/VoiceStudio#2624 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Make Catch2 optional when `RDK_BUILD_CPP_TESTS=OFF`Possibly taken @pechersky claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
There are a few redundant calls to `fdesc._setCloseOnExec()`Possibly taken @gudnimg claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day