Fix issue-1309: Incorrect transmitter location in BistaticRange measurement
Fix incorrect transmitter location, issue #1309 (closed). Took the opportunity to reduce code by using the common ground measurement calculations.
Should I have a go at reducing the code in BistaticRangeRate
as well?