United States Department of Agriculture
Natural Resources Conservation Service
National Water and Climate Center Go to Accessibility Information
Skip to Page Content
National Water and Climate Center

                        

AWDB Web Service Announcements/Release Notes

Announcements

  • December 19, 2014 - On January 14, 2015 we will be updating the AWDB Web Service.  Specifically, we will be adding two attributes to the Data object that is returned by the getData method. The first attribute is the stationTriplet. This identifies the station that each Data object which is in the array returned by the getData method is for.  The second attribute is an array of collectionDates that will contain the date of collection for each value which is returned when a user asks for SEMIMONTHLY data.

    If you use the Visual Basic API, any Excel spreadsheet or other application that uses the API will continue to work, and you will not have to make any changes to your code. If you want to use the stationTriplet or the collectionDates returned by the getData method, you can get the updated Visual Basic API here. The zip file AwdbWebServiceVBClasses-1.9.10.zip contains the latest version of the API that supports retrieval of the stationTriplet and the collectionDates from the getData method.

    If your application does not call the getData method of the AWDB Web Service you also are not affected by the changes and you do not have to do anything to your application(s).

    If you have generated “stubs” from the WSDL for the AWDB Web Service to have your application communicate with the AWDB Web Service, you will need to re-generate the “stubs” and rebuild your application.  To prevent any downtime for your application, you can rebuild your application in advance of January 14 by generating new “stubs” using the new WSDL file.

    If you have any questions about these changes, please contact Dipesh Patel at dipesh.patel@por.usda.gov.

     

Release Notes

Date

Version

Description

Oct. 23, 2013 2.13.0 Fixed a defect in the getStations() method where using wildcards in the stationId parameter was not working correctly.  Also, the getStationMetadata() and getStationMetadataMultiple() methods now return the precise latitude and longitude for all stations.
Aug. 7, 2013 2.12.1 Fixed a defect in the getInstantaneousData method where it was not returning an empty slot when a station did not have data for the requested element.  This was causing data to be misinterpreted by applications when data for multiple stations was being requested.  If someone had requested data for two stations and the first station didn’t have any data for the requested element, nothing was being returned for the first station, so applications would assume that the data returned was for the first station requested and there was no data for the second station.

Fixed a problem in the getHourlyData method where it would always retrieve ordinal 1 data regardless of the ordinal passed in. Also modified getInstantaneousData so that it will work to retrieve ordinal 2 or greater data even if there is only an ordinal 1 station element that exists.
July 24, 2013 2.11.0 Modified the getData and getInstanteousData methods so that network codes are not hard-coded and instead are table-driven.  This will allow changing the network codes of stations (such as splitting SNTL into SNTL and SCAN) in the database.  Also added a timestamp on the status page.
May 9, 2013 2.10.0 The getData method now has an additional parameter called ‘alwaysReturnDailyFeb29’.  If ‘true’ is passed in for this parameter (or null), requests for daily data will always return a slot for February 29 (regardless of whether the year is a leap year or not.  For leap years, the actual February 29 value will be returned; for non-leap years, null will be returned).  If ‘false’ is passed in, requests for daily data will only return a slot for February 29 for leap years.

The methods that return central tendencies (and peak central tendencies) now return values rounded to the precision of the sensor that collected the data.

The value that is returned for snow depth data is no longer affected by the snow water equivalent data co-located at a station (previously if the snow water equivalent value was zero, the snow depth value would be forced to zero).
Apr. 5, 2013 2.9.1 Defect fix on getHourlyData method which was producing return of erroneous results
Mar. 7, 2013 2.8.0 Modified the getStations call so that the “hucs” parameter has an implied wildcard at the end. 

Modified the getStationMetadata call so that the “huc” attribute now returns the 12-digit HUC (hydrologic unit code) of the station.  There is a new attribute that is now returned called “hud” which is the 8-digit HUC (based on the Hydrologic Unit Dataset).
Feb. 11, 2013 2.7.0 Defect fix on the status page which was causing the status page to fail in production.
Jan. 14, 2013 2.6.0 The data retrieval code was modified so that if a SWE value is between 0 and -1, it will be returned as 0.

Deployed Web Service Test Tool to http://www.wcc.nrcs.usda.gov/awdbWebService.
Dec. 17, 2013 2.5.0 Modified the getStationMetadata call so that the “huc” attribute now returns the 12-digit HUC of the station.  There is a new attribute that is now returned also called “hud” which is the 8-digit HUC (that is based on the Hydrologic Unit Dataset).
Nov. 26, 2013 2.4.1 Modified the code so that derived PRCP normals are rounded to the precision of the sensor before subtraction
Oct. 15, 2013 2.4.0 Fixed a defect in getCentralTendencyData where it was not setting the centralTendencyType correctly in the return object

Oct. 1, 2012

2.3.0

Added the following 30-Year Central Tendency methods:

getCentralTendencyData
getCentralTendencyPeakData
getForecastPeriodCentralTendency