Precip Fields In Premium Point Forecast API
-
@idefix37 that justify the 2 month timespan for just idenifing a problem
-
@nikarayanpouya specially when I'm being charged for every minute using your API in premium.
-
@nikarayanpouya
I’m just a Windy user as you are. So don’t start this type of discussion with me. I was just trying to help you ! -
@idefix37 im sorry but im just frustrated with the admins not paying attention and just ignoring the problem while im here showing wrong data in my website due to this problem.
-
@nikarayanpouya Hi, I am sorry about the delay in the reply. Can you please describe what you image under term convPrecip?
-
@Suty hi actually i dont know what the term exactly mean but i know that as you send the picture earlier it concludes snow and conv percip but as you see in the numbers you are giving me snow percip is higher than these both.
-
@Suty I also examined some other sample and problem occurs frequently in your data and its not a one time error (for the record the problem is : the number for snowpercip is larger than convpercip and percip)
-
@nikarayanpouya Hi, once again, I had discussion with colleagues and the problem is caused by the fact that @idefix37 mentioned. snowprecip is calculated as snow column, but the precipitation contains this value from water column. So the snowPrecip is contained in total precipitation, but in the different form.
-
Hi @nikarayanpouya, may I ask which model are you using? I would like to examine your issue more the make sure the data you are receiving are correct. Our documentation notes that both
past3hprecip-surfaceandpast3hsnowprecip-surfaceshould be returned as water column equivalent.edit: Also, which areas do you see discrepancies at? Everywhere? I briefly checked Alps in
icon-euandgfsand so far I haven't found anything wrong (snow precip always below or equal total precip) -
@Filip_K Yes , I examined some other sample and problem occurs frequently in your data and its not a one time error. im using the gfs model.
-
@nikarayanpouya
you are right, I was able to replicate the issue withGFSmodel. Same issue most likely happens with other NOAA models (nam*) because these models don't provide snow precipitation directly but it is instead computed from total precipitation accumulation and categorical snow.
I will look more into this and try to improve the computed results, as it doesn't make much sense now. -
Hi @Filip_K ! I just wanted to express my sincere appreciation for finally addressing the issue we've been facing. It's a relief to know that the matter is being taken seriously. I'm really looking forward to receiving updates from you regarding the progress made in resolving this problem. It's crucial for me to fix it as soon as possible, as my own customers have been reporting the issue, and their satisfaction is my top priority. Thank you for your attention to this matter, and I eagerly await your notification when the problem is solved.
-
@nikarayanpouya
it is fixed now andpast3hsnowprecip-surfaceis guaranteed to never go abovepast3hprecip-surface -
@Filip_K Hi
I also appreciate it if you fix the units you are returning in your service because you said snowpercip is in centimeters but you are returning millimeter as unit for snow percip. -
Hi @nikarayanpouya, as stated in the docs, all precipitation values are returned as water column:
We cannot change returned values, that would break the API for all other users. If you want to get height of new snow from snowPrecip, multiply the water column value by 10 (or use the value as it was cm of snow already - that does the same job). As mentioned before, 1mm of water column precipitation roughly equals to 1cm of new snow.
