# Can the automatically generated tie points be exported?

**URL:** <https://forums.unrealengine.com/t/can-the-automatically-generated-tie-points-be-exported/1719750>\
**Category:** Photogrammetry\
**Tags:** question, realityscan\
**Created:** [February 29, 2024, 4:59am UTC](https://forums.unrealengine.com/t/can-the-automatically-generated-tie-points-be-exported/1719750 "2024-02-29T04:59:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TKSharpless](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@TKSharpless](https://forums.unrealengine.com/u/TKSharpless)\
**Post date:** [February 29, 2024, 4:59am UTC](https://forums.unrealengine.com/t/can-the-automatically-generated-tie-points-be-exported/1719750/1 "2024-02-29T04:59:38Z")

</div>

I want to use sparse alignments made by RC for research on alternative modeling methods. I see that it is possible to export files containing the camera intrinsics and poses, and the 3D world coordinates of the automatically found tie points. But I can’t find a way to export the image coordinates of those points. Is this an intentional restriction?  
I can use the reprojected world points, but it would be helpful to have the actual image points found by the tie point generator.

---

<div class="post-metadata">

**Author:** ![OndrejTrhan](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ondrejtrhan/32/906565_2.png) [@OndrejTrhan](https://forums.unrealengine.com/u/OndrejTrhan)\
**Post date:** [February 29, 2024, 8:34am UTC](https://forums.unrealengine.com/t/can-the-automatically-generated-tie-points-be-exported/1719750/2 "2024-02-29T08:34:27Z")

</div>

Hi [TKSharpless](https://dev.epicgames.com/community/api/user_profiles/tab-redirect/about?discourse_username=TKSharpless)  
Indeed, that is not possible. But there is an option to compute those coordinates by yourself: [RealityCapture XMP Camera Math](https://forums.unrealengine.com/t/realitycapture-xmp-camera-math/682564)

I will create a feature request for this.

---

<div class="post-metadata">

**Author:** ![TKSharpless](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@TKSharpless](https://forums.unrealengine.com/u/TKSharpless)\
**Post date:** [February 29, 2024, 3:58pm UTC](https://forums.unrealengine.com/t/can-the-automatically-generated-tie-points-be-exported/1719750/3 "2024-02-29T15:58:13Z")

</div>

Thank you, Ondrej. That post on camera calibration is very helpful, too.

---

<div class="post-metadata">

**Author:** ![TKSharpless](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@TKSharpless](https://forums.unrealengine.com/u/TKSharpless)\
**Post date:** [July 4, 2024, 10:54pm UTC](https://forums.unrealengine.com/t/can-the-automatically-generated-tie-points-be-exported/1719750/4 "2024-07-04T22:54:11Z")

</div>

The camera report in bundler .out format does contain tie point coordinates, both 3D and 2D. However on a different coordinate system from what is used in the native reports. I have made some experiments to convert them, using the camera positions as corresponding points, but it does not appear that this correspondence is exact. Can you give any guidance on how to convert the bundler coordinates correctly?

---

<div class="post-metadata">

**Author:** ![OndrejTrhan](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ondrejtrhan/32/906565_2.png) [@OndrejTrhan](https://forums.unrealengine.com/u/OndrejTrhan)\
**Post date:** [July 15, 2024, 9:03am UTC](https://forums.unrealengine.com/t/can-the-automatically-generated-tie-points-be-exported/1719750/5 "2024-07-15T09:03:17Z")

</div>

Hi @TKSharpless  
According to the calibration.xml file

```auto
Bundle file v0.3
$(cameraCount) $(pointsCount)$ExportCameras(
$(f*scale) $(k1) $(k2)
$(R00:g) $(R01:g) $(R02:g)
$(-R10:g) $(-R11:g) $(-R12:g)
$(-R20:g) $(-R21:g) $(-R22:g)
$(tx:g) $(-ty:g) $(-tz:g))$ExportPoints(
$(x:.8) $(y:.8) $(z:.8)
$(r) $(g) $(b)
$(trackLength)$ExportTrack( $(imageIndex) $(featureIndex) $(x*scale:.3) $(-y*scale:.3)))

```

it seems like the coordinates are in local coordinate system (3D) and in pixels for 2D.

I suppose the XMP camera math is also used there in the same way.
