Add CORDEX-CMIP6 data servers registry with automated HTML generation

[Copilot]

Collects servers hosting CORDEX-CMIP6 data (including non-ESGF sources) as an interim solution while ESGF-NG publication is pending. Community-editable YAML file automatically generates searchable HTML table via GitHub Actions.

Implementation

• CORDEX_CMIP6_data_servers.yaml: Machine-readable registry with fields: domain, institution, url, availability, comment
• CORDEX_CMIP6_data_servers.py: Generates interactive DataTables HTML from YAML (proper error handling, cross-platform temp files)
• Build pipeline: Integrated into Makefile and GitHub Actions workflow triggers on YAML changes
• Documentation: Added "Data Access" section to docs/index.md, updated README with contribution instructions

Usage

Contributors add servers by editing the YAML file:

servers:
  - domain: AUS-15
    institution: NCI Australia
    url: https://thredds.nci.org.au/thredds/catalog/catalogs/ig45/catalog.html
    availability: THREDDS
    comment: Australian CORDEX-CMIP6 data via THREDDS Data Server

Automated workflow regenerates the HTML table on merge.

Screenshot

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Collect existing servers with CORDEX-CMIP6 data</issue_title>
<issue_description>The idea is to collect existing servers with CORDEX-CMIP6 data, even if they are not on ESGF and as an interim solution while ESGF-NG publication is a reality. Some of these already appear in the TF report, such as the AUS one, but we could collect all of them. The question is where. Several options:

• in a discussion in github, so additional entries can be suggested
• in a cordex.org static page (harder to update and currently unmanned until the new IPOC takes over)
• in a dedicated website (e.g. under the simulation-status pages)
• as a table in the TF report (too hidden)
• ...

@dompaq could you add here the link to the NA-CORDEX server you mentioned?</issue_description>

Comments on the Issue (you are @copilot in this section)

@jesusff let's start with a table in markdown under the simulation-status repo. This could be built from a yaml file collecting the information (domain, url, availability, comment) using a github Action

• Fixes Collect existing servers with CORDEX-CMIP6 data #113

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.