Reconstruction Region Set but not applied

Dani_rm · November 15, 2024, 11:20am

Hello,
we are using the -setReconstructionRegion command to set the bounding box.
Unfortunately for some cases the processed model results in a model that is too big and has blurry outlines.
When I checked the .rcbox file it has the correct width/height etc. Also sometimes if we retrigger the exact same pipeline the reconstruction region was set correctly and has the correct size.
As you can see in the images the models are blurry on the outside and the surface is at least twice or three times the size we specified in the rcbox file.

Do you know what would cause such a situation, or what we could do to prevent it?

Thanks in Advance!

OndrejTrhan · November 15, 2024, 11:53am

Hi Daniele
what is the script you are using? This looks like region is not loaded at all.

Dani_rm · November 22, 2024, 4:45pm

Thanks for your response. We run a custom custom script that provides a .rcbox file to the -setReconstructionRegion command.
But the same command with the same file sometimes doesn’t actually set the reconstruction region. When I checked the Reality Capture UI while the automated script was running, I noticed that the reconstruction region was never set. Even if we saw that the -setReconstructionRegion ran and no error was thrown.

Is it possible to check whether the reconstruction region was successfully set via a cli command?

OndrejTrhan · November 25, 2024, 8:09am

Hi Daniele,
how was the reconstruction region created?
Is it possible to import that region manually?

It is not possible to check that using the CLI command.

MatejAirteam · January 14, 2025, 3:56pm

Hi Ondrej, I work at the same company that Daniele worked at, and would like to continue since we’re still facing the issue.

Our flow when applying the rcbox file is the following:

Align the images, generate and export the reconstruction region
Get the elevation and use GPS coordinates to create a new rcbox file
Use the newly created rcbox to set the region

Here is the content of the file:

'<ReconstructionRegion globalCoordinateSystem="+proj=longlat +datum=WGS84 +no_defs" '
        'globalCoordinateSystemName="epsg:4326 - GPS (WGS 84)"\n'
        '   isGeoreferenced="1" isLatLon="1" '
        'widthHeightDepth="48.0641059874739 53.278949737143 10.1386680599677">\n'
        '  <globalCoordinateSystemWkt>GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",'
        '6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]'
        "</globalCoordinateSystemWkt>\n"
        f"  <yawPitchRoll>0.0 0.0 -{yaw}</yawPitchRoll>\n"
        f"  <widthHeightDepth>{depth_west} {width_north} {height}</widthHeightDepth>\n"
        '  <Header magic="5395016" version="2"/>\n'
        "  <CentreEuclid>\n"
        f"    <centre>{long} {lat} {z}</centre>\n"
        "  </CentreEuclid>\n"
        '  <Residual R="1 0 0 0 1 0 0 0 1" t="0 0 0" s="1" '
        'ownerId="{8D3C7DA5-CD49-417A-8EC0-34C096F0B330}"/>\n'
        "</ReconstructionRegion>\n"

As Daniele said, the weird thing is that if we rerun the same project for a 2nd or 3rd time, the BB will be there and it’ll work. This happens for a wide variety of projects and I couldn’t find any correlation between them. We also can’t do this manually.

I do have additional questions:

Is it possible for the bounding box to fail when it’s being applied but for no error to be raised by the command?

OndrejTrhan · January 15, 2025, 9:59am

Hi Matej,
this is quite unusual workflow.
Are you using that region in the same project? Do you have set the project and output coordinate system properly? How are you getting the elevation? Are you changing that value in the rcbox file?

Also, I exported the rcbox file and checked it and it is different to yours. Are you adding some lines into that file? As you have widthHeightDepth line twice…
Also, for the centre, are you using the degree coordinates or radians?

As you are running it more times, is that a fresh start of the project?

Regarding the manual testing, I was curious, if it is possible to import the rcbox into your project using the Import Reconstruction Region tool.

I suppose there is no error for the importing of the region in the system.

MatejAirteam · January 16, 2025, 10:14am

Hi Ondrej,

It seems I gave you some wrong information at the start. I’m not familiar much with RC and was just starting to debug this so sorry for that.
It seems this bug is always constant so it won’t fix by itself after the 1st or 2nd try. I’m guessing that the problem here is with the RC box file.

Regarding the elevation, we parse the rcbox file and read the last value of the CentreEuclid tag. We the increase it by 10 (constant) and set it in the new rcbox file along with the other values such as yaw, width, height, depth, long and lat.
Would RC throw an error if the rcbox file is not formatted correctly or has some incorrect values?

OndrejTrhan · January 16, 2025, 11:25am

Hi Matej,
can you share the original and modified rcbox file? Also some images from that area?

Yes, if the values are incorrect, it will throw an error.

MatejAirteam · January 16, 2025, 4:28pm

Here’s an example of the rcbox file

<ReconstructionRegion globalCoordinateSystem="+proj=longlat +datum=WGS84 +no_defs" globalCoordinateSystemName="epsg:4326 - GPS (WGS 84)"
   isGeoreferenced="1" isLatLon="1">
  <globalCoordinateSystemWkt>GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]</globalCoordinateSystemWkt>
  <yawPitchRoll>0.0 0.0 -57.994596645808386</yawPitchRoll>
  <widthHeightDepth>23.19294638093561 31.892667421139777 60</widthHeightDepth>
  <Header magic="5395016" version="2"/>
  <CentreEuclid>
    <centre>0.2872301359801154 0.8349964618725966 123.650970031507</centre>
  </CentreEuclid>
  <Residual R="1 0 0 0 1 0 0 0 1" t="0 0 0" s="1" ownerId="{8D3C7DA5-CD49-417A-8EC0-34C096F0B330}"/>
</ReconstructionRegion>

I tried importing it manually by going to Mesh Model → Reconstruction Region in the Import section and then selecting this rcbox file but nothing happens.

Here’s an image:

OndrejTrhan · January 17, 2025, 8:08am

Hi Matej, thank you for your file.
I tested it and it looks I am able to import your region (I used original one and also changed the values for my project).
Can you check your Project and Output coordinate system settings?
Also, are the images from the attached picture georeferenced (because I don’t see any orange lines for the images)?
Can you try the application reset (Reset RealityCapture) and then try the import again?

MatejAirteam · January 17, 2025, 11:40am

The coordinate system on the Project and the Output is epsg:4326 - GPS (WGS 84).
The component is not Geo-references but I am not sure how or whether there exists a setting for each image.

I’m not sure if resetting RC will do anything since other projects have been processed with a BB.

OndrejTrhan · January 17, 2025, 12:03pm

OK, the usage of different coordinate systems could be a problem there.
Can you show me also the 1Ds view with one selected input image in the component?
As the reconstruction region is georeferenced, also the component must be georeferenced. As it is not for you, it is placed in different position, which is far away from the component and therefore it is not imported.

I tested this on my dataset, turned off the camera priors and nothing happened. To use the reconstruction region I had to turn on the priors and create georeferenced component.

The setting for separated images is in 1Ds view after image selection:

For all images it is possible to disable the Camera priors settings under the Alignment settings:

The reset can help turn the app back to its original state when some wrong settings were used, but it is hard to find them.

MatejAirteam · January 17, 2025, 4:33pm

It seems the no Georeference components was my mistake since my local testing env wasn’t the same as production. I’ve changed it and it now applies the BB locally which is even stranger since it’s still not working in production for some buildings.
I’m not quite sure how to continue, do you have an idea of what might go wrong in those cases?

Can you let me know why are the coordinate systems wrong since they both match and are the same as the one in the rcbox file?