Surprisingly, it is just a simple conversion. Here is an older post that explains it in detail:
http://forum.accurateshooter.com/threads/figuring-g7-based-off-g1.3893552/#post-36699032
Adam is correct, the conversion from
averaged banded G1 BCs to G7 is fairly straightforward, and a simple conversion
does work for the majority of applications. In his book entitled, "Applied Ballistics for Long Range Shooting, 2nd Ed." the values Bryan Litz published for a number of G1 and G7 BCs were very uniform in that the multiplication factor to go from G1 to G7 was almost uniformly 0.51. In a more recent book entitled, "Ballistic Performance of Rifle Bullets", conversion between the updated BC values exhibit a slightly wider multiplication factor range, from about 0.47 to 0.51, in order to exactly match the experimentally-determined values. If you take the
average of banded G1 BCs over 3000-1500 fps, which cover the velocity range we are typically interested in, and divide by 2, you'll end up with a G7 value that should be reasonably close to the true value. None of these estimates are "perfect", but should be close enough to get you on the target, even at longer distances.
Adam's use of that general formula above was valid; however, the G1 (starting) value he used (0.563) was slightly inflated because it is the single banded value (from Sierra) for velocities of 2080 fps and above. If you take the average of Sierra's banded velocities (>2080 fps = 0.563, 1640-2080 fps = 0.550, and <1640 fps = 0.480), you get an
averaged G1 BC of 0.531, which when multiplied by 0.51 would give a G7 value of 0.271, very close to what I estimated using Bryan's actual data and the 5% pointing increase fudge factor. I do not know whether Sierra's current BC values represent the fact that they now come pointed from the factory. I suspect that they
do represent the pointed form. If so, then my estimate of .270 G7 BC was reasonable. If Sierra's current G1 BC values
do not represent the fact that they are pointed, then I think the values are slightly inflated as based on Bryan Litz' testing and the results of people I know that have been using them.
In my hands, if the estimated BCs are within about 3-5% of the true value, the ballistic calculator predictions match very well to what I see in terms of actual drops at various distances using known MVs. In other words, it's not really noticeable above the noise. If the estimates differ by 5-7% (or more), the predicted drops based on a known MV will be off noticeably. As with almost everything, it boils down to whether or not I can shoot the difference (or reliably detect the difference). If the amount by which an
estimate differs from a
true value is not large enough that I can reliably shoot or at least detect the difference, then the estimate provides a valid and useful working tool for me.
None of that means that I am not willing to update "estimates" as new and pertinent data become available. However, in F-Class we have a pretty large aiming black on the target. All I really need to do is get on with the first shot, then I can correct as necessary based on the shot marker position. Those are not very stringent accuracy requirements, and I can tell you that as long as the wind conditions aren't extremely challenging, I am rarely outside the 7-ring or 8-ring on my first sighting shots at 600-1000 yd using these type of BC estimates. However, making first round hits on a much smaller target certainly requires better estimates than I normally need. If that was my requirement, I would start with the BC estimate, then determine my actual DOPE on multiple days over a range of atmospheric conditions, if possible, to obtain the best possible data with my specific setup.