-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create controlled ATL03 HDF5 test file #27
Comments
@andypbarrett to provide key variables, including quality flags, needed for higher level products. Utilize ATBD and earthdata-varinfo to inform what information is needed for a controlled ATL03 HDF5 test file. |
I've looked at ATL07 and ATL06. Below are a list of candidate variables. I've left out geophysical corrections that are already included in h_ph. Paths are from ATL03 data dictionary. Variable lists are from table 2 in ATL07 ATBD and table 5-1 in ATL06 ATBD. 11 out of the 13 variables in /gtx/heights are used by one or both of ATL07 and ATL06, and 12 out of 37 variables from /gtx/geolocation are used.
|
We determined that we will grab all variables within the /heights groups for each beam group. A new task was added to actually perform the subsetting using |
This may still be helpful to determine core variables needed to create a derived product if we were to reformat to something like geoparquet. |
To better control these performance tests, we ought to create stripped down ATL03 files based on information from #23 and #26. The goal is to better control for the complexities in the native data. We can then reduce the noise as we investigate switches in the HDF5 library to increase performance in the cloud.
Tasks
The text was updated successfully, but these errors were encountered: