Opened 4 years ago
Closed 4 years ago
#21295 closed defect (fixed)
Mapillary shows grey sequence links which cannot be followed
| Reported by: | Polarbear-j | Owned by: | taylor.smock |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Plugin mapillary | Version: | |
| Keywords: | Cc: |
Description
JOSM/1.5 (18193 en_GB) Mac OS X 10.14.6
+ Mapillary (2.0.0-alpha.34-dirty)
Occasionally, the sequence shown in the josm-tiles gets a grey line, or with no line at all, which makes the forward/backward buttons inoperable.
Checking the same image in the browser shows the sequence connected.
The screenshot example is https://www.mapillary.com/app/?pKey=1448726572130647&lat=51.797032376250996&lng=12.278917715211037&z=19.9
Closing just the mapillary layer and restarting it did not help.
Closing JOSM and reloading everything did work.
Attachments (3)
Change History (6)
by , 4 years ago
| Attachment: | Screenshot 2021-09-06 at 18.14.59.png added |
|---|
by , 4 years ago
| Attachment: | Screenshot 2021-09-06 at 18.15.21.png added |
|---|
by , 4 years ago
| Attachment: | Screenshot 2021-09-06 at 18.19.56.png added |
|---|
comment:2 by , 4 years ago
OK. I've been able to reproduce. It looks like it may be that the sequence isn't properly set somewhere. I'll add a check and fix. (When I reproduced, the sequence had no tags).
The gray line, in and of itself, does not prevent forward/backward. It will prevent forward/backward when there are not Mapillary nodes in front of or behind of the selected image. So it is possible that the selected node isn't actually "part of" the sequence way.
Closing just the mapillary layer and restarting it did not help.
At this time, there is only ever one Mapillary layer. I may be changing this in the future, but a workaround in the next release will be to toggle the computed geometry setting in preferences (this may be in the current release, I don't remember -- it will destroy the Mapillary layer instance).
comment:3 by , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I think I fixed this in 7432f2490fb07c1cc585f953e224ac48b5477c33. But it is kind of hard to reproduce.





