Instructor Notes

Example of a note

Introduction

Instructor Note

Examples of barriers to reuse datasets might include:

  • Missing metadata

  • Non-standard units or unclear variable names

  • File formats you could not easily open

  • Access restrictions or unstable URLs

  • Large data volumes and inefficient download workflows

  • Difficulty aligning datasets from multiple institutions

  • Lack of documentation on coordinate systems or time conventions

  • Inconsistent versions or unclear provenance

This discussion sets up the motivation for the rest of the workshop: practical, hands-on methods to make interoperable data using real tools such as NetCDF, CF conventions, and OPeNDAP.


Instructor Note

This exercise is for discussion in Plenum nad it can serves as a good link to the next section


Structural interoperability

To link it to semantic interoperability for next section

If you want to deepen discussion, ask participants:

  • Which of these expectations would still work if metadata were incomplete?
  • Which expectations primarily benefit machines rather than humans?

This naturally leads into the next section on NetCDF structure and the boundary between structural and semantic interoperability.


Semantic interoperability

Technical interoperability: Streaming protocols

Instructor Note

Most of the cases , a warning is prompted. This warning is normal when using pydap with a THREDDS OPeNDAP server. It is not an error and your dataset should still load correctly. The warning simply means that PyDAP could not detect whether the server supports DAP2 or DAP4, so it defaults to DAP2, which is the older protocol.

The OPeNDAP protocol has two main versions:

DAP2 – legacy but widely supported (many THREDDS servers still use it) DAP4 – newer, more efficient protocol

PyDAP tries to infer the protocol automatically. If it cannot, it falls back to DAP2, which triggers the warning.The server (opendap.4tu.nl) is a THREDDS server, and these typically expose DAP2 endpoints, so this behavior is expected.


Instructor Note

You can go back to the exercise of the Episode of structural interoperability : Identify the structural elements in a NetCDF file


Technical interoperability: API

Instructor Note

This section could be shown as a live demo or a step-by-step walkthrough, depending on the audience and format of the lesson. The key is to demonstrate how to interact with the API using command-line tools like curl, and to explain the underlying concepts of RESTful APIs as you go through the examples.


Instructor Note

Open this link : https://data.4tu.nl/v2/articles/03c249d6-674c-47cf-918f-1ef9bdafe749/files in the browser to check the uuid of a file to download (the readme, the last file) for the following step.


Cloud-Native Layouts

Instructor Note

This session can be delivered as a live-coding demonstration.
Walk through each step, explain the concepts, and let learners follow along.


Instructor Note

Common issues when working with Kerchunk:

  • Use the /fileServer/ endpoint (not /dodsC/)
  • NetCDF3 files require NetCDF3ToZarr
  • If you see async errors, set "asynchronous": True
  • Prefer engine="kerchunk" over "reference://" for simplicity

Interoperable Infrastructure in the AI Era