# Deleting broken segment/fixing processed desktop CLI utility images from 360° video

**URL:** <https://forum.mapillary.com/t/deleting-broken-segment-fixing-processed-desktop-cli-utility-images-from-360-video/2707>\
**Category:** Mapillary integrations\
**Created:** [March 20, 2019, 10:39pm UTC](https://forum.mapillary.com/t/deleting-broken-segment-fixing-processed-desktop-cli-utility-images-from-360-video/2707 "2019-03-20T22:39:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![milkcrateridesabike](https://avatars.discourse-cdn.com/v4/letter/m/f475e1/32.png) [@milkcrateridesabike](https://forum.mapillary.com/u/milkcrateridesabike)\
**Post date:** [March 20, 2019, 10:39pm UTC](https://forum.mapillary.com/t/deleting-broken-segment-fixing-processed-desktop-cli-utility-images-from-360-video/2707/1 "2019-03-20T22:39:50Z")

</div>

Pulled and uploaded images from a 360° video and fixed the EXIF data using `process_csv` argument in `mapillary_tools`. Unfortunately, the CLI utility doesn’t check if the source media has 360° metadata and automatically add it to the output files if it does… Google has a Python library called spatialmedia on GitHub that I should be able to use to write some helper methods to fix the processed images before uploading them, but my more immediate concern is deleting the segment of bad 360° images. It looks like some of the images are still processing, but part of the segment is public, but the editor modal that lets me delete the segment isn’t loading right now.

Anyone have any recommended next steps or advice on the best way of handling this situation?