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

Adding a detected feature can cause nearby features to vanish #1288

Closed
bos opened this issue Jan 5, 2024 · 1 comment
Closed

Adding a detected feature can cause nearby features to vanish #1288

bos opened this issue Jan 5, 2024 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@bos
Copy link

bos commented Jan 5, 2024

Description

In some unclear circumstances, selecting an AI-detected track will cause nearby ones to vanish. It is not clear why this occurs, as it only happens in some locations.

Screenshots

Here's an MP4 video of trying to select add a few tracks.

Repro.mp4

Version

2.2.2

What browser are you seeing the problem on? What version are you running?

Safari v17.2

The OS you're using

mac

Steps to reproduce

The location in the video is as follows, which I'm leaving untouched:

https://rapideditor.org/edit#background=EsriWorldImageryClarity&datasets=fbRoads,msBuildings&disable_features=boundaries,water,power&map=18.00/35.09060/-114.46091

Just select one of the features at this location, and see one of its neighbors vanish. Notice that this happens for some, but not all, features.

The browser URL at the time you encountered the bug

https://rapideditor.org/edit#background=EsriWorldImageryClarity&datasets=fbRoads,msBuildings&disable_features=boundaries,water,power&map=18.00/35.09060/-114.46091

The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.2 Safari/605.1.15

@bhousel
Copy link
Contributor

bhousel commented Jan 8, 2024

Thanks for reporting @bos , this has been a tricky issue to track down, but the location around here is a good place to test because the ways are split into a lot of pieces.

@bhousel bhousel closed this as completed in 57db299 Jan 9, 2024
bhousel added a commit that referenced this issue Jan 10, 2024
(re: #1288)

We handled the case before where they were at the beginning only,
but I thought about it more, and this is another thing that can happen.
@bhousel bhousel added this to the v2.2.4 milestone Jan 10, 2024
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
None yet
Development

No branches or pull requests

2 participants