stac-extensions / stac-extensions/vpp
Proposed descriptions for the fields
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Proposed improvement for the field names:
- season ==> growing-season
- sub_parameter ==> parameter / variable or product
Descriptions:
<style> </style>| Field Name | Type | Description |
|---|---|---|
| vpp:season | string | Growing-season identifier for the Vegetation Phenology and Productivity (VPP) parameters. Allowed values are s1 and s2. Seasons are ordered chronologically by the day of maximum seasonal Plant Phenology Index value (MAXD): s1 is the earlier season and s2 the later season. They are not ordered by size or productivity, so the main growing season may be s2. A maximum of two seasons is provided for each year; when more than two are detected, the two seasons with the largest seasonal peaks are retained and then ordered chronologically. A season is assigned to the year containing its maximum value, even when it crosses a calendar-year boundary. |
| vpp:sub_parameter | string | Acronym identifying the Vegetation Phenology and Productivity (VPP) parameters represented by the asset. Allowed values are AMPL, EOSD, EOSV, LENGTH, LSLOPE, MAXD, MAXV, MINV, QFLAG, RSLOPE, SOSD, SOSV, SPROD, and TPROD. |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the extension documentation or schema definitions for vpp:season and vpp:sub_parameter, since no file is named in the issue. Review the proposed field names and descriptions, then update the relevant definitions so they match; done means the published field documentation reflects the requested terminology and allowed values.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100