Tao Peng
Tao Peng
This can be done by geotag with a external GPX. The final clip is the overlap between the GPX and the video, so cut your GPX should solve the issue:...
This is v0.10.1. Is it still an issue in the latest version?
LGTM. The only concern is the ground speed added in `mapillary_tools/geotag/camm_parser.py`. It is used to determine if a GPS point is noisy or not (and noisy points and corresponding frames...
Hey @mvexel would you mind providing some sample videos?
Hey @govvin the link to the sample video is expired. Could you try again? The exiftool approach looks good to me.
This is likely an issue fixed in https://github.com/mapillary/mapillary_tools/releases/tag/v0.14.0a1
> Suggested solution 1: make mapillary_tools export both front/back images from *.360 file with suffix _front.jpg / _back.jpg so people can batch stitch them together themselves using PTGui for example...
It prefers `GPS Date/Time` if it's available. In your case, the GPS timestamp has no subseconds. We can use `Date/Time Original` as the secondary key for sorting, i.e. sort images...
Is the PR still needed if decimal values are serialized in JSON, instead of converting to EXIF rational values? See my comment in https://github.com/mapillary/mapillary_tools/pull/782.
@JakeSmarter Do we really need to care about the **whole number part**? Can we just increase the precision to 8 for all?