Hi, I would like to know if the Version D of the SWOT level 2 lake single-pass vector Data Product is going to be available through Hydrocon API. When it can be expected to be available? Currently, in hydrocon API there is water level data only up until May 2025 (version C). Thanks!
Hydrocon API: https://podaac.github.io/hydrocron/intro.html
Version D transition: https://podaac.jpl.nasa.gov/announcements/2025-04-24-SWOT-Science-Data-Products-Transitioning-from-Version-C-to-Version-D-on-April-28-2025#:~:text=The%20first%20Version%20D%20products%20will%20be%20for,this%20transition%20from%20Version%20C%20to%20D%20products.
SWOT level 2 lake Single-Pass, Version D availability in Hydrocon
Re: SWOT level 2 lake Single-Pass, Version D availability in Hydrocon
I would also like to know the answer to this question. Thanks!
I've noticed that looking at USGS WISP and requesting data from Hydrocron (which should be the same), I can only view lake wse data up to April 29, 2025. However, SWOTViz appears to have data from April 29, 2025 to present day. But with large gaps prior to April 29.
Here is an example for Baker Lake:
I've noticed that looking at USGS WISP and requesting data from Hydrocron (which should be the same), I can only view lake wse data up to April 29, 2025. However, SWOTViz appears to have data from April 29, 2025 to present day. But with large gaps prior to April 29.
Here is an example for Baker Lake:
- Attachments
-
- wse from Hydrocron, USGS WISP, and SWOTViz
-
oceancat18
- Posts: 1
- Joined: Thu Dec 14, 2023 12:05 pm America/New_York
Re: SWOT level 2 lake Single-Pass, Version D availability in Hydrocon
Hi, SWOT version D of the data is available through Hydrocron API, but it is not yet the default (default being vC). We are waiting for the reprocessing of version D to complete (expected April 2026), at which point we will update the Hydrocron API to default to vD.
To use vD in the API call, please see https://podaac.github.io/hydrocron/user-guide/versioning.html
To specify which collection you want to retrieve data from, use the new collection_name: string, required: no request parameter. Here is an example command, with the key addition being: collection_name=SWOT_L2_HR_LakeSP_D (for the lakeSP product). Here is a full API call example, with riverSP vD data: https://soto.podaac.earthdatacloud.nasa.gov/hydrocron/v1/timeseries?feature=Reach&feature_id=78340600051&output=csv&collection_name=SWOT_L2_HR_RiverSP_D&start_time=2024-01-01T00:00:00Z&end_time=2026-01-01T00:00:00Z&fields=reach_id,time_str,wse,slope
Dashboards like USGS's WISP and CUAHSI's SWOTviz are likely using the default vC because right now both vC and vD are available but vD is still back-filling from the reprocessing campaign. I expect once the reprocessing is complete, and vD record is available, tools like Hydrocron API and dashboards that use it on their backend will update to provide vD data (I don't want to speak for these dashboard owners, but vD will be available to them via Hydrocron API so they will be able to more easily provide that via the dashboards). Thanks for your patience.
To use vD in the API call, please see https://podaac.github.io/hydrocron/user-guide/versioning.html
To specify which collection you want to retrieve data from, use the new collection_name: string, required: no request parameter. Here is an example command, with the key addition being: collection_name=SWOT_L2_HR_LakeSP_D (for the lakeSP product). Here is a full API call example, with riverSP vD data: https://soto.podaac.earthdatacloud.nasa.gov/hydrocron/v1/timeseries?feature=Reach&feature_id=78340600051&output=csv&collection_name=SWOT_L2_HR_RiverSP_D&start_time=2024-01-01T00:00:00Z&end_time=2026-01-01T00:00:00Z&fields=reach_id,time_str,wse,slope
Dashboards like USGS's WISP and CUAHSI's SWOTviz are likely using the default vC because right now both vC and vD are available but vD is still back-filling from the reprocessing campaign. I expect once the reprocessing is complete, and vD record is available, tools like Hydrocron API and dashboards that use it on their backend will update to provide vD data (I don't want to speak for these dashboard owners, but vD will be available to them via Hydrocron API so they will be able to more easily provide that via the dashboards). Thanks for your patience.