In these CMEMs ZARR there's evidence of the dummy "crs" var used via "grid_mapping" in NetCDF, but there's no such var.
https://data.marine.copernicus.eu/product/SEALEVEL_GLO_PHY_L4_MY_008_047/description
curl -s "https://s3.waw3-1.cloudferro.com/mdl-arco-time-045/arco/SEALEVEL_GLO_PHY_L4_MY_008_047/cmems_obs-sl_glo_phy-ssh_my_allsat-demo-l4-duacs-0.125deg_P1D-i_202511/timeChunked.zarr/.zmetadata" | grep -i "grid_mapping\|crs\|spatial_ref"
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
"grid_mapping": "crs",
curl -s "https://s3.waw3-1.cloudferro.com/mdl-arco-time-045/arco/SEALEVEL_GLO_PHY_L4_MY_008_047/cmems_obs-sl_glo_phy-ssh_my_allsat-demo-l4-duacs-0.125deg_P1D-i_202511/timeChunked.zarr/.zmetadata" | grep -i "\\.zarray"
"adt/.zarray": {
"err_sla/.zarray": {
"err_ugosa/.zarray": {
"err_vgosa/.zarray": {
"flag_ice/.zarray": {
"lat_bnds/.zarray": {
"latitude/.zarray": {
"lon_bnds/.zarray": {
"longitude/.zarray": {
"nv/.zarray": {
"sla/.zarray": {
"time/.zarray": {
"tpa_correction/.zarray": {
"ugos/.zarray": {
"ugosa/.zarray": {
"vgos/.zarray": {
"vgosa/.zarray": {
it's funny because I very clearly remember earlier products by AVISO that shipped in transposed Mercator grid but with rectilinear long lat arrays (ewk), there was a brief happy time when CF provided crs and this stuff just worked from the NetCDFs.
here's more on the context around the grid_mapping attributes