Vidensdatabase

A custom trigger is designed to be a way for clients to be notified of an upcoming weather condition or conditions that are pertinent to their operations without having to parse the hourly forecast manually twice a day for each of their forecasting locations. The clients can do this by setting an individual weather condition or using multiple weather conditions together and assigning an operator and a value to that condition.

For example, if high winds are an issue for tree trimming or fertilization, a custom trigger could be made using either wind speed or wind gust, let's say greater than or equal to (>=) 25 mph. Since tree trimming and fertilizing are typically done in warm weather, maybe you set the months to April through October and adjust the hours to 7 AM through 7 PM, since you likely won't be doing either at night. When it comes to fertilizing, maybe temperature or relative humidity plays a role, so you might want to add those conditions to the custom trigger before hitting submit.

Or maybe irrigation is part of your operations and you need to know when temperatures will be dropping below freezing in the fall for proper winterization. You could create a custom trigger where the temperature is less than or equal to (<=) 32° and set the months to September through November with hours being just fine at 12 AM to 11 PM, since it doesn't matter what time of day the temperatures will be dropping below 32°.

Those are just two examples of ways custom triggers can be used because while the Threat Intelligence Alerts are great for precipitation-related events, we realized there are many precipitation-free weather-related issues your operations deal with. Custom triggers were designed to streamline the process of combing over all the hourly forecast information for each of your forecasting locations to find what you're looking for to better plan your operations.