Partager via

NOAA Weather Forecast Web Service

  • Article

Some time ago I published a Web user control that employed NOAA Web Service and displayed weather forecast. Since then I received a few emails from those folks who downloaded the control with complaints that it stopped working. The reason was always the same: timeout when calling NOAA server. Increasing timeout period didn't help. Apparently we are not alone and the problem does not seem to be control-specific. NOAA sample pages still work, but they use postback from a browser, not RPC calls to a Web service from code.

I also made a small C# Windows Application in VS 2003 that called NOAA Web Service. It ended up with timeout as well. So the issue does not seem to be related to ASP.NET or Framework 2.0.

I recenlty sent an email to NOAA Web master asking for help. I'll keep you posted.

Updated version: https://blogs.msdn.com/mikhailarkhipov/archive/2006/06/12/628540.aspx

Comments

  • Anonymous
    January 02, 2005
    I apologize for not remembering more detail, but I did run into a similiar problem sometime back. Something to do with the server date/time differential from the client. Max 5 minutes maybe? Good luck.
  • Anonymous
    January 02, 2005
    Sounds interesting, I look forward to seeing what happened.
  • Anonymous
    January 03, 2005
    The comment has been removed
  • Anonymous
    January 08, 2005
    During work of this service discovered failures in work with the co-ordinates of 34°00’E -- 46°00’N But service pleased
  • Anonymous
    January 11, 2005
    I don't think NOAA works with coordinates outside the US and its vicinity.
  • Anonymous
    January 18, 2005
    Try using the WSDL located at: http://weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl

    After changing to this WSDL from http://weather.gov/forecasts/xml/SOAP_server/ndfdXMLserver.php?wsdl my timeout issues seem to have gone away.

    Matt
  • Anonymous
    October 07, 2005
    I am using this service from my ASP.NET app for couple of days and keep getting error:
    The underlying connection was closed: The server committed an HTTP protocol violation.
    I don't know, this may be my or their problem.
    P.S. I increased the timeout in 5 times.
  • Anonymous
    October 18, 2005
    If you're getting: underlying connection was closed: The server committed an HTTP protocol violation, it's because noaa is having issues with .net 1.1:

    http://www.weather.gov/forecasts/xml/xml_changes.xml

    Some are reporting asp 2.0 beta 3 works ok.

    Brent