docs: Coverage API filtering (radio config, dates, power, antenna) - #14
Merged
Conversation
…omponent, radio_configs field
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documents the f_* filters that now actually apply on regional and group Coverage keys (MeshMapper_Server dev 29b1098): a Filtering section with the param table (f_radio_freq, f_freq/f_bw/f_sf/f_cr, f_days, f_dstart/f_dend, f_power, f_extant), the new radio_configs top level field and the filters echo, the not-cached note, and the three new 400 error codes. Global sections stay as they are.