interpolation(...) is now at(...), i.e. grid.at(...), to avoid any confusion about whether extrapolation is supported
The within arg to contains(...) has been changed to margin
Changed the plain header to expect (lat_0, lon_0) to be the coordinate tuple of the first node of the grid, and (lat_1, lon_1) to be the coordinate tuple of the first node of the grid. In ALL cases. The builtin Gravsoft reader swaps signs and orders to fit with this.
Generalized BaseGrid to handle any grid orientation (left-right, right-left, upside-down, downside-up, and any combination thereof), everything determined from the values of lat_0, lat_1, lon_0, lon_1, which are also used to assign the correct sign to dlat, dlon.
Changed method names for BaseGrid:
interpolation(...)is nowat(...), i.e.grid.at(...), to avoid any confusion about whether extrapolation is supportedwithinarg tocontains(...)has been changed tomarginChanged the plain header to expect
(lat_0, lon_0)to be the coordinate tuple of the first node of the grid, and(lat_1, lon_1)to be the coordinate tuple of the first node of the grid. In ALL cases. The builtin Gravsoft reader swaps signs and orders to fit with this.Generalized
BaseGridto handle any grid orientation (left-right, right-left, upside-down, downside-up, and any combination thereof), everything determined from the values oflat_0, lat_1, lon_0, lon_1, which are also used to assign the correct sign todlat, dlon.