Skip to content
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

Next Task - Nearby no longer working #2577

Open
mneko opened this issue Feb 21, 2025 · 4 comments
Open

Next Task - Nearby no longer working #2577

mneko opened this issue Feb 21, 2025 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@mneko
Copy link

mneko commented Feb 21, 2025

Please Read First

  • If you are having issues creating your own Challenges, please make sure you carefully read the MapRoulette documentation, specifically the section about Creating and Managing Challenges. If that doesn't help you, please post to the OSM community forum with the hashtag #maproulette.
  • If you would like to report a Challenge you think is causing bad edits to OSM, please raise the issue with the Challenge owner first using the Get In Touch feature on the Challenge home page. If they fail to respond, please post to the OSM community forum with the hashtag #maproulette.
  • There is a separate repository for the MapRoulette back end. If your report pertains to the API / back end, please submit it there.

Thanks for helping us make MapRoulette great for everyone!

Describe the bug
When completing a task, you select whether to get a random task, or the next closest task. Nearby no longer selects a close task at all.

Expected behavior
Nearby selects the next closest task.

To Reproduce
Steps to reproduce the behavior:

  1. A good example is this task: https://maproulette.org/challenge/43001
  2. Pick a task in let's say Wisconsin and complete it.
  3. Complete the task and request the next task to be Nearest. The map will show that there's definitely a close task to jump to.
  4. It jumps to a random task instead of a close task.

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Vivaldi 7.1.3570.50, which is a Chromium fork
@mvexel
Copy link
Member

mvexel commented Feb 21, 2025

I just tried:

  1. Select task https://maproulette.org/challenge/43001/task/274014757 and fix it (way https://www.openstreetmap.org/way/467553926#map=19/42.240380/-83.616128) - Ypsilanti MI
  2. Select Nearby for next task
  3. Next task presented to me is https://maproulette.org/challenge/43001/task/274010319 which is way https://www.openstreetmap.org/way/1351884708#map=18/38.921433/-76.998598 (Washington, DC)

Looks like there are however plenty of nearby tasks that could have been selected:

Image

So this needs to be looked into, thanks for reporting

@mvexel
Copy link
Member

mvexel commented Feb 21, 2025

More investigation:

If I manually select a task initially, I can reproduce the error.. to an extent.

  1. Select initial task manually from the challenge browse page
  2. Skip
  3. Next task will not be nearby

If I click start on the Challenge browse page to start with a random task, the next task will be in the same area.

@mneko are you seeing the same?

@CollinBeczak CollinBeczak self-assigned this Feb 21, 2025
@CollinBeczak CollinBeczak moved this from Backlog to Planned in MapRoulette Frontend Kanban Board Feb 21, 2025
@mneko
Copy link
Author

mneko commented Feb 21, 2025

@mvexel I'm not sure how my setup differs from yours, but hitting Start instead of preselecting seems to have the same issue.
Start sent me to Tempe, AZ, then Nearby picked Los Angeles when I'm certain there's plenty left in Arizona.

Interesting, but probably a separate bug: Start also immediately sent me to a Skipped task when as far as I can tell, the algorithm is supposed to prefer untouched tasks first.

@CollinBeczak
Copy link
Collaborator

CollinBeczak commented Feb 21, 2025

I'm guessing it has something to do with the prioritization of tasks (you have some low and high "priority" tasks)... Hard to say and I will need to investigate this more, but it's been an issue in the past so maybe it's still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

3 participants