Consider the usage of DataTree options like inheritance of dimension (suggested by Owen Littlejohn).
We need an analysis of the costs.
Context:
We are looking to assist users who are attempting to download RAD and RADT data ie https://search.earthdata.nasa.gov/search/granules?p=C3868234842-LARC_CLOUD!C3868234842-LA[…]7.483434700000004&long=-97.471834&zoom=4.390622813521526
because the files are very large. We have been looking at using the L2SS with these L1 data but have not been successful. I did look through previous conversations about similar attempts, but was wondering if you would be willing to tag up for a discussion on this....
L2SS does not properly subset TEMPO_RAD/TEMPO_RADT files when bounding box subsetting is used. The TEMPO_RAD/RADT files contain 2 bands/sets of data, each with their own latitude/longitude data. The bands do not contain separate time data, so L2SS uses the global time data for processing the lat/lon bands, however the current subsetting logic doesn’t work with the 2 bands and time data having separate data paths. We would like to meet to discuss what we’ve found and see if we can work toward a solution that will support subsetting the TEMPO_RAD/TEMPO_RADT data.
Consider the usage of DataTree options like inheritance of dimension (suggested by Owen Littlejohn).
We need an analysis of the costs.
Context:
We are looking to assist users who are attempting to download RAD and RADT data ie https://search.earthdata.nasa.gov/search/granules?p=C3868234842-LARC_CLOUD!C3868234842-LA[…]7.483434700000004&long=-97.471834&zoom=4.390622813521526
because the files are very large. We have been looking at using the L2SS with these L1 data but have not been successful. I did look through previous conversations about similar attempts, but was wondering if you would be willing to tag up for a discussion on this....
L2SS does not properly subset TEMPO_RAD/TEMPO_RADT files when bounding box subsetting is used. The TEMPO_RAD/RADT files contain 2 bands/sets of data, each with their own latitude/longitude data. The bands do not contain separate time data, so L2SS uses the global time data for processing the lat/lon bands, however the current subsetting logic doesn’t work with the 2 bands and time data having separate data paths. We would like to meet to discuss what we’ve found and see if we can work toward a solution that will support subsetting the TEMPO_RAD/TEMPO_RADT data.