Reported by @noaaroland on 11 May 2010 16:33 UTC
From Steve H. email:
The next step is to think about how to apply these techniques to the UAF datasets that have this same character. One approach to this would be for you to configure one of the UAF datasets on your private server, applying all of the techniques that you've just learned, and then work with Kevin to transfer the configuration over to the UAF server (http://ferret.pmel.noaa.gov/geoide/geoIDECleanCatalog.html).
An important question to be thinking about is how to automate the configuration steps for the sigma-regridding by F-TDS and the "shadow" dataset that is on a depth axis. I suggest that for now we stick with the shadow dataset approach -- having LAS show both the native dataset as-is on sigma coordinates and the shadow dataset in meters of depth. I don't think this is the right strategy for the long term, though. The ideal would be to offer an LAS constraint that invoked the regridding. The new challenge to doing that will be that when the user clicks the constraint the vertical axis widget needs to be replaced. Note that this is the very same requirement that we want to address for time axes such as "january-only" and "seasonal-averaged".
This is set in the UI components, but it might have effects every where from the UI to F-TDS to the product server to addXML.
Reported by @noaaroland on 11 May 2010 16:33 UTC From Steve H. email:
The next step is to think about how to apply these techniques to the UAF datasets that have this same character. One approach to this would be for you to configure one of the UAF datasets on your private server, applying all of the techniques that you've just learned, and then work with Kevin to transfer the configuration over to the UAF server (http://ferret.pmel.noaa.gov/geoide/geoIDECleanCatalog.html).
A good candidate would be the USGS model at http://ferret.pmel.noaa.gov/geoide/geoIDECleanCatalogs/ioos_neracoos_usgs_coawst_bst.html?dataset=coawst_2_best_time_series That dataset does have "coordinates" attributes. It looks like variables s_rho and s_w are the sigma coordinates (staggered grid in the horizontal, hence two vertical axes).
An important question to be thinking about is how to automate the configuration steps for the sigma-regridding by F-TDS and the "shadow" dataset that is on a depth axis. I suggest that for now we stick with the shadow dataset approach -- having LAS show both the native dataset as-is on sigma coordinates and the shadow dataset in meters of depth. I don't think this is the right strategy for the long term, though. The ideal would be to offer an LAS constraint that invoked the regridding. The new challenge to doing that will be that when the user clicks the constraint the vertical axis widget needs to be replaced. Note that this is the very same requirement that we want to address for time axes such as "january-only" and "seasonal-averaged".
This is set in the UI components, but it might have effects every where from the UI to F-TDS to the product server to addXML.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/las/ticket/790