Skip to content
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

Populate frameNumber for S1 ARIA GUNW search results #197

Open
asjohnston-asf opened this issue May 30, 2023 · 2 comments
Open

Populate frameNumber for S1 ARIA GUNW search results #197

asjohnston-asf opened this issue May 30, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@asjohnston-asf
Copy link
Member

New S1 ARIA GUNW products published to CMR will soon include a FRAME_NUMBER additional attribute. @cmarshak would like this value populated in the frameNumber field for asf_search search results.

For more context, see ACCESS-Cloud-Based-InSAR/DockerizedTopsApp#136

To implement, I suspect we'd need to add the ASF_PLATFORM of Sentinel-1 Interferogram (BETA) the lists of platforms at:

@asjohnston-asf asjohnston-asf added the enhancement New feature or request label May 30, 2023
@asjohnston-asf
Copy link
Member Author

We'd also like to see support for searching these products by frame number, whether that be with asf_search.search's frame or asfFrame parameters.

@SpicyGarlicAlbacoreRoll
Copy link
Contributor

We won't be adding asfPlatform as a keyword, so the way to search for these products via FRAME_NUMBER would be to

  1. Specify the product type(s) with processingLevel (alternatively you can use a list of concept-ids with the collections keyword in v6.5.0)
  2. Set platform to Sentinel-1 (this will make asf-search to use FRAME_NUMBER instead of ESA_FRAME)

We will update the UMM parsing to use FRAME_NUMBER like other Sentinel products so that field will be set properly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants