-
Notifications
You must be signed in to change notification settings - Fork 3
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
CMR Metadata #136
Comments
Regarding
I believe any of these searches are already supported if you query CMR directly, in case that's valuable in the iterim. |
So would like to "de-duplicate" (i.e. find existing GUNWs uniquely in CMR using these attributes) - what would be the lift for getting |
@cmarshak most of this will be on the @glshort's side of the house -- @krkristenson-asf is going to connect with him and see how best to engage there. :-D |
Describe the bug
This is related to operations and coordinating between @asjohnston-asf, @cirrusasf, https://github.com/asfadmin/Discovery-asf_search, and JPL. This is related to #102 which now includes:
frame_id
,temporal_baseline_days
, andversion
.I submitted 5 products using the operational user which are currently set to be delivered to the UAT venue. All succeeded.
To view the relevant metadata:
Should return 5.
It appears the new metadata is going correctly to umm json as:
Returns:
However,
Returns
The questions are:
frameNumber
be different thanframe_id
? I thought we wanted them to be the same.frame_id
,temporal_baseline_days
, and a range ofstartTime
? Are we going to have to CMR orpython-cmr
?Thanks.
The text was updated successfully, but these errors were encountered: