Values for Camera Optimization are high

[JasonSchilling1]

I'm generating orthos with a Phantom 4 Pro, using a 80% forward and 80% side overlap for flights at 100 meters and am routinely getting high values for the relative difference between initial and optimized internal camera parameters. The orthos look good and are fine for projects that don't require survey grade accuracy, but for some projects I need these values to be better. Has anyone run into this problem and found a solution?

[JasonSchilling1]

Here are the last two photos of the batch of 8.

[ViTran]

Hi Cody,

In your previous comment, you mentioned this:

 If you have ground control points, do you know how to withhold some from the processing and apply them as Check points to measure your output accuracy?  If you need instructions on that, I can send information.

Can we withhold the check points directly in the Drone2Map software? If you don't mind, could you share the information please?

Thanks!