You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’d like to request that the dwc:reproductiveCondition field be included in the API search results, even if not as a filterable parameter. This field contains valuable phenology information, such as flowering and fruiting conditions, which is crucial for visualizing lifecycle stages of plants in our project.
Our team is working on a project in Uruguay where we display the months when various plant species are flowering or fruiting. It would be incredibly helpful if reproductiveCondition data, with values like "in bloom" or "fruit-bearing," were simply included in the API output, as this would allow us to use it directly in our visualizations. Examples of values in the documentation include:
non-reproductive
pregnant
in bloom
fruit-bearing
While this field is available in the downloaded occurrence and verbatim files, it doesn’t appear in the API search results, limiting our ability to access it in real-time applications. Including it in the API output would provide a more complete and useful dataset for phenological studies.
Thank you for considering this addition!
The text was updated successfully, but these errors were encountered:
I’d like to request that the dwc:reproductiveCondition field be included in the API search results, even if not as a filterable parameter. This field contains valuable phenology information, such as flowering and fruiting conditions, which is crucial for visualizing lifecycle stages of plants in our project.
Our team is working on a project in Uruguay where we display the months when various plant species are flowering or fruiting. It would be incredibly helpful if reproductiveCondition data, with values like "in bloom" or "fruit-bearing," were simply included in the API output, as this would allow us to use it directly in our visualizations. Examples of values in the documentation include:
While this field is available in the downloaded occurrence and verbatim files, it doesn’t appear in the API search results, limiting our ability to access it in real-time applications. Including it in the API output would provide a more complete and useful dataset for phenological studies.
Thank you for considering this addition!
The text was updated successfully, but these errors were encountered: