Region of interest, import/export with min + max altitude

[maal]

Does this sound familiar?

In projects involving repeated drone flights, we often need a consistent Region of Interest (ROI). Usually, the XY coordinates remain the same, and the elevation (Z) within the area doesn’t change either. That’s why it would be incredibly helpful to import and export the ROI not just in XY, but with the full 3D information – including Z values.

At the moment, I still have to manually adjust the Z heights after alignment in each new project. I keep wondering why the ROI can’t be transferred completely – both in position and elevation.

To be honest, it feels like this part hasn’t been fully thought through yet. Solving this doesn’t seem overly complex – or am I missing something and should prepare for another long wait for implementation?

[Rhea_Garratt]

@maal we have found that most users only need to adjust the region of interest horizontally, but rarely need to adjust it vertically. Do you need the region of interest to have a minimum and maximum altitude, and why? Would it be enough to just leave it as “inifinite” on the vertical axis=

[drones6]

No that won’t help.

Need top of ROI accessible to filter out cranes from the ortho and pointcloud. The ROI-top helps here so I don’t have to do that manually. Due to I know the height of the cranes, and because I’m always importing the same ROI, you would save my time if this is already included in the ROI import. Because right now I have to calculate the alignment first, just in order to adjust the ROI afterwards. More steps for me

After alignment the bottom of the ROI is set to the deepest ATP. sometimes I get holes in my ortho because of that so I always have to adjust it too.

Can’t say more, the function to import a ROI including the top and bottom at specific values was there in mapper already. Good for most user if they don’t need that. I say again it would help me in my daily work with your product.

Is it so complicated?