Statistical Assessment of Sea-Surface Salinity from SMAP: Arabian Sea, Bay of Bengal and a Promising Red Sea Application

Sea-surface salinity (SSS) is an essential climate variable connected to Earth’s hydrological cycle and a dynamical component of ocean circulation, but its variability is not well-understood. Thanks to Argo floats, and the first decade of salinity remote sensing, this is changing. While satellites can retrieve salinity with some confidence, accuracy is regionally dependent and challenging within 500–1000 km offshore. The present work assesses the first four years of the National Aeronautics and Space Administration’s Soil Moisture Active Passive (SMAP) satellite in the North Indian Ocean. SMAP’s improved spatial resolution, better mitigation for radio-frequency interference, and land contamination make it particularly attractive to study coastal areas. Here, regions of interest are the Bay of Bengal, the Arabian Sea, and the extremely salty Red Sea (the last of which has not yet received attention). Six SMAP products, which include Levels 2 and 3 data, were statistically evaluated against in situ measurements collected by a variety of instruments. SMAP reproduced SSS well in both the Arabian Sea and the Bay of Bengal, and surprisingly well in the Red Sea. Correlations there were 0.81–0.93, and the root-mean-square difference was 0.38–0.67 for Level 3 data.


Introduction
The National Aeronautics and Space Administration's (NASA) Soil Moisture Active Passive (SMAP) satellite launched on 31 January 2015 was designed as a soil-moisture mission, but expanded to retrieve sea-surface salinity (SSS) from space continuing the legacy of the Aquarius mission (2011)(2012)(2013)(2014)(2015), the NASA pathfinder ocean-salinity satellite [1][2][3][4]. SMAP spinning antenna allows it to observe Earth in nearly full 360°scans in few seconds, and overlapping loops create a 1000 km wide swath. The surface footprint is 39 × 47 km, and the satellite observes each ground location in both forward (fore) and backward (aft) directions, with observations taken a few minutes apart. The SMAP satellite's 40 km effective spatial resolution is similar to that of Soil Moisture Ocean Salinity (SMOS), the European Space Agency's salinity mission launched in November 2009, and quite improved relative to the retired Aquarius (about 150 km). SMAP has an exact repeat cycle of eight days, but it reaches global coverage in about 2-3 days. SSS retrievals are available from April 2015 to the present.
Ocean salinity is far from being the primary factor contributing to the received signals by satellite L-band radiometers. There are several unwanted signals that must be removed to retrieve salinity [1,2,4]. These unwanted signals include extraterrestrial contributions (e.g., galaxy, moon, sun), antenna-radiation emissions, Faraday rotation in Earth's ionosphere, atmospheric attenuation, sea-surface temperature and roughness, and land contamination near coastlines (i.e., leakage of emissivity from the land surface into the radiometer receiver [3]). Besides that, there is also Radio Frequency Interference (RFI) that results from the unauthorized use of the protected L-band that may measurements, such as from Argo floats; others can be hourly or daily averages, such as time series from moored buoys, and these differences may affect comparison statistics between satellite and in situ observations. Moreover, there is variability within the satellite footprint that is captured by in situ measurements but not by the satellite, in which SSS can be interpreted as a spatial-average over the footprint [33][34][35]. Because of the inconsistency between satellite and in situ measurements, the present work uses the term "difference" instead of "error" to refer to it (see [4] for a discussion on this matter). Figure 1 shows the mean SSS field for four years (September 2015 to September 2019) based on Argo in situ observations mapped into a 1°× 1°grid [36], and the mean fields from the two SMAP products that are evaluated in the present work. The period for calculating the mean fields was chosen to start in September 2015 because there was an indication that SMAP SSS retrievals may have been degraded during the early months of the mission (April-August 2015) [6]. In the long-term mean, in situ and satellite fields agree relatively well with a strong east-west gradient of surface salinity: SSS varies from less than 32.4 in the Bay of Bengal to more than 36.6 in the Arabian Sea, although RSS/JPL products slightly under-/overestimated in situ SSS as measured by Argo in the Arabian Sea. Broadly speaking, the Indian Ocean salinity pattern is controlled by four major processes [37][38][39][40][41][42][43]: net-air sea fluxes (evaporation minus precipitation), runoff from large rivers in the Bay of Bengal, inflow of relatively fresh waters from the Pacific Ocean through Indonesian throughflow straits, and inflow of saltier waters from the Red Sea and the Arabian/Persian Gulf. The wide salinity range and a variety of processes controlling SSS make the North Indian Ocean especially attractive to assess spaceborne SSS measurements.
A difference in the maps of Figure 1 is the absence of in situ observations in marginal seas (the Red Sea and the Arabian/Persian Gulf in the western, and the Andaman Sea in the eastern). Marginal seas are usually not included in Argo-gridded products [4,36] because the amount of in situ observations is much reduced and even nonexistent in these regions, such as in the very shallow Arabian/Persian Gulf (maximum depths of 110-160 m [44]). In the SMAP fields of Figure 1, there are also defined SSS values closer to the coast than in the Argo SSS mean-field as float-parking depth is around 1000 m, with few observations in shallow waters (<1000 m) in the standard Argo program [36].
Apart from Argo, other sources of in situ salinity observations are also sparse in time and space in marginal seas of the Indian Ocean. Take, for instance, the extremely salty Red Sea. Most knowledge of salinity dynamics there is based on numerical simulations, and few in situ observations exist [22,[45][46][47][48][49][50]. The scarcity of salinity measurements may be surprising because the Red Sea has one of Earth's largest evaporation rates with an annual mean of around 2 m/yr, which makes the Red Sea a crucial source of moisture for the arid Middle Eastern atmosphere and an essential component of the regional hydrological cycle [46,[51][52][53]. In consequence of the extreme evaporation, freshwater must be imported from adjacent basins (the Gulf of Aden and the Arabian Sea) to keep sea level and mean salinity in a steady-state [48]. As part of the ocean dynamics (which is controlled by buoyancy forcing dominated by salinity [54]), one of the saltiest water masses of the global oceans is formed in the extreme north of the Red Sea: the Red Sea Overflow Water (RSOW), which escapes the marginal sea and spreads to the intermediate depths of the whole Indian Ocean [24]. Although salinity is a crucial variable in the Red Sea, both as an indicator of the regional hydrological cycle and as a dynamical forcing, our knowledge about its variability is incipient given the scarcity of in situ observations e.g., [22,51].
Therefore, it is appropriate to ask whether SMAP could capture salinity in a narrow marginal sea such as the Red Sea. It is now known that SMAP can retrieve signals, although with limitations, in complex regions such as the Mediterranean Sea and the Arctic Ocean. However, the maximum Red Sea width is only about 355 km with coastlines on both sides, so land contamination and the RFI may be a severe issue precluding SSS retrievals. A similar problem may occur in the Gulf of Aden that is surrounded by land. The present work addresses this problem through exploratory analysis of SMAP data in these particular areas, and results are promising for the Red Sea.
The paper is organized as follows: Section 2 describes satellite and in situ SSS data, and collocation procedures and statistics used to assess SMAP performance; Section 3 outlines statistical-analysis results for the Arabian Sea (Section 3.1), Bay of Bengal (Section 3.2), and the Red Sea (Section 3.3); Sections 4 and 5 provide a discussion and a summary of the present work, respectively.

SMAP Products
This work assesses the latest version of two different SMAP product series in the North Indian Ocean (0°-31°N; 30°-100°E) against in situ SSS observations collected by a variety of instruments in the period of 1 April 2015 to 30 September 2019. Because the goal here was to evaluate SMAP SSS, the early months of the mission (April-August 2015), in which retrievals may have been degraded [6], were included. All SSS observations used in the present work are in the 1978 Practical Salinity Scale (PSS-1978) [55].
One SMAP product series was processed by using the Geophysical Model Function (GMF) for the Combined Active-Passive (CAP) algorithm [3,7,56], and distributed by the NASA/JPL/Physical Oceanography Distributed Active Archive Center (PO.DAAC). Hereafter, we refer to this product series as CAP/JPL. The other SMAP series was produced by RSS using Aquarius version 5.0 GMF adapted to the SMAP mission [2,57]. From now on, this study refers to those SMAP products as RSS. Except for a significant gap between 17 June 2019 and 25 July 2019 when the SMAP satellite was offline due to a spacecraft issue, both series span almost continually from April 2015 to the present, and are composed of Level-2 (L2; along-track data) and Level-3 (L3; global gridded maps) datasets.
Besides distinct GMFs, the RSS and CAP/JPL series also differ in correction schemes and ancillary data used to retrieve SSS. For example, CAP/JPL relies on winds from the National Oceanic and Atmospheric Administration/National Centers for Environmental Prediction (NOAA/NCEP) Global Forecast System (GFS) atmospheric model. The RSS series, on the other hand, uses Cross-Calibrated Multiplatform (CCMP) gridded surface vector winds that are mostly based on satellite microwave winds. The use of distinct wind products is likely to contribute to differences in salinity retrievals between CAP/JPL and RSS in the North Indian Ocean, which is dominated by the South Asian monsoonal wind regime. A full description of processing, ancillary data, and global validation is given by Fore et al. [7] (CAP/JPL) and by Meissner et al. [57] (RSS).
CAP/JPL products used here belong to version 4.2, released on 24 January 2019, and comprise of L2B data distributed on a 25 km swath grid with 1624 × 76 cells (along/cross-track) per satellite revolution and L3 8-day running average fields [7,58]. These L3 fields are available on a uniform 0.25°× 0.25°rectangular grid and have daily time steps. For producing them, L2B data were averaged over the 8-day period (centered at midpoint), and a Gaussian weight function with a search radius of about 45 km and a half-power radius of 30 km was used to map the data into the 0.25°grid. For the CAP/JPL v4.2 datasets, the effective spatial resolution of the SSS fields is about 60 km. Globally, the mean bias of CAP/JPL v4.2 in relation to Argo-gridded products is less than 0.1, with an rmsd of 0.3 [7].
RSS products belong to version 4.0, released on 29 August 2019, and include L2C and L3 8-day running average datasets [6]. For both processing levels, RSS data are distributed in two spatial resolutions: 40 and 70 km. The 70 km data are obtained by smoothing the 40 km product using a simple near-neighbor averaging scheme over 9 cells (8 adjacent and the center cell itself) and should be considered the RSS official product for open-ocean applications. Different from CAP/JPL, in the RSS processing, Level-1 swath data were first interpolated onto a fixed 0.25°Earth grid at approximately 40 km spatial resolution using Backus-Gilbert optimal interpolation that maintains the approximated resolution and shape (39 × 47 km) of the original data (see Meissner et al. [57] for more detail). Consequently, the RSS L2C grid has different dimensions (1526 × 720 cells) than the CAP/JPL L2B. For each location in L2C data, there are SSS retrievals for both fore and aft directions [2]. This format is different from that of L2B CAP/JPL, in which a single salinity retrieval is available per cell. Besides the 1-month data gap in June/July 2019, there are also some other missing L2C data, since salinity is not retrieved in RSS products when there are incomplete ancillary data [57].
The rmsd of L3 RSS-70 km version 3.0 and Argo gridded data was about 0.15 at 1°resolution after August 2015, being slightly higher for the RSS-v3 40 km (around 0.2). No global rmsd estimation for version 4.0 has been released yet. Meissner et al. [57] showed that, during the early months of the SMAP mission (April-August 2015), the rmsd was much higher in version 3 ( Figure 21 in [57]), indicating a significant degradation in SMAP SSS. However, the causes are unknown to date.

Argo Floats
For the present work, SSS observations, collected by Argo floats in the North Indian Ocean (0°-31°N; 30°-100°E) for the period of 1 April 2015 to 30 September 2019, were selected from the global CORIOLIS repository (http://www.coriolis.eu.org/) that contains data from all Argo floats deployed to date. This 4-year subset consists of 37,693 measurements ( Figure 2) after the quality-control (QC) procedure described below, and includes both delayed-mode and real-time data from 320 individual floats. About 12% of the original measurements were rejected in the QC. From the original subset, only floats with valid salinity measurements between the sea surface and 10 m depth were selected. For each float (time, position), SSS refers to the nearest sea-surface depth. In the 4-year QC subset, about 42.6% of SSS measurements were collected between 2 and 5 m depth, 30.1% between 5 and 10 m, and 27.3% were shallower than 2 m. The seasonal distribution of SSS measurements is relatively homogeneous in the North Indian Ocean as a whole: June holds a maximum number of observations with 10.5% of the total, and November the minimum (7%). For comparison with SMAP data, we gave preference for delayed mode or adjusted values. Only SSS measurements with quality-control flag issued as 1 or 2 (good or probably good) for position, time, pressure, and salinity, were selected, and duplicate data were discarded.
Moreover, 53 floats in which salinity or pressure sensors were flagged in the Argo gray list were not used for comparison with SMAP over the flagged period except for the Red Sea. From the 6 Argo floats there, 4 floats (1900959,1900960,1901521,6900425) belong to the Seabird CTD batch (6000-7100) that may develop a high salinity bias within 2 years of deployment. In situ SSS observations are scarce in the Red Sea, and because of that, these Argo floats were used for statistical analysis. The complete Argo float gray list can be found at https://www.nodc.noaa.gov/argo/grey_floats.htm (or at ftp://ftp.ifremer.fr/ifremer/argo/ar_greylist.txt). A visual screening was also used to eliminate clear outliers in Argo measurements that occurred in near real-time data.

Thermosalinograph (TSG)
All TSG observations in the North Indian Ocean between 1 April 2015 and 30 September 2019 were downloaded from the CORIOLIS repository that also distributed data from the Global Ocean Surface Underway Data (GOSUD) Project. The CORIOLIS/GOSUD dataset consists of SSS observations collected by 6 different platforms (Table 1). However, this dataset lacks TSG data collected by U.S. research vessels that are available at the NOAA National Centers for Environmental Information (NOAA/NCEI) TSG portal. Thus, we augmented the original CORIOLIS/GOSUD dataset with NOAA/NCEI TSG data to have comprehensive TSG salinity data (Table 1). Before merging the 2 datasets, the respective quality-control flags were individually applied to each file, and only observations classified as of good or probably good quality were selected, totaling 236,750 samples. The nominal depth of TSG intake water varies from ship to ship; in our set, it went from 1.6 to 9 m. These SSS along-track observations have a spatial resolution of about 1-3 km and were taken under different years. About 26.8% of TSG measurements were obtained in 2015, 17.2% in 2016, 7.3% in 2017, 14.6% in 2018, and 34.1% in 2019. Seasonally, 51% of all observations were taken in summer (June-July, boreal seasons hereafter), while only 6% in winter (December-March). The spatial distribution of TSG data in the North Indian Ocean is also much more heterogeneous than that from Argo floats, with large areas without any observation ( Figure 3).  Table 1 for details about these data).

Moored Buoys
Daily-average time series of surface salinity from 13 Research Moored Array for African-Asian-Australian Monsoon Analysis and Prediction (RAMA) buoys located north of the equator ( Figure 2) were downloaded from the Tropical Atmosphere Ocean project, Pacific Marine Laboratory (TAO/PMEL) website [59]. Only salinity observations from the first 2 depth levels (1 and 5 or 10 m) with quality-control flag issued as good were used. Six moorings are located in the equatorial zone at (0°-1.5°N), 3 in the Arabian Sea (4°-15°N, 65°-67°E), and 4 in the Bay of Bengal (4°-15°N, 90°E) ( Figure 2). From the 13 buoys, only 4 spanned the 4 years of SMAP operation ( Table 2). Even in the overlapping period between SMAP and in situ observations, some buoys returned few valid measurements, such as the 2 buoys at 1.5°E, east of 80°(about 30% for both surface and subsurface sensors; Table 2). As there were few observations in both depths, these 2 buoys were not used in the comparison with SMAP.
Besides observations from the RAMA array, we also used SSS observations at a nominal depth of 1 m from the WHOI Bay of Bengal Mooring at 18°N-89.5°E ( Figure 2). The WHOI mooring [60] worked from 9 December 2014 to 29 January 2016, overlapping for 10 months with SMAP. Surface data, including meteorological parameters, are available at the WHOI Upper Ocean Process Group website (http://uop.whoi.edu/projects/Bengal/QCData.html), with resolutions of 1 min, hourly, and daily averages. All data were quality-controlled by the WHOI group. For comparison with SMAP, this study used the daily averages. Different from the RAMA buoys, the WHOI SSS time series is almost complete.

Ship-Based CTD
Over the SMAP era (April 2015-September 2019), 2 meridional transects were occupied in the North Indian Ocean as part of the international GO-SHIP program [32] (Figure 2). One transect was in the Arabian Sea (2018) and is known as the I07N line. The second transect was in the Bay of Bengal (2016) and is known as the I09N.
In the Arabian Sea, the northern portion of I07N extended from the equator to 18°N and took place between 22 May 2018 and 4 June 2018. SSS observations were collected in a total of 48 stations, spaced 50 km apart on average. In the Bay of Bengal, the northern portion of the I09N (0°N-18°N) was occupied in 10-24 April 2016 in a total of 57 stations (also spaced 50 km apart in average). For both transects, SSS was collected using ship-based CTD instruments and it refers to salinity at 2 to 5 dbar. In the GO-SHIP, CTD salinity observations were calibrated against in situ samples from Niskin bottles, which were measured using Guildline 8400 Austosal salinometers, calibrated using the International Association for the Physical Sciences of the Oceans (IAPSO) Standard Sea Waters (SSW). GO-SHIP salinity observations are of the highest quality and aim for climate studies. Data are publicly available at the CLIVAR Carbon Hydrographic Data Office (CCHDO) website.

Collocation between SMAP and In Situ Observations and Statistics
For assessing several SMAP products, pairs of concurrent SMAP and in situ observations (Argo, TSG, moored buoys, and ship-based CTD) were first formed by selecting satellite data from the closest grid cell to in situ observations (details are given below in the respective subsections). Currently, there is no consensus in the community about the best methodology and a single criterion to do the match up because in situ and satellite SSS observations are intrinsically different. Any criterion is ad hoc. Here, this task was performed individually for each of the 6 SMAP products that were assessed: 8 day running average L3 (CAP/JPL, RSS-40 km, and RSS-70 km) and L2 (CAP/JPL, RSS-40 km, and RSS-70 km). No space-time interpolation was performed for SMAP data. This study refers to these data pairs (SMAP, in-situ) as collocated observations. These pairs, however, are not strictly collocated because of the intrinsic differences between satellite and in situ observations [4,33,34].
Basic statistics such as the linear correlation coefficient, and histograms were calculated for each SMAP product for the collocated datasets to assess SMAP performance in the North Indian Ocean in both the spatial and temporal domains. These statistics are generally used in studies evaluating satellite salinity observations [1,3,8,9,12,13,[16][17][18]21,61].

Argo Collocation Procedure
For the L3 datasets, the following steps were performed. First, for each Argo observation, SSS argo (t,x,y), the SMAP field correspondent to day t was selected; then, the salinity value at the grid cell in which the in situ observation resided (x,y) was extracted. L3 daily fields are averages, centered at the midpoint over an 8-day interval; therefore, the comparison is between measurements that are not quite equivalent (Argo floats give instantaneous measurements).
For the L3 RSS-40 km product, a total of 36,285 collocated pairs were formed in the North Indian Ocean, 36,068 for the RSS-70 km, and 36,553 for CAP/JPL. These collocated subsets excluded pairs in which salinity difference between SMAP and Argo was larger than 2, which was less than 0.5% of the total. For example, from the 36,197 original L3 RSS-70 km pairs, only 129 had salinity differences larger than 2. These pairs were labeled as outliers and discarded as these differences might be due to Argo errors because a large portion of Argo data in the North Indian Ocean have only passed through automatic near-real-time QC checking. In the collocated L3 pairs, the median distance between the SMAP grid cell center and Argo float positions was about 11 km.
For the L2 products, a slightly different match-up procedure was adopted. The aim was to have data pairs that were obtained as close in both time and space as possible. For that, for each in situ SSS argo (t,x,y), the algorithm selected the SMAP value from the closet grid cell to the in situ position on a radius of 25 km, taken up to ±12 h from the in situ observation. For RSS products, the ancillary 32-bit quality-control flag -available in the L2C files -was used to discard strongly degraded SMAP measurements [57] (pp. 37,39). Besides these QC checks, L2C data with rain flags were also discarded. For comparison with in situ observations, valid fore and aft data, which were taken minutes apart, were averaged. Only collocated observations that had both the 40 and 70 km salinity retrievals were considered. For L2B CAP/JPL, the ancillary 16-bit quality-control variable was used to discard SMAP salinity retrievals that were not of good quality [7] (Section 6.2.24). Collocated observations in which salinity differences between L2 and in situ data were above 2 were also discarded for statistical comparisons (136 data pairs for RSS and 120 for the CAP/JPL).
A total of 11,378 collocated pairs were formed for the RSS L2C data, and 13,475 for the L2B CAP/JPL. In these pairs, the median distance between SMAP grid cell center and Argo float positions was about 11.3 km (RSS) and 9.5 km (CAP/JPL), and 5.6 h for both. Note that, for the CAP/JPL, many L2B files for 2015 had the row_time variable (approximate observation time for each swath row) with month/year that did not match the filename timestamp. For safety's sake, these files were discarded and not used for comparison with in situ data.

TSG Collocation Procedure
Unlike Argo observations, TSG data are collected along the ship tracks with a high spatial resolution of 1 to 3 km (Figure 3), which results in a substantial number of samples. The following steps were performed to match up satellite and TSG observations; the aim was both to avoid oversampling bias and to smooth submesoscale variability present in TSG observations. For the L3 products, for each day t that TSG observations existed, the respective SMAP field was selected. Then, SSS TSG from day t was spatially averaged over SMAP grid cells (i, j). Then, for each grid cell (i, j) in which SMAP and TSG data were valid, the pair was formed as [SMAP(t, i, j) TSG (t)]. For SMAP data, no interpolation/smoothing was performed. Following this procedure, a total of 5,116 collocated pairs were formed for the L3 RSS-40 km product over the North Indian Ocean; 4,946 for RSS-70 km, and 5199 for CAP/JPL.
A similar procedure to that described above was used for matching up the TSG to L2 data except that the SMAP data had to be no more than ±12 h apart from the averaged grid-cell TSG observation. Similar to the Argo case, only QC SMAP data was used, and the fore and aft data were averaged for the RSS product. A total of 2340 (40 km) and 2307 (70 km) pairs were formed for the L2C RSS product and 1908 for the L2B CAP/JPL. The time-mean difference between the observations in these collocated datasets is about six hours. Note that the number of collocated observations is much less for the CAP/JPL product because the files from 2015 were not used (see the previous section), and many of the TSG observations are from this year (Table 1). In various TSG collocated observations, there is a large number of pairs with salinity differences above 2 (3-10%). Thus, these pairs cannot be considered outliers and were kept for the statistical analysis, unless otherwise stated.

Collocation Procedure for Moored-Buoy Time Series and Ship-Based CTD
For in situ observations from buoys and ship-based CTDs, only comparisons with L3 SMAP products were performed, since these in situ data were much fewer and more scattered in space and time than those of the Argo and TSG datasets. For the buoys, the SMAP SSS time series from the grid cells at the buoy locations were extracted. For ship-based CTDs, for each SSS CTD (t, x, y) in situ observation, the salinity value from the grid cell in which the in situ observation resided (x,y) was extracted for same day t as that in the in situ data.

Results
In the present work, the 80°E meridian was used to delimit the salty western from the much fresher eastern (Figure 1). The western side encompasses the Arabian Sea, the Gulfs of Aden and Oman, and the Red Sea and the Arabian/Persian Gulf. The eastern side includes the Bay of Bengal and the Andaman Sea. Because there are no in situ SSS observations in the Arabian/Persian Gulf over the SMAP era in public repositories such as CORIOLIS, GOSUD, or NCEI (see Figures 2 and 3), this study did not perform a statistical evaluation there.
This section starts by assessing SMAP salinity in the Arabian Sea, the Bay of Bengal, and their surroundings. A comparison with the Red Sea is made in a dedicated section since the Red Sea is a challenging region for salinity remote sensing. For the Red Sea, the analysis is exploratory and based on TSG data besides the six Argo floats.

Arabian Sea
From all collocated SMAP and Argo observations, around 60% are located west of the 80°E (excluding the Red Sea), which this study refers to as the Arabian Sea for short (although it also encompasses the near-equatorial area, and the Gulfs of Aden and Oman). About half of the collocated Argo observations were taken between 2 and 5 m depth (Table 3), and their temporal distribution is relatively homogeneous, with all seasons well-represented. Spatially, Argo data density is higher in the eastern side of the Arabian Sea, with 80-85 observations per 0.5°grid cell over four years (Figure 2). In the region west of 60°E, Argo data density was, on average, much lower. Table 3. Comparison of collocated SSS from SMAP and Argo observations in Arabian Sea (0°-31°N; 30°-80°E, excluding Red Sea) between 1 April 2015 and 30 September 2019. Upper part: number N of collocated observations over considered period, number of individual Argo floats, and vertical distribution of Argo observations in relation to total of collocated data in the region. Middle part: statistics (mean, maximum, minimum, standard deviation, and skewness) for each individual dataset (values between brackets are for Argo, and outside for SMAP). Lower part: statistics of collocated observations. correl: linear correlation coefficients that were significantly different from zero at 95% confidence (p-value); ∆: differences between SMAP and Argo observations (SMAP − Argo); bias: mean difference (bias = ∆); rmsd: root mean square difference; skew(∆): skewness of probability distribution of the differences. Values between parenthesis in Level 2 columns are for RSS-L2C 40 km product; between brackets are for Argo. Overall, all products reproduce Argo SSS observations in the Arabian Sea relatively well (Figure 4). Correlation coefficients vary from 0.71 (L2B CAP/JPL) to 0.94 (L3 RSS-70 km), with statistics improving with the smoothing of SMAP data in space and time (Table 3). For instance, for L3 products, correlation increases, and rmsd decreases with spatial smoothing, such that CAP/JPL (60 km) has better performance than RSS-40 km but worse than RSS-70 km. A similar improvement is observed when SMAP data is averaged in time, with correlation being lower and rmsd higher for L2 products when contrasted with the respective L3 data (Table 3). For example, RSS-40 km data have an rmsd of 0.41 for L3, but 0.59 for L2. Scatter plots in Figure 4 also show that SMAP products with less smoothing (L2 and L3 RSS-40 km) have high salinity values that were not observed by Argo.
Basic statistics of SSS distributions -mean, minimum, standard deviation, and skewness -are similar for different datasets (Table 3, middle), with all of them presenting moderate-high, left-tailed skewed distribution (long tail in low salinity values). Statistical distributions from Argo data, however, tend to be slightly more skewed than those from SMAP products.  (Table 4) or SMAP-RAMA (Table 5) datasets. This agreement is despite TSG observations being concentrated closer to the Arabian Peninsula coastline (and not well-distributed seasonally), and RAMA buoy array is located in the eastern Arabian Sea. In general, correlations for the SMAP-TSG datasets (0.52-0.82) are worse than those for SMAP-Argo (0.71-0.94), but rmsd is mostly of the same order (0.3-0.4 for L3 products). In comparison with RAMA buoys, the correlations of several collocated SMAP-RAMA datasets (for both surface and subsurface in situ observations) are in agreement (0.64-0.95) with the ones found for the SMAP-Argo, but the rmsd (0.2-0.4) are overall lower (Table 5).
SMAP also captures well SSS spatial variability during the GO-SHIP I07N cruise in 2018 (Figure 5a), which has a similar resolution (≈ 50 km) to the satellite. Salinity steadily increases northward from the equatorial zone to the heart of the Arabian Sea in both the in situ and the L3 dataset. However, SMAP not only captures this basin-scale pattern, but also mesoscale salinity peaks and troughs observed in GO-SHIP (gray shadings in Figure 5a). Bias is negligible for CAP/JPL, but it is negative for both RSS products (Table 6)-there is an apparent offset, albeit small, in the RSS curves in Figure 5a, especially between 8°and 15°N.
Despite the negligible bias, CAP/JPL is saltier than GO-SHIP from 4°to 8°N (Figure 5a). Correlations are high, as expected, in GO-SHIP (0.85-0.94) as GO-SHIP only samples open-ocean waters. The rmsd, however, is of the same order as for the other analyzed datasets here (0.20-0.39).  Table 5. Comparison of SSS observations from SMAP and RAMA array buoys (daily averages) at 1 m and at subsurface (5 or 10 m; see Table 2) in the Arabian Sea between 1 April 2015 (or buoy start time, which is recent) and 30 September 2019 (or end time for nonoperational buoys). The same statistics as shown in Table 3. Values between brackets relative to subsurface in situ observations, and outside brackets at 1 m depth. Linear correlation coefficients were significantly different from zero at 95% confidence (p-value < 0.001).  , the messed pattern between 8°and 10°N was because ship trajectory turned around itself, as seen in Figure 2. Red curves refer to in situ observations. Grey shadings highlight mesoscale peaks and troughs in salinity captured by SMAP. In conclusion, RSS and CAP/JPL products compare similarly well with Argo, TSG, RAMA, and GO-SHIP observations in the Arabian Sea. Overall, RSS has slightly better skills in the Arabian Sea (higher correlation and lower rmsd) compared with similar CAP/JPL products, but these skill differences may not be statistically significant. Indeed, for GO-SHIP, CAP/JPL presents better statistics (Table 6).
However, a crucial difference exists between the two product series. While for all RSS datasets, the bias (∆) is negative in relation to Argo, TSG, GO-SHIP, and almost all RAMA buoy data, in CAP/JPL products, bias is of the same strength but positive (Tables 3-5). This indicates that salinity from RSS products is typically fresher than that from in situ observations, while saltier in CAP/JPL. This pattern can also be seen, for example, in the scatterplot between SMAP and Argo shown in Figure 4-most data pairs fell to the right of the 1:1 line in RSS products and left in CAP/JPL.
Freshening/salting satellite bias is not restricted to the Arabian Sea, a particular processing level, or in situ observation type. They are consistent between the L2 and L3 datasets, and found both in the western and eastern basins, although they are larger in L2 products ( Figure 6). If SMAP-Argo salinity differences, shown in Figures 6a,b, for instance, are averaged over boxes of 5°× 5°, RSS freshening bias is more prominent in the eastern Arabian Sea and the western side of the Bay of Bengal (Figure 7). In the equatorial zone and the eastern Bay of Bengal, the RSS bias is less prominent. In general, CAP/JPL bias is more homogeneous in terms of spatial distribution than that of RSS, although CAP/JPL salting is higher in the western Arabian Sea and lower in the eastern. Spatially, correlations and rmsd between SMAP and Argo have a defined pattern in both RSS and CAP/JPL products ( Figure 8). Mainly, correlation increases and rmsd decreases from west to east within the Arabian Sea. This pattern is observed in all six products evaluated here, although Figure 8 only shows two products (L3 RSS-70 km and CAP/JPL) for the sake of clarity. In the western Arabian Sea, performance is slightly better for the L3 RSS-70 km product when compared with L3 CAP/JPL. Thus, most TSG data are located in the region of lower agreement (western Arabian Sea), while the RAMA array is in the higher agreement area (eastern). Therefore, comparison statistics are shown in Table 4 (TSG) and Table  To determine the overall SMAP skill in the Gulf of Aden, the collocated Argo and TSG data were merged into two single datasets, one for L3 CAP/JPL and the other for L3 RSS-70 km, and statistics were recalculated. A total of 1260 (RSS) and 1447 (CAP/JPL) pairs were formed for the area between 10°-15°N and 43.5°-51°E. When both Argo and TSG observations are considered together, bias follows the same pattern as before: the RSS product underestimates SSS by 0.11, and CAP/JPL overestimates by 0.37. In this comparison, the rmsd is lower for CAP/JPL (0.35 versus 0.55 for RSS), but correlations are similar for both SMAP products (0.42 and 0.43 for RSS). Although SMAP L3 SSS time series are generally noisier than RAMA salinity observations in the Arabian Sea, SMAP captures overall seasonal and subseasonal variability in buoy locations south of 15°N ( Figure 9). However, SMAP sometimes does not capture the intensity of salinity drops in the equatorial zone, for instance, in January-March 2019 at the 1.5°-67°N buoy. The buoy measured a much stronger freshening than those observed by the satellite (Figure 9d). For the 15°N-65°E mooring, in situ time series was short and with many gaps, and was not shown in Figure 9 for the sake of clarity.  5°N, 4°N, and 8°N, plots show RAMA observations at subsurface (10 m depth) because time series at these depths have more valid measurements; correlations are higher at these subsurface depths (see Table 5).
In order to evaluate seasonal SMAP performance, statistics (correlation, biases, and rmsd) were calculated in a monthly base using collocated Argo datasets, which constitutes the largest dataset in the Arabian Sea. In this case, all year round, bias is negative for RSS products and positive for CAP/JPL (not shown), confirming the previous analysis. The RSS-70 km product also has slightly better skill than the CAP/JPL and the RSS-40 km products -higher correlations and lower rmsd, but CAP/JPL is better than RSS-40 km (Figure 10a). Figure 10a only shows monthly correlation and rmsd for the L3 datasets, but the plot is similar for L2 products, except that correlation coefficients are lower and rmsd is higher than those of the L3. For all products, correlation in the Arabian Sea tends to be slightly lower in the second half of the year, especially for RSS-40 km that has a well-defined minimum in October. This pattern is also clearly observed in the L2 products (not shown).

Bay of Bengal
In the region east of 80°E, the seasonal distribution of Argo floats is not as homogeneous as west of that meridian. There are almost double the collocated Argo measurements in June during the wet summer monsoon (about 13% of the total) than in November (7%). Spatially, data density is higher in the interior of the Bay of Bengal than in the equatorial region ( Figure 2). Fewer observations exist in the Andaman Sea (92°-100°E). For simplicity, this study refers to the region east of 80°E as the Bay of Bengal, although it also includes the equatorial zone and the Andaman Sea.
The Bay of Bengal is much fresher than the Arabian Sea in both satellite and Argo observations. Minimal salinity in Argo is around 21-22, which is well-captured by all SMAP products (Table 7, middle). Although salinity variability is more prominent in the Bay of Bengal (high standard deviation and wide salinity range), SMAP is more strongly correlated with Argo here (0.89-0.96) than in the Arabian Sea (0.71-0.94). The rmsd, however, is of the same order, which means that signal-to-noise ratio (SN = std SMAP /rmsd [12,16]) is higher in the Bay of Bengal.
As in the Arabian Sea, L2 data present increased rmsd (0.40-0.68) when compared with L3 products (0.35-0.45), but the correlation is similar for L2 and L3 products (which is different from the western basin). The RSS mean freshening bias is negligible in the Bay of Bengal (−0.07 to −0.04), but for CAP/JPL products, salting bias (0.21-0.24) is still present and with similar strength as in the Arabian Sea. The difference between RSS and CAP/JPL can be clearly seen in Figure 7, where most regions in the Bay of Bengal has a bias between −0.1 and 0 in the RSS product, while it is positive and higher in CAP/JPL. In the extreme north of the Bay of Bengal, both RSS and CAP/JPL products show accentuated negative bias (Figure 7), but this region has few collocated Argo observations (less than 50 over four years), and no publicly available TSG data. Thus, this intense freshening may be unreliable. Scatter plots in Figure 11 reflect the better agreement between SMAP and Argo floats in the Bay of Bengal. Data pairs are cohesive around the 1:1 relationship, and no outstanding bias is apparent. SMAP captures well both low and high salinity values observed by Argo. In general, there are fewer low-salinity-value pairs for L2 products because the amount of collocated data for these products is less overall (Table 7).
Chiefly, SMAP reproduces sea-surface salinity in the eastern basin as measured during the I09N GO-SHIP cruise in May 2016 (intermonsoon period), including some mesoscale salinity features (Figure 5b). Correlation is similar between the three L3 products (0.82-0.86), with rmsd slightly reduced for RSS-70 km ( Table 6). Consistent with Argo, bias is positive for CAP/JPL and negative for RSS products, although not negligible (−0.17/−0.18) for GO-SHIP synoptic data. Enhanced CAP/JPL bias is apparent in Figure 5b, in which the CAP/JPL curve has a clear offset to in situ observations south of 12°N. However, in the interior of the Bay of Bengal (north of 15°N), CAP/JPL agrees better with in situ data than RSS products that underestimate salinity there. Biases between several SMAP products and TSG observations are distinct from those found with Argo and GO-SHIP. For TSG, all biases are positive (including RSS), and particularly high for both L3 (0.61) and L2 (0.87) CAP/JPL data (Table 8). Moreover, rmsd is consistently elevated (0.83-1.30) when contrasted with collocated Argo (0.35-0.68) and GO-SHIP (0.36-0.44) data. In general, correlation with TSG is lower for L3 products (0.74-0.78) but accentuated low for L2 CAP/JPL (0.46). A deeper look at individual differences showed that the cross-basin section around 5°N contributed the most to the low skill (Figure 6f). These TSG data were collected in 2016 by the R/V Marion Dufresne, and also present high positive differences for the RSS-70 km product (Figure 6e), although there is no apparent error in the TSG data. Whether the 5°N section is excluded and the statistics recalculated, the skills are much improved. For instance, the correlation for the L2 CAP/JPL product increases from 0.46 to 0.57, and the mean bias becomes negative.
As previously done for the Arabian Sea, statistics for collocated Argo datasets were computed into boxes of 5°× 5°to evaluate their spatial distribution in the Bay of Bengal. Correlation and rmsd also show a clear spatial pattern, with correlation increasing and rmsd decreasing in a southeastward direction across the basin from India to Sumatra/Indonesia (Figure 12). Except for the latter region, correlations are overall higher in the Bay of Bengal than those in the Arabian Sea, but rmsd also tend to be higher, especially in the basin interior (Figures 8 and 12 use the same color bar).  Color bars are the same as in Figure 8 for the Arabian Sea.
Seasonally, correlation and rmsd in the Bay of Bengal are lower in the wet June for all collocated L3-Argo datasets, as shown in Figure 10b. The pattern is similar for L2 data, but it is omitted here for brevity. As before, RSS-70 km has relatively higher skill than the less-smoothed CAP/JPL and RSS-40 km data. However, different from the Arabian Sea, RSS-40 km and CAP/JPL have similar skill levels all year round ( Figure 10).
SMAP also captures subseasonal variability relatively well when compared with in situ observations from the RAMA array and the WHOI buoy located in the Bay of Bengal interior at 18°N (Figure 13). For instance, all drops in salinity at 18°N are contemporarily observed by SMAP, although they are less intense in the L3 data. Correlation with this buoy is high (0.87-0.89), but because drops are less intense in the satellite, rmsd is also high (0.89-0.91), and skewness is accentuated ( Table 9). The rmsd for other buoys is much less (0.22-0.58); biases are mostly negative for RSS products and positive for CAP/JPL.  Table 9. Comparison of SSS observations from SMAP with daily averages from moored buoys (RAMA and WHOI) in the Bay of Bengal between 1 April 2015 (or buoy start time, which is recent) and 30 September 2019 (or end time for nonoperational buoys). Statistics are similar to Table 3. Values between brackets relative to subsurface RAMA observations, and outside brackets at 1-m depth. Linear correlation coefficients were significantly different from zero at 95% confidence (p-value < 0.001).

Red Sea
In situ observations for assessing SMAP in the Red Sea were collected by TSGs along the central Red Sea axis ( Figure 3) and six Argo floats, mostly in the western side of the basin (Figure 2). From these floats, four were flagged in the Argo gray list and may present a salting bias. However, this study did not find evidence of a strong bias. Because of uncertainty about the Argo observation quality, all data pairs with differences above two were not used to calculate Argo statistics shown in Table 10 (middle). For TSG data, all collocated pairs were used, although statistics discarding pairs with salinity differences above 2 (less than 2% of the total data) are also shown in Table 10.
While Argo data are relatively homogeneous in time, about half of the TSG data are from 2015, and no observations exist for 2018. March contains the most significant number of TSG measurements (about 17% of the total), but none was collected in April or July. Despite that, SMAP captures the high salinity of the Red Sea very well when compared with TSGs, independent of product or processing level ( Figure 14). The agreement is surprising because the Red Sea is narrow (maximum width of 355 km), and it would be expected that land contamination of the satellite footprint and RFI would be a severe issue to recover salinity there. For collocated L3-TSG data, correlation varies from 0.82 (RSS 40 km) to 0.94 (RSS 70 km), and rmsd was 0.41-0.78 (Table 10, upper). If we exclude the outliers (salinity differences > 2), correlation and rmsd improve to 0.89-0.95 and 0.39-0.60, respectively. Performance is similar for L2 products (although slightly worse). However, the signal-to-noise ratio is relatively high even for the L2 datasets (1.5-1.8). Biases follow the same pattern as already described for the Arabian Sea and the Bay of Bengal, with RSS products underestimating salinity by about 0.10-0.15, and CAP/JPL overestimating it by 0.08-0.23.
SMAP is also strongly correlated with Argo data, although coefficients are slightly lower (0.71-0.85) for L3 products (Table 10, middle). Similar to TSG, biases are positive for CAP/JPL and negative for RSS products, and rmsd is of similar strength. To obtain overall SMAP skill in the Red Sea, new sets were formed by merging collocated TSG (excluding outlier pairs) and Argo datasets. There were around 2000 pairs for each set (Table 10, lower). For brevity, only SMAP L3 is evaluated. Correlation is high for all three merged L3 (0.81-0.93) datasets, and rmsd varies from 0.38 (RSS-70 km) to 0.67 (RSS-40 km). Giving the SMAP standard deviation, the signal-to-noise ratio (1.6 to 2.3) indicates that the SMAP can capture the SSS signal in the Red Sea, and this ability is apparent in scatter plots of Figure 15a-c. Correlation tends to be lower (and rmsd high) in the extreme south (near the Gulf of Aden) and north (near the Gulf of Suez and Aqaba), as shown in Figure 15d; in conclusion, the SMAP skill in the Red Sea is promising.
As the SMAP skill level in the Red Sea is not worse than that in the open-ocean regions of the Arabian Sea or the Bay of Bengal, it is pertinent to ask if SMAP can capture seasonal variability of surface salinity in this extremely salty marginal sea. For evaluating that, monthly climatologies based on L3 SMAP products were computed for the first four years of the satellite's operation (September 2015 to September 2019). As a reference to the SSS seasonal cycle, the World Ocean Atlas (WOA, 2018 version) [62], published in July 2019, was used. WOA18 SSS fields had a grid resolution of 0.25°× 0.25°and are based on objective mapping of most available in situ observations to date.   Figure 16). Both CAP/JPL and RSS-70 km reproduce this spatial pattern (Figures 17 and 18), even with SMAP climatologies computed over a much shorter period than that of WOA18. However, salinity is overall lower in the RSS-70 km climatology (see Supplementary Figure S1), and overall higher in CAP/JPL ( Figure S2), which is consistent with the freshening/salting biases described in this work.
In WOA18, the inflow of the fresher Gulf of Aden surface waters seasonally spread northward, starting in December and reaching maximum latitude in May, around 18°-20°N. From May to September, this feature retracts to 14°N. Despite moderate SMAP spatial resolution, this seasonal cycle is also observed in SMAP. In both SMAP climatologies, the most northward latitude of the fresher Gulf of Aden surface waters is found around May. From May to September, a retraction to a southward position is observed.

Discussion
Several studies reported that SMAP is able to retrieve SSS with some confidence in coastal regions within 500-1000 km offshore in many places around the globe [11][12][13][14][15][16][17][18][19]. The present study adds another region to that list: the Red Sea. The Red Sea is an extremely salty environment, such as the Mediterranean Sea, and the issues to retrieve SSS in these two marginal seas are somehow similar [3,17]. However, the Red Sea is narrower on average, and land contamination would be expected to be a more severe issue there. Nonetheless, this work revealed a great SMAP signal-to-noise ratio in the Red Sea.
Tang et al. [3], using a previous version of the L3 CAP/JPL product, described correlations of 0.78 (TSG and Argo) and rmsd of 0.52/0.56 (TSG/Argo) over 18 months in the Mediterranean Sea.
The present study, the first to evaluate SMAP in the Red Sea, found correlations to be even higher (0.88/0.85, p-value < 0.001) and rmsd even lower (0.59/0.46) for L3 CAP/JPL in the Red Sea. Note that the SMAP skill level in the Red Sea is indeed slightly better for the L3 RSS-70 km product (Table 10).
Different from the Mediterranean Sea, bias is consistent for a product series in the Red Sea, such as RSS products underestimate in situ SSS, and CAP/JPL ones overestimate it (independent if Argo or TSG observations are used for statistical comparison). In the Mediterranean Sea, bias is positive for the TSG and negative for Argo [3], but that was for a previous SMAP version than the ones used here. Moreover, there is no outstanding offset in Figure 14, such as in the Levantine area of the Mediterranean Sea (Figure 3a of Tang et al. [17]).
Within the Red Sea, SMAP performance is reduced in the extreme north and south (Figure 15), areas with less collocated data, and more prone to RFI and land contamination. Tang et al. [3] also described spatial differences in SMAP performance in the Mediterranean Sea due to these factors.
Seasonally, there is evidence that SMAP captures the intrusion of the fresher, colder, and nutrient-rich Gulf of Aden Surface Water (GASW) in winter [48,63]. Sofianos and Johns [48] described GASW as a relatively fresh surface inflow with salinity around 36-36.5. This description is similar to what SMAP shows (Figures 17 and 18). SMAP SSS climatological maps also resemble the numerical simulations of Sofianos and Johns [54], with the eastern Red Sea slightly fresher than the western, especially north of 18°N (see also Figure S2). The SMAP SSS pattern would be consistent with the existence of a northward surface Eastern Boundary Current bringing warm and relatively fresh waters to the north, as described by Bower and Farrar [22]. However, the zonal difference in SMAP maps should be interpreted with caution given the moderate spatial resolution of the satellite, and possible RFI and land contamination. WOA18 does not show a clear zonal pattern in salinity, but its mapping scales are too wide. In conclusion, more work needs to be done to ensure that the SMAP zonal pattern is not an artifact due to RFI and land contamination.
The SMAP results in the Red Sea presented here are promising, particularly when they are contrasted with other marginal seas. For instance, Vazquez-Cuervo et al. [16] found correlations of 0.61-0.91 (except by one mooring in which correlation was around 0.3) and rmsd of 0.4-0.78 in the much wider Gulf of Mexico for the L3 SMAP products they analyzed. These numbers are the same order as those described here for the narrow Red Sea.
In the Gulf of Aden and Oman, SMAP performance is worse than that in the Red Sea, probably because RFI effects are more severe in the southward part of the Arabian Peninsula, although this study did not evaluate that. Despite this limitation, SMAP seems to capture signatures from mesoscale eddies in the Gulf of Aden. For instance, Figure 19 shows SSS and satellite-based sea-surface temperature (SST) fields for a random day in February 2019, overlaid with multisatellite altimetric geostrophic currents. Note that these datasets do not accurately represent the same period. A cyclonic (anticlockwise) eddy centered at 48°E and 12°N within the Gulf of Aden has a low salinity and temperature signature when compared with its surroundings. Mesoscale eddies are a crucial component of the Gulf of Aden dynamics, affecting Red Sea Overflow Water properties and the Gulf's biogeochemistry [23,29,63,64]. Other agreements also exist in maps between mesoscale features, SSS and SST. However, new investigations are required before it can be ruled that SMAP is capturing mesoscale eddies in the Gulf of Aden, but these initial results are promising. Within the Arabian Sea, there is a consistent improvement in SMAP statistical skills from the west, where the Gulfs of Aden and Oman are, to the east (Figure 8). Offshore the western boundary, all products show that SMAP captures SSS in the Arabian Sea with similar performance to the global evaluations [3,8], in which correlation in open water away from the coast is above 0.7 and rmsd was less than 0. 2 In the temporal domain, SMAP also reproduces the seasonal and subseasonal variability as measured by the RAMA array. Data from the RAMA array have also been previously used to validate SMAP [3], but at that time (April 2015-September 2016), there was no mooring outside the equatorial zone in the Arabian Sea. For the equatorial buoys in the western Indian Ocean, Tang et al. [3] found a high correlation (>0.7) and relatively low rmsd (≈0.25). Here, statistics of the newest L3 CAP/JPL version over a much longer period (four years) are similar, with a correlation of 0.76 (0°N; 67°E) and 0.84 (1.5°N; 67°E), and rmsd of 0.30 and 0.28, respectively. For the two moorings later deployed at 4°N and 8°N, correlations are even higher (Table 5).
In the Bay of Bengal, statistics between the RAMA array and the CAP/JPL product follow a similar pattern, as shown in Tang et al. [3] (their Figure 8), with correlation decreasing and rmsd increasing northward (Table 9). However, the spatial pattern from Argo does not show this northward worsening in SMAP retrieval ( Figure 12). When compared with Argo, SMAP statistics are indeed better northward. As a point of fact, SMAP SSS is highly correlated (0.87-0.89) with observations at the WHOI mooring located in the northern part of the bay (18°N), with SMAP in-phase and capturing the timing of the intense drops in salinity measured at the buoy, although without the same intensity (Figure 13a).
Fournier et al. [18] compared a previous version of L3 CAP/JPL SMAP and all in situ SSS observations in the Bay of Bengal available at the World Ocean Database (which include Argo floats) between April 2015 and December 2016. In their 1.5 years collocated dataset, the correlation was 0.83, rmsd 0.49, and there was a positive bias of 0.1. For the new version shown here and over four years, correlation is 0.95, rmsd is more or less the same (0.44), but the positive bias is 0.2. However, the in situ data used as ground truth in both works are not quite the same.

Conclusions
The present study assessed SMAP SSS retrievals in the North Indian Ocean, particularly in the Arabian Sea and the Red Sea. The wide range of salinity of the North Indian Ocean, with SSS of less than 30 in the Bay of Bengal to more than 40 in the Red Sea, was attractive for evaluating the performance of the new SMAP versions in relation to in situ SSS. For this task, this work put together almost all in situ SSS observations publicly available over the SMAP era, which included Argo floats, TSG, ship-based CTD, and time series from moored buoys.
Overall, SMAP reproduces SSS relatively well with a high signal-to-noise ratio, in both the Arabian Sea and the Bay of Bengal, with correlation increasing, and rmsd decreasing with spatial smoothing. Thus, CAP/JPL, with an effective spatial resolution of 60 km, tended to have a better performance than that of the RSS-40 km product, and slightly worse than that of the RSS-70 km. Similar improvement was observed when SMAP data is averaged over time, with the correlation being generally lower and rmsd higher for L2 products when contrasted with the respective L3 datasets.
Furthermore, SMAP captures seasonal and subseasonal SSS variability, and also captures exceptionally well the sharp drops in salinity in the northern Bay of Bengal measured by the WHOI mooring, although with less intensity. The present work showed that there is seasonal sensitivity in SMAP's skills, but the performance decrease is small and not equal in the western and eastern basin. In the Bay of Bengal, SMAP performance is lower in June while, in the Arabian Sea, it is around October. Interestingly, GO-SHIP hydrographic sections in the Arabian Sea and the Bay of Bengal give new evidence that SMAP can capture salinity features, which may be related to mesoscale eddies.
Agreement between the new SMAP products and Argo floats is better in the Bay of Bengal than that in the Arabian Sea, but this better agreement is not apparent when using TSG or RAMA data. Within the Arabian Sea, SMAP performance is much reduced on the western side for all products. This fact is particularly evident in the Gulfs of Aden and Oman. Skill reduction in these regions is possibly related to RFI contamination there, a subject to be further investigated. However, there is evidence that SMAP may be capturing SSS signatures due to mesoscale eddies in the Gulf of Aden, but this matter requires in-depth study.
On the other hand, SMAP retrievals in the narrow Red Sea are surprisingly good. SMAP statistics (with both TSG and Argo floats) are similar to the ones found in open-ocean water away from the coast. Results there encourage the development of a specially designed SMAP product in this marginal sea where the scarcity of SSS observations is historical, and not much is known about SSS variability [22,48]. One could imagine designing a product by using more advanced filtering techniques to remove spatial noise in L2 data, such as the ones based on singular spectrum analysis used by Menezes et al. [61], and an optimal interpolation scheme to map SMAP L2-filtered data into a regular grid instead of simple average binning.
A still-present limitation in both RSS and CAP/JPL products is the bias in the entire North Indian Ocean. However, because the bias is consistent and spatially homogeneous, as shown here, it should not affect studies about temporal SSS variability in the North Indian Ocean, which is the next step in this project. Issues still to be thoroughly investigated are the possible effects of RFI contamination, particularly in the Gulf of Oman, and precipitation in the Bay of Bengal during the summer monsoon. However, in the latter case, the in situ data currently available are not the most adequate since Argo floats do not capture possible near-surface stratification (0-5 m) that may occur in heavy rainfall.

Funding:
This research and open-access publication were funded by NASA grant number 80NSSC18K133 (NASA Ocean Salinity Science Team).