nt.tiepoints.get_tiepoints is specifically designed to return tiepoints for data sources utilized by the latest version of the seaice_ecdr. So passing am2 as the satellite will return tiepoints based on NSIDC-0802 for use in NSIDC-0803, which is what we want for the seaice_ecdr. But there are other options for ASMR2 data. The amsru_am2 "satellite" will return tiepoints derived from AMSRU data.
The "satellite" kwarg is misleading because it maps to a list of keys that are not themselves "satellites". E.g., 17_final maps to tiepoints that are for use with data from the F17 platform that is considered "final" from Goddard (NSIDC-0001).
Ideally, this function is updated to replace the satellite kwarg with e.g., platform and product kwargs. The combination of platformand product tells us which variant of a set of tiepoints should be returned, instead of curating a mapping of "satellite" to tiepoint set in this function.
nt.tiepoints.get_tiepointsis specifically designed to return tiepoints for data sources utilized by the latest version of theseaice_ecdr. So passingam2as thesatellitewill return tiepoints based on NSIDC-0802 for use in NSIDC-0803, which is what we want for theseaice_ecdr. But there are other options for ASMR2 data. Theamsru_am2"satellite" will return tiepoints derived from AMSRU data.The "satellite" kwarg is misleading because it maps to a list of keys that are not themselves "satellites". E.g.,
17_finalmaps to tiepoints that are for use with data from the F17 platform that is considered "final" from Goddard (NSIDC-0001).Ideally, this function is updated to replace the
satellitekwarg with e.g.,platformandproductkwargs. The combination ofplatformandproducttells us which variant of a set of tiepoints should be returned, instead of curating a mapping of "satellite" to tiepoint set in this function.