In general, the precision returned by GeodePy are suitable for the average (or great majority of) use case.
There MAY be cases, however, where a user wants to make comparisons of outputs at greater precision.
There seems no need to artificially round to the given precisions.
Consider returning the full float, or rounding to even greater precision.
GeodePy.ntv2reader.py ntv2_bicubic() and GeodePy.ntv2reader.py ntv2_bilinear()
round their lat and lon shift values (in arc seconds) to 6 decimal places (equivalent to approx 3/100th of a mm).
GeodePy.convert.geo2grid()
rounds Easting and Northing outputs (in metres) to 4 decimal places.
In general, the precision returned by GeodePy are suitable for the average (or great majority of) use case.
There MAY be cases, however, where a user wants to make comparisons of outputs at greater precision.
There seems no need to artificially round to the given precisions.
Consider returning the full float, or rounding to even greater precision.
GeodePy.ntv2reader.py ntv2_bicubic() and GeodePy.ntv2reader.py ntv2_bilinear()
round their lat and lon shift values (in arc seconds) to 6 decimal places (equivalent to approx 3/100th of a mm).
GeodePy.convert.geo2grid()
rounds Easting and Northing outputs (in metres) to 4 decimal places.