Include subsetting for variables in top group without a slash
Closed this issue · 5 comments
Earthdata search doesn't show variables that are in the top level of a file with grouped data. This is because there is a leading slash in front of these variables and won't show them. Fix is to make the code more flexible to variables without the leading
(https://search.uat.earthdata.nasa.gov/projects?p=C1232998567-GES_DISC!C1232998567-GES_DISC&pg[1][a]=1242124279!GES_DISC&pg[1][v]=t&pg[1][gsk]=-start_date&pg[1][m]=harmony0&pg[1][ets]=t&q=SNDR&tl=1668529855!3!!)
I don't think this is an issue with l2ss-py. If I recall correctly Harmony takes care of normalizing the variable names passed to backend services. Will need to confirm with Harmony team first though.
I don't think this is an issue with l2ss-py. If I recall correctly Harmony takes care of normalizing the variable names passed to backend services. Will need to confirm with Harmony team first though.
But the variable names in UMM-VAR need to be altered, won't that mean l2ss-py will need to accommodate that?
I don't think so. If I recall correctly, Harmony will always pass variable names to the backend with a leading slash. I remember a long discussion happening about this leading-slash convention but the outcome of the conversation is a bit fuzzy.
Looks like I was mistaken and that Harmony just sends whatever is in UMM-V for variable name.
However, I still don't know what the ask is on the l2ss-py side of things?
To be flexible with a given variable in the root group without a front slash. Variable subsets for SNDR should be able to work for "/surf_temp" and "surf_temp"