This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 40%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Hi there.
I'm working with Azure Maps Weather service and experiencing some issue here.
When I try with Get Current Conditions API call, all works perfect, I get correct data for different cities. But when I try with Get Quarter Day Forecast API call I'm constantly getting the same data for different cities :(
I'm working with manual from here:
https://learn.microsoft.com/en-us/rest/api/maps/weather/getquarterdayforecastpreview
Examples of my calls:
NY: https://atlas.microsoft.com/weather/forecast/quarterDay/json?api-version=1.0&query=40.71305,-74.00723&subscription-key={myKey};
Could you please tell me where I'm wrong?
Best regards, Max.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 56.00000000000001%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBC%3C/text%3E%3C/svg%3E)
I'm seeing the same thing. Or, rather, I didn't get as far as you did in tracking it down. I just know that the quarterDay forecast is telling me the low temperature for Sunnyvale, California on Feb 11 from 7 AM to 1 PM, will be 19 degrees Fahrenheit. Which I know is wrong.
I checked on accuweather.com and it has the overnight lows as being anywhere from 44 to 48 degrees F, on the 11th, the day before, and the day after. That's about a 25 degree difference from what the quarterDay said!
If, as you say, it's "stuck" and is actually returning data from some different city altogether, then that makes more sense.
It's not just you! :-)
I have a response with full headers (including a X-MSEdge-Ref header) that I can post if it would help the MSFT folks track this down.
Thanks!!
@Maksym Samoilenko , this issue has been resolved. The bug that was causing this behavior has been fixed and the issue shouldn't happen again. Apologies for the inconvenience and thank you for your patience while waiting for a resolution.
I see it as fixed now too. Thanks so much to all involved!!
Thank you @ErikLindeman .
Oh, wow, that's not good. I was able to reproduce. Will escalate this internally for investigation. Thanks for reporting.
Hello.
Thank you for your response.
Could you please tell us if there is any approximate date when this fix can become available for us?
Best regards, Max.