From 4cc8d1dc668b7d8fcfae0787c6599b4e954ce267 Mon Sep 17 00:00:00 2001 From: Miles Curry <2590700+MiCurry@users.noreply.github.com> Date: Mon, 15 Dec 2025 17:41:04 -0700 Subject: [PATCH] Fixed Unresolved GTS link in IODA introduction documentation The link to GTS in the Ioda introduction page links to a 404. It appears that the WMO public page was relaunched in Nov 2023 and thus some pages are no longer, or are hosted elsewhere. --- docs/inside/jedi-components/ioda/introduction.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/inside/jedi-components/ioda/introduction.rst b/docs/inside/jedi-components/ioda/introduction.rst index 562b6ed0..cb2d6c20 100644 --- a/docs/inside/jedi-components/ioda/introduction.rst +++ b/docs/inside/jedi-components/ioda/introduction.rst @@ -61,7 +61,7 @@ OOPS collects H(x) from UFO and y from IODA to form a departure, y - H(x), that Data Providers and Output Diagnostics ------------------------------------- -The Data Providers, :numref:`ioda-hlev-dflow`, (e.g., `Global Telecommunication System (GTS) `_ store observation data in a wide variety of formats. +The Data Providers, :numref:`ioda-hlev-dflow`, (e.g., `Global Telecommunication System (GTS) `_ store observation data in a wide variety of formats. Because of this, the general idea in IODA is to convert these formats to a common format, the IODA data model, to facilitate access by IODA. This way, the different manners in which JEDI may want to select, query, or distribute the observation data can be done through one API to the IODA data model, as opposed to many API's to the various data provider formats. After the DA run completes, it is often desired to analyze different aspects of that run.