@davidhassell commented on this pull request.
> +alignment. As an example, such discontinuities are common in remote +sensing data and may be caused by combinations of the instrument scan +motion, the motion of the sensor platform and changes in the +instrument scan mode. When discontinuities are present, the domain is +first divided into multiple __continuous areas__, each of which is +free of discontinuities. When no discontinuities are present, the +whole domain is a single continuous area. Following this step, each +continuous area is segmented into interpolation subareas. The +processes of generating interpolation subareas for a domain without +discontinuities and for a domain with discontinuities is illustrated +in <<interpolation_subarea_generation>>, and described in more detail in +<<Appendix J>>. + +For each __interpolated dimension__, i.e. a target domain dimension for which coordinate interpolation is required, the locations of the tie point coordinates are defined by a corresponding __tie point index variable__, which also indicates the location of the continuous areas (<<compression-by-coordinate-sampling-tie-point-index-mapping>>). + +The interpolation subareas within a continuous area do not overlap, ensuring that each coordinate of an interpolated dimension is computed from a unique interpolation subarea. These interpolation subareas, however, share the tie point coordinates that define their common boundaries. Such a shared tie point coordinate can only be located in one of a pair of adjacent interpolation subareas, which is always the first of the pair in index space. For instance, in <<interpolation_subarea_generation>>, the interpolation subarea labeled `(0,0)` contains all four of its tie point coordinates, and the interpolation subarea `(0,1)` only contains two of them. When applied for a given interpolation subarea, interpolation methods, such as those described in <<Appendix J>>, must ensure that reconstituted coordinate points are only generated inside the interpolation subarea being processed, even if some of the tie point coordinates lie outside of that interpolation subarea. I thought the sentence flow was a bit obfuscated by too many commas: ```suggestion The interpolation subareas within a continuous area do not overlap, ensuring that each coordinate of an interpolated dimension is computed from a unique interpolation subarea. These interpolation subareas, however, share the tie point coordinates that define their common boundaries. Such a shared tie point coordinate can only be located in one of a pair of adjacent interpolation subareas, which is always the first of the pair in index space. For instance, in <<interpolation_subarea_generation>>, the interpolation subarea labeled `(0,0)` contains all four of its tie point coordinates, and the interpolation subarea `(0,1)` only contains two of them. When applied for a given interpolation subarea, interpolation methods (such as those described in <<Appendix J>>) must ensure that reconstituted coordinate points are only generated inside the interpolation subarea being processed, even if some of the tie point coordinates lie outside of that interpolation subarea. ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326*pullrequestreview-699747227__;Iw!!G2kpM7uM-TzIFchu!m13jlRHVa0s0DXIB3fHL4JO_pMWp8qonRobM_jnBFn3UBFlGuaVYEcEEZdXTwf2BSdUnqn_G8uc$ This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
