search

weather-gov / weather.gov

weather.gov 2.0
Other
326 stars 7 forks source link

Severe thunderstorm verbiage not showing in beta #1160

Open shadkeene opened 3 months ago

shadkeene commented 3 months ago

This is from a "high risk" day for Oklahoma--the highest risk for severe weather that is issued by the Storm Prediction Center. In other words, schools will close, people might die, and property will most likely be destroyed.

User story: I want to be able to understand the significance of thunderstorms that will be affecting my area, especially when these thunderstorms will likely pose a threat to life and property.

Severe thunderstorm wording shows in the point forecast on Weather.gov 1.0 image

Severe wording does not show up on the point forecast in beta.weather.gov image

Is the API not offering this wording? If so, it probably should. Additionally, this is a good use case for integration of center information to beta.weather.gov.

Additional detail below via another similar ticket: Forecasters can add lots of detail (manually or automated via forecastbuilder), like "thunderstorms" + large hail or "thunderstorms" plus damaging winds or "thunderstorms" plus heavy rain, and we'll want some of this detail to be included in the shortText that accompanies the hourly or AM/PM forecast. There are a several things we need to do:

Identify all potential enhanced wording options for thunderstorms. Prioritize what wording should be included in shortText and perhaps investigate current logic in forecast.weather.gov. Determine how many characters can/should be included in shortText (hourly too?) so it fits with beta.weather.gov design.

colinmurphy01 commented 3 months ago

Question for API team

shadkeene commented 3 months ago

verbiage in weather.gov 1.0 comes out of netcdf. api doesn't. need team to determine "if statements" (if 1 hour of thunderstorms during day, must have in day shorttext forecast)

colinmurphy01 commented 3 months ago

@shadkeene Can you confirm that the fix for this is on the API team?

shadkeene commented 2 months ago

@colinmurphy01 @coreypieper Confirmed with API team we need to include this as a requirement to be included in API. Will discuss in Slack. Once we make decision going forward, we can document here and close.

colinmurphy01 commented 2 months ago

let's confirm if there's a ticket for this in API's backlog then close

coreypieper commented 1 week ago

JIRA ticket: https://nco-jira.atlassian.net/browse/API-543