# How to provide global coordinate system after crop volume segment?

**URL:** <https://discourse.slicer.org/t/how-to-provide-global-coordinate-system-after-crop-volume-segment/1199>\
**Category:** Support\
**Tags:** segmentation\
**Created:** [October 9, 2017, 10:47am UTC](https://discourse.slicer.org/t/how-to-provide-global-coordinate-system-after-crop-volume-segment/1199 "2017-10-09T10:47:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [October 9, 2017, 5:04pm UTC](https://discourse.slicer.org/t/how-to-provide-global-coordinate-system-after-crop-volume-segment/1199/5 "2017-10-09T17:04:17Z")

</div>

This looks like RAS/LPS mismatch. See solution in this post:

> [@DICOM and VTK file orientation Issue](https://discourse.slicer.org/t/dicom-and-vtk-file-orientation-issue/717/7):
>
> Most common issue is LPS/RAS coordinate system mismatch. So, may try to convert your data from LPS to RAS coordinate system by transforming it using Transforms module by a matrix that has [-1,-1,1,1] in the diagonal: [image]

---

_[View the full topic](https://discourse.slicer.org/t/how-to-provide-global-coordinate-system-after-crop-volume-segment/1199)._