Sequences out of order

the sequences which contain these images:
https://www.mapillary.com/map/im/KsGMNWEVx66q75YtzWr5BA
https://www.mapillary.com/map/im/8O4l2WwNdwhxnJx69gt5VQ
(i can only put 2 links, there are more in the area)

are out of order.
can i report the sequence itself? i dont really see a problem with all of the images

1 Like

well, they’re old, from 2002, i’m going to just set them to be deleted

Yeah, looks really terrible. :face_vomiting: Something must have gone wrong with the Exif header/timestamps.

well, they’re old, from 2002, i’m going to just set them to be deleted

True, I guess is indeed best to delete and upload them again. See if you can analyze the Exif meta data and perhaps fix the timestamps with a script. Or, perhaps you can create a correct GPX track and align them with mapillary_tools or JOSM? After all, despite or perhaps because of their age I think that they have some intrinsic value and possibly even some true value to someone in the future. So, please do not write them off so easily (just because they are old), give them a chance to live on. :wink:

they are not mine, so i can not upload them again.
I just saw the spiderwebbing effect on the map, which obscures the underlying map and any other sequences that may or may not be there

Oh, I see. That was not clear from the initial post. Well then, I guess it should be best to report these sequences before requesting deletion because as the web interface is right now, you cannot comment on the reason for deletion. Reporting is the best way to proceed so that the backend developers get a chance to look at the sequence’s meta data and potentially perhaps fix a problem. So, thank you for pointing these out!

I’ve made a similar sequence by making a mistake in a file operation.

The desktop uploader I’m using seems to sequence the photos uploaded from the same folder using the time stamp of the shooting date and time of each photo.
It is not the order of file names.

Well, I shot a sequence containing hundreds of shots.
I shot multiple such sequences.

Then, in the post-shooting process, EXIF ​​was written to give location information to each photo.
At that time, I rewrote the shooting start times of the above multiple sequences to the same time.

I put them under the same folder and uploaded them all in one process with the desktop uploader.

Then, the resulting Street-level Imagery rearranged all the photos in those photo groups in EXIF ​​chronological order, so a mesh that goes back and forth between multiple photos that were originally in different sequences.

The example given by the questioner also seems to me to make regular round trips between several series of chunks.
I think it’s a sequence created by a failed operation similar to mine.

I also get the same symptom when I give EXIF ​​at the correct time for each frame extracted from the video.
Even if I only use 5 frames per second, the 5 images with the same time may be arranged in a random order. It does not sort by file name.

Looks like @potaro67v is right. The web pattern occurs when images in a sequence have an identical timestamp. Look at sequence MMELGQyTaUbj3IMDMKJ_Hw for example:

{
  "type": "Feature",
  "properties": {
    "ca": 181.06398512714964,
    "camera_make": "Motorola",
    "camera_model": "XT1032",
    "captured_at": "2002-12-08T12:00:00.000Z",
    "key": "TwFJx5fo1bA8Zr0HTa7rhg",
    "pano": false,
    "sequence_key": "MMELGQyTaUbj3IMDMKJ_Hw",
    "user_key": "JPgWcFefquxNHtScGW-fdg",
    "username": "didihn",
    "quality_score": 5
  },
  "geometry": {
    "type": "Point",
    "coordinates": [
      13.2815717,
      52.6568217
    ]
  }
}
{
  "type": "Feature",
  "properties": {
    "ca": 237.96131545377943,
    "camera_make": "Motorola",
    "camera_model": "XT1032",
    "captured_at": "2002-12-08T12:00:00.000Z",
    "key": "hiNMc9M72Cmjvdzl8AaVog",
    "pano": false,
    "sequence_key": "MMELGQyTaUbj3IMDMKJ_Hw",
    "user_key": "JPgWcFefquxNHtScGW-fdg",
    "username": "didihn",
    "quality_score": 5
  },
  "geometry": {
    "type": "Point",
    "coordinates": [
      13.281135,
      52.642555
    ]
  }
}

However, this basically only concerns the web viewer (or mapillary-js) because reconstruction produces proper navigation in space. Only sequence traversal is broken or turns out ugly on the map. These sequences do not break other sequences or other Mapillary data. They only look ugly on the map. I am not sure there is any easy remedy for this for the web viewer because even if for example the original image files were ordered alphabetically as to the true sequence of events (shots) the web viewer has no access (and should not have) to the original file names to make out any proper order. I don’t know, perhaps ordering by image key might help to make the web pattern more bearable in that case?

1 Like