You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The white traces indicating Mapillary coverage is not visible even though there is a Mapillary detection in the same locality. Once clicked on the detection, a trial indicating mapillary photos appears. This is not the case across the map but exists at few locations.
The white mapillary trace would help the team to quickly identify the regions with new mapillary trace when filtered for 'n' days. It also helps in determining the direction of travel during the mapillary drive which eases while analysing a turn restriction detection.
Looks like there's a mismatch between the captured_at timestamp in the mapillary trail and the updated_at timestamp for a detected restriction. One possible reason could be that the detection algorithms are run at a latter time after a trail is first uploaded.
We should change the filtering logic to:
Get all detected objects updated with the past n days
Get the corresponding image keys from the detected objects
From the image keys, get the sequence keys for the trail
The white traces indicating Mapillary coverage is not visible even though there is a Mapillary detection in the same locality. Once clicked on the detection, a trial indicating mapillary photos appears. This is not the case across the map but exists at few locations.
The white mapillary trace would help the team to quickly identify the regions with new mapillary trace when filtered for 'n' days. It also helps in determining the direction of travel during the mapillary drive which eases while analysing a turn restriction detection.
Few images below to depict the case.
cc: @ajithranka
The text was updated successfully, but these errors were encountered: