Document seasonal FBFM40 in the creating-grids guide - #214
Merged
Conversation
Add a "Seasonal fuels" how-to section covering the new season argument (ES/SP/SU/FA with a seasonal version) and note that represented_year is the projected season year. Also correct the annual-version example, which listed "2025" as a pinnable vintage -- 2025 is seasonal-only and is rejected without a season.
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.
Summary
Follow-up to #213: documents the
seasonargument for seasonal FBFM40 in the SDK docs.docs/v2/guides/creating-grids.md— how to request LANDFIRE Seasonal Fuels (ES/SP/SU/FA) with a seasonalversion("2025"), thatrepresented_yearis the projected season year (2025 + SP → 2026), and a coverage caveat linking to the LANDFIRE Seasonal Fuels page."2025"as a pinnable vintage. 2025 is seasonal-only and the API rejects it without aseason, so the annual example now pins an annual vintage ("2024") only.Docs-only change. The
represented_year == 2026output is verified against the live API by the test added in #213.