add the merge burst insar products section in the burst_insar_product_guide.md #413
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Mostly small stuff but a couple of areas where I was confused as to where the ordering of things was.
Mainly, I wanted to know
- How you wanted to format the 'Options'. Are they their own subsections
- What does the first 'Options' section pertain to? Can you link more documentation there?
- It generally seems that code values and snippets should be indicated as such with markdown, so I went and suggested those changes. I don't know how necessary that is
cirrusasf
commented
Feb 9, 2024
| The product packaging of merged burst InSAR products follows the same conventions outlined in [Product Packaging](#product-packaging "Jump to the Product Packaging section of this document") section above with two exceptions. First, the four range-doppler images are not included since the products have already been merged. Second, the product is modified slightly; the Burst ID is swapped for the zero-padded relative orbit number, and the swath number are removed. The resulting format is: | ||
| ``` | ||
| S1_rrr__yyymmdd_yyymmdd_pp_INTn_uuuu | ||
| ``` |
There was a problem hiding this comment.
Do we need to list the file names in the merge product as a table and also give the example filenames just like in Table 2 ?
There was a problem hiding this comment.
@cirrusasf I can see the logic in this, but I don't think we should. Adding a second table would add a ton of duplication to the product guide and I think we're better off just referencing the product packaging section like we've done here.
forrestfwilliams
approved these changes
Feb 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.