cnetcombinept doesn't properly set a prior lat/lon to the adjusted values
This will not have an impact on ISIS, since the fix was made in the application itself and not in an object.
The SETAPRIORIBEST option in cnetcombinept is intended to reset the a priori latitude and longitude values to the best available values. The best values are typically the adjusted lat/lon values produced by jigsaw.
The wrong ControlPoint method is invoked in the main to set these values correctly.
#11 Updated by Tyler Wilson 11 months ago
To make things easier for testing, I have combined all three of the cnetcombinept tickets into one ticket which can be tested by pointing your ISIS version here:
The other two tickets are:
I have tested this and it looks like the adjusted lat, lon, radius are copied to the apriori lat, lon, radius fields within the network as expected.