GeodePy.ntv2reader.ntv2_bicubic() demonstrate errors of various severity when interpolating within 1 grid node of the grid extents.
A comparison against the NTv2 bilinear method is a good way to identify such issues (differences are much larger than elsewhere in same region).
Examples are provided in the attached document GeodePy Issue170 Ntv2 bicubic error examples (1pg)
Issues include:
- binary file read errors occur within 54 arcsec (i.e. grid spacing) of southern extent of first grid, and northern extent of last grid
- i.e. trying to read outside of the binary file
- computation errors occur within 54 arcsec (i.e. grid spacing) of all extents, likely reading incorrectly from neighbouring part of binary file
- some shifts differ by centimetres, others by kilometres)
- Note only: Coordinates directly on Western extents are occasionally returned as 'outside of grid extents’
Note only: Coordinates directly on Northern extents are always returned as 'outside of grid extents’
These exceptions COULD be handled (use just those grid nodes available) but the use-cases are rare. Ok to leave as is.
GeodePy.ntv2reader.ntv2_bicubic() demonstrate errors of various severity when interpolating within 1 grid node of the grid extents.
A comparison against the NTv2 bilinear method is a good way to identify such issues (differences are much larger than elsewhere in same region).
Examples are provided in the attached document GeodePy Issue170 Ntv2 bicubic error examples (1pg)
Issues include:
Note only: Coordinates directly on Northern extents are always returned as 'outside of grid extents’
These exceptions COULD be handled (use just those grid nodes available) but the use-cases are rare. Ok to leave as is.