Welcome, Guest
Username: Password: Remember me

TOPIC: mapping Telemac3D variables into CF compliant variables

mapping Telemac3D variables into CF compliant variables 2 years 11 months ago #39430

  • JulienM
  • JulienM's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 6
Hi there,
I have done a bit of work previously on making Telemac3D files accessible to Opendrift using the Telemac3D scripts.
I know would like to port my results into a cloud environment. The best thing is to make xarray datasets into zarr at the moment.
However, to do so it is preferable to make your data CF-Compliant.
Is there anyone that mapped all the potential Telemac variables and tried to map them against their CF equivalent?
I have done it on the case by case basis but not in a systemic way. I feel that could be interesting for a number of project to exploit Telemac results in a cloud environment.
Cheers

Here an example of the mapping with python dictionaries
Vars_OD = {
                'VELOCITY U      ': 'x_sea_water_velocity',
                'VELOCITY V      ': 'y_sea_water_velocity',
                'VELOCITY W      ': 'upward_sea_water_velocity',
                'TURBULENT ENERGY': 'turbulent_kinetic_energy',
                'TEMPERATURE     ': 'sea_water_temperature',
                'SALINITY        ': 'sea_water_salinity',
                'NUZ FOR VELOCITY': 'ocean_vertical_diffusivity',
                'NUX FOR VELOCITY': 'horizontal_diffusivity',
                'ELEVATION Z     ': 'sea_floor_depth_below_sea_level',
            }

            No_OD_equiv = {
                'x_wind', 'y_wind', 'wind_speed',
                'sea_floor_depth_below_sea_level', 'wind_from_direction',
                'sea_ice_x_velocity', 'sea_ice_y_velocity',
                'sea_surface_wave_significant_height',
                'sea_surface_wave_stokes_drift_x_velocity',
                'sea_surface_wave_stokes_drift_y_velocity',
                'sea_surface_wave_period_at_variance_spectral_density_maximum',
                'sea_surface_wave_mean_period_from_variance_spectral_density_second_frequency_moment',
                'sea_ice_area_fraction', 'surface_downward_x_stress',
                'surface_downward_y_stress', 'turbulent_generic_length_scale'
            }
            No_Telemac_equiv = {
                'NUY FOR VELOCITY',
                'DISSIPATION     ',
            }
The administrator has disabled public write access.

mapping Telemac3D variables into CF compliant variables 2 years 11 months ago #39473

  • JulienM
  • JulienM's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 6
I have done that, support would be much appreciated so that Telemac results can be optimised and used on multiple platforms
github.com/Boorhin/Telemac3D_to_xarray
The administrator has disabled public write access.
Moderators: borisb

The open TELEMAC-MASCARET template for Joomla!2.5, the HTML 4 version.