Difference between revisions of "$twcweather.alerts"

From webCoRE Wiki - Web-enabled Community's own Rule Engine
Jump to: navigation, search
m
m
Line 356: Line 356:
 
=== Location ===
 
=== Location ===
  
−
This seems to be the only helpful location, that changes based on the location of the alert.
+
These seem to be the only helpful locations, that changes based on the location of the alert.
  
 
{| class="mw-datatable"
 
{| class="mw-datatable"
Line 362: Line 362:
 
! Expression
 
! Expression
 
! Sample value
 
! Sample value
 +
|-
 +
| <code>$twcweather.alerts.areaId</code>
 +
| <code>"NYZ179", "ANZ335"</code>
 
|-
 
|-
 
| <code>$twcweather.alerts.areaName</code>
 
| <code>$twcweather.alerts.areaName</code>
−
| <code>Southern Nassau County</code>
+
| <code>"Southern Nassau County", "Long Island Sound West of New Haven CT/Port Jefferson NY"</code>
 
|-
 
|-
 
|}
 
|}
Line 407: Line 410:
 
| <code>adminDistrictCode</code>
 
| <code>adminDistrictCode</code>
 
| <code>NY</code>
 
| <code>NY</code>
−
|-
 
−
| <code>areaId</code>
 
−
| <code>NYZ179</code>
 
 
|-
 
|-
 
| <code>countryCode</code>
 
| <code>countryCode</code>

Revision as of 23:57, 4 August 2019

This page is currently under construction. I would wait a day or two before using the data found below.

As of Aug 4th, I have been unable to locate an official document for the weather alerts, so we have been gathering data the old fashioned way, and combining our findings on this page.

If you get a unique alert in your location, please contribute your observations to this thread.

Introduction

Everything on this page focuses on $twcweather.alerts. This query will usually return [] unless there is an alert for your location. When that happens, up to 62 different dataPoints may be returned. Every one of them begins with $twcweather.alerts followed by a period, and the dataPoint listed below. (such as: $twcweather.alerts.eventDescription) There are a few tables below that got a bit crowded, so some of them will not mention $twcweather.alerts, but it is important to remember that every single command on this page begins with $twcweather.alerts.

Unfortunately, a weather alert cannot be used as a trigger. To to get alerts for your area, you can program a piston to periodically make a query. (mine is set to run every 15 minutes, but any other trigger can work as well)

Many of the Alert dataPoints go hand in hand with each other, so the format on this page is a bit different than the TWC_Weather page. For the most part, the "unknown" dataPoints are listed first, so they get the most exposure. These will be followed by the dataPoints that are likely the most useful. The final category will be dataPoints that rarely change.

Needs More Information Gathered

We really need more data responses for this section. Please add any unique observations to this thread.

Unknown dataPoints

Expression Sample value Notes
$twcweather.alerts.areaTypeCode "Z", "C" Returns "Z" 80% of the time
$twcweather.alerts.categories.category "Met" Metropolis??
$twcweather.alerts.categories.categoryCode "1"  ??
$twcweather.alerts.significance "A", "S", "W", "Y"  ??
$twcweather.alerts.disclaimer null  ??
$twcweather.alerts.eventTrackingNumber 0003  ??

$twcweather.alerts.flood

The dataPoint "flood" is usually null, but when there is an alert for possible flooding, then all of these dataPoints will appear:

Expression Sample value Notes
$twcweather.alerts.flood.floodCrestTimeLocal null  ??
$twcweather.alerts.flood.floodCrestTimeLocalTimeZone null  ??
$twcweather.alerts.flood.floodEndTimeLocal null  ??
$twcweather.alerts.flood.floodEndTimeLocalTimeZone null  ??
$twcweather.alerts.flood.floodImmediateCause "Excessive Rainfall" Needs more examples
$twcweather.alerts.flood.floodImmediateCauseCode "ER" Needs more examples
$twcweather.alerts.flood.floodLocationId 00000, AFBI2  ??
$twcweather.alerts.flood.floodLocationName "N/A", "White River at Apache Tailwater"  ??
$twcweather.alerts.flood.floodRecordStatus "N/A"  ??
$twcweather.alerts.flood.floodRecordStatusCode "OO"  ??
$twcweather.alerts.flood.floodSeverity "None"  ??
$twcweather.alerts.flood.floodSeverityCode "N"  ??
$twcweather.alerts.flood.floodStartTimeLocal null  ??
$twcweather.alerts.flood.floodStartTimeLocalTimeZone null  ??

Important & Useful

Alerts

It appears that these 5 dataPoints are connected, so this table is shown a bit differently than the above tables. To conserve space, the first three columns are marked with numbers that match this:

  1. phenomena
  2. productIdentifier
  3. eventTrackingNumber
1 2 3 eventDescription headlineText
CF CFW 0024 Coastal Flood Statement Coastal Flood Statement from FRI 8:00 PM EDT until SAT 12:00 AM EDT
FA FLS 0156 Flood Advisory Flood Advisory from THU 5:21 PM EDT until THU 7:15 PM EDT
FF FFA 1 Flash Flood Watch Flash Flood Watch until WED 9:00 PM AST
FG NPW 0003 Dense Fog Advisory Dense Fog Advisory from SAT 5:40 AM EDT until SAT 10:00 AM EDT
FL FLS 0065 River Flood Advisory River Flood Advisory until SUN 7:00 AM CDT
HT NPW 0003 Heat Advisory Heat Advisory from TUE 10:00 AM EDT until TUE 9:00 PM EDT
SV SVR 0106 Severe Thunderstorm Warning Severe Thunderstorm Warning from WED 6:14 PM CDT until WED 6:45 PM CDT
SV WCN 0547 Severe Thunderstorm Watch Severe Thunderstorm Watch until WED 9:00 PM EDT
TAW AWW 0000 Airport Weather Warning Airport Weather Warning until FRI 2:15 PM CDT
TSG SPS 0000 Significant Weather Advisory Significant Weather Advisory until FRI 4:15 PM EDT

Descriptions

It appears that these dataPoints are paired up, so this table is shown a bit differently than the above tables.

certaintyCode certainty Notes
1 Observed
2 Likely
3 Possible
4? ??  ??
5 Unknown
messageTypeCode messageType Notes
1 New
2 Update
responseTypes.responseTypeCode responseTypes.responseType Notes
1 Shelter
2? ??  ??
3? ??  ??
4 Execute
5 Avoid
6 Monitor
severityCode severity Notes
1? ??  ??
2 Severe
3 Moderate
4 Minor
urgencyCode urgency Notes
1 Immediate
2 Expected
3 Future
4? ??  ??
5 Unknown

Times

These seem to be the most helpful times listed.

Expression Sample value Notes
issueTimeLocal 2019-07-30T03:21:00-04:00
expireTimeLocal 2019-07-30T21:00:00-04:00
onsetTimeLocal 2019-07-30T10:00:00-04:00 Usually returns null
effectiveTimeLocal 2019-07-30T10:00:00-04:00 Usually returns null
processTimeUTC 1564471315
expireTimeUTC 1564534800

Location

These seem to be the only helpful locations, that changes based on the location of the alert.

Expression Sample value
$twcweather.alerts.areaId "NYZ179", "ANZ335"
$twcweather.alerts.areaName "Southern Nassau County", "Long Island Sound West of New Haven CT/Port Jefferson NY"

Not Very Useful

Times

I suspect these dataPoints will only change twice a year when we change our clocks.

Expression Sample value
expireTimeLocalTimeZone EDT
effectiveTimeLocalTimeZone EDT
issueTimeLocalTimeZone EDT
onsetTimeLocalTimeZone EDT

Locations

I suspect these dataPoints may never change.

Expression Sample value
adminDistrict New York
adminDistrictCode NY
countryCode US
countryName UNITED STATES OF AMERICA
ianaTimeZone America/New_York
latitude 40.01
longitude -75.01
officeAdminDistrict New York
officeAdminDistrictCode NY
officeCode KOKX
officeCountryCode US
officeName New York City
source National Weather Service










IGNORE EVERYTHING ELSE ON THIS PAGE (PLACEHOLDERS)

Articles worth reading:

Handy Links for Reference

Here are a few links that I have found to be helpful

webCoRE

  • Dashboard (where we create & edit our pistons)
  • webCoRE Forum - Latest Topics (great community for like-minded people)
Code Description TWC Icon WU v4 Icon
0 Tornado

:twc-0:

:wu-v4-0:

1 Tropical Storm

:twc-1:

:wu-v4-1:

47 Scattered Thunderstorms

:twc-47:

:wu-v4-47:

Retrieved from "https://wiki.webcore.co/index.php?title=$twcweather.alerts&oldid=1171"