Documentation forthcoming

Documentation forthcoming

This is used for reading values from OPeNDAP where -90N is stored at the zero (first) index in the array.

This is used for reading values from OPeNDAP where 90N is stored at the zero (first) index in the array.

Note that this must also be used in conjunction with the hi and lo values for latitude in the OPeNDAP lookup array being swapped (see cmr.opendap.ous.variable/create-opendap-lookup-reversed).

This is used for reading values from OPeNDAP where -90N is stored at the zero (first) index in the array.

This is used for reading values from OPeNDAP where 90N is stored at the zero (first) index in the array.

Note that this must also be used in conjunction with the hi and lo values for latitude in the OPeNDAP lookup array being swapped (see cmr.opendap.ous.variable/create-opendap-lookup-reversed).

Documentation forthcoming

Documentation forthcoming

OPeNDAP indices are 0-based, thus gridded longitudinal data with 1x resolution is stored at indices from 0 to 359 and similar latitudinal data is stored at indices from 0 to 179. The max values for lat and lon are stored in the UMM-Var records as part of the dimensions. Sometimes those values are pre-decremented for use in OPeNDAP, sometimes not (e.g., sometimes max longitude is given as 359, sometimes as 360). This function attempts to ensure a consistent use of decremented max values for indices.

Longitude goes from -180 to 180 and latitude from -90 to 90. However, when referencing data in OPeNDAP arrays, 0-based indices are needed. Thus in order to get indices that match up with degrees, our longitude needs to be phase-shifted by 180 degrees, latitude by 90 degrees.