web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / 24 Hour Rainfall Data ...
Power Automate
Unanswered

24 Hour Rainfall Data Scheduled Flow

(0) ShareShare
ReportReport
Posted on by 2

Attempting to crack this flow, however really coming up empty handed here. I am looking to use NWS API to pull the previous 24 hour rainfall information. I can get the HTTP call out and parse the JSON it returns, however it limits the precipitation to last 6 hours and I am not sure there is another means to go about getting this data to be honest. If anyone has conquered something like this it would be great. The intent is to setup a message system that notifies me when a threshold has been past for rainfall over the previous 24 hours.

Categories:
I have the same question (0)
  • wskinnermctc Profile Picture
    6,519 Moderator on at

    I don't know what the data looks like that is returned from the HTTP request, but could you add it together with another http request? 

     

    So you have a flow that triggers and sends HTTP1 request to get data. Then put in a delay of 6 hours or less and run another HTTP2 request. Add those two rainfall from HTTP1 and HTTP2 together and if it hit the limit send an email. 

    If it did not hit the limit, put another delay of 6 hours or less and send HTTP3 request.....

     

    So you basically have a flow that would run for 24 hours using delay steps within the flow. Then a new flow triggers the next day.

     

    Does that seem possible with the data or what you are trying to do?

     

     

    .......Thinking about it again, I guess that wouldn't work for rolling time would it?

  • wskinnermctc Profile Picture
    6,519 Moderator on at

    Could you put the rainfall quantity in a SharePoint list and add it together?

     

    So with the same idea of flow with delay steps in it, except you are putting the rainfall amount into a sharepoint list. Then you add that amount together and if it is to the threshold then it send an email? 

     

    Like if you had a single flow with HTTP Request every 6 hours, so 4 HTTP Requests. Then you have 4 items in the sharepoint list. And those items repeatedly get updated by their corresponding HTTP request.

     

    You could add those 4 items together and get total rainfall for the past rolling 24 hours.

     

    Something like that? It's kind of a funny solution and requires a SharePoint list or Excel Table to post the data.

  • jeromuhi Profile Picture
    2 on at

    Possibly, however when the JSON is parsed, it does not separate out the values and typical each call gives a long list of updates that occurred in the previous time period. I managed to filter these by the past 24 hours, however the list is extensively long, so further filtering it down to 6 hours and then adding 12 hours, and 18 and 24 hours may be doable the the times are not at specific intervals so setting it up to be precise based on the intervals NWS updates at would seem cumbersome to say the least. The following step from there would be to sort out why it does not provide an actual integer for the value the API presents.

    {
     "@context": [
     "https://geojson.org/geojson-ld/geojson-context.jsonld",
     {
     "@version": "1.1",
     "wx": "https://api.weather.gov/ontology#",
     "s": "https://schema.org/",
     "geo": "http://www.opengis.net/ont/geosparql#",
     "unit": "http://codes.wmo.int/common/unit/",
     "@vocab": "https://api.weather.gov/ontology#",
     "geometry": {
     "@id": "s:GeoCoordinates",
     "@type": "geo:wktLiteral"
     },
     "city": "s:addressLocality",
     "state": "s:addressRegion",
     "distance": {
     "@id": "s:Distance",
     "@type": "s:QuantitativeValue"
     },
     "bearing": {
     "@type": "s:QuantitativeValue"
     },
     "value": {
     "@id": "s:value"
     },
     "unitCode": {
     "@id": "s:unitCode",
     "@type": "@id"
     },
     "forecastOffice": {
     "@type": "@id"
     },
     "forecastGridData": {
     "@type": "@id"
     },
     "publicZone": {
     "@type": "@id"
     },
     "county": {
     "@type": "@id"
     }
     }
     ],
     "id": "https://api.weather.gov/stations/PADQ/observations/2023-08-09T18:53:00+00:00",
     "type": "Feature",
     "geometry": {
     "type": "Point",
     "coordinates": [
     -152.5,
     57.75
     ]
     },
     "properties": {
     "@id": "https://api.weather.gov/stations/PADQ/observations/2023-08-09T18:53:00+00:00",
     "@type": "wx:ObservationStation",
     "elevation": {
     "unitCode": "wmoUnit:m",
     "value": 34
     },
     "station": "https://api.weather.gov/stations/PADQ",
     "timestamp": "2023-08-09T18:53:00+00:00",
     "rawMessage": "PADQ 091853Z 06003KT 10SM -RA BKN003 OVC007 12/11 A2961 RMK AO2 SLP028 P0001 T01170111",
     "textDescription": "Light Rain",
     "icon": "https://api.weather.gov/icons/land/day/rain?size=medium",
     "presentWeather": [
     {
     "intensity": "light",
     "modifier": null,
     "weather": "rain",
     "rawString": "-RA"
     }
     ],
     "temperature": {
     "unitCode": "wmoUnit:degC",
     "value": 11.7,
     "qualityControl": "V"
     },
     "dewpoint": {
     "unitCode": "wmoUnit:degC",
     "value": 11.1,
     "qualityControl": "V"
     },
     "windDirection": {
     "unitCode": "wmoUnit:degree_(angle)",
     "value": 60,
     "qualityControl": "V"
     },
     "windSpeed": {
     "unitCode": "wmoUnit:km_h-1",
     "value": 5.4,
     "qualityControl": "V"
     },
     "windGust": {
     "unitCode": "wmoUnit:km_h-1",
     "value": null,
     "qualityControl": "Z"
     },
     "barometricPressure": {
     "unitCode": "wmoUnit:Pa",
     "value": 100270,
     "qualityControl": "V"
     },
     "seaLevelPressure": {
     "unitCode": "wmoUnit:Pa",
     "value": 100280,
     "qualityControl": "V"
     },
     "visibility": {
     "unitCode": "wmoUnit:m",
     "value": 16090,
     "qualityControl": "C"
     },
     "maxTemperatureLast24Hours": {
     "unitCode": "wmoUnit:degC",
     "value": null
     },
     "minTemperatureLast24Hours": {
     "unitCode": "wmoUnit:degC",
     "value": null
     },
     "precipitationLastHour": {
     "unitCode": "wmoUnit:mm",
     "value": 0,
     "qualityControl": "C"
     },
     "precipitationLast3Hours": {
     "unitCode": "wmoUnit:mm",
     "value": null,
     "qualityControl": "Z"
     },
     "precipitationLast6Hours": {
     "unitCode": "wmoUnit:mm",
     "value": null,
     "qualityControl": "Z"
     },
     "relativeHumidity": {
     "unitCode": "wmoUnit:percent",
     "value": 96.107794274811,
     "qualityControl": "V"
     },
     "windChill": {
     "unitCode": "wmoUnit:degC",
     "value": null,
     "qualityControl": "V"
     },
     "heatIndex": {
     "unitCode": "wmoUnit:degC",
     "value": null,
     "qualityControl": "V"
     },
     "cloudLayers": [
     {
     "base": {
     "unitCode": "wmoUnit:m",
     "value": 90
     },
     "amount": "BKN"
     },
     {
     "base": {
     "unitCode": "wmoUnit:m",
     "value": 210
     },
     "amount": "OVC"
     }
     ]
     }
    }

     Above is what the response looks like for the latest observations.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 784

#2
Valantis Profile Picture

Valantis 589

#3
Haque Profile Picture

Haque 522

Last 30 days Overall leaderboard