Standard Data Format (SDF) - SOS Software Revision History

This page documents the revision history of the NDBC SOS service located at http://sdf.ndbc.noaa.gov/sos/. Source code and installation instructions may be downloaded from the software page.

• August 19, 2010 - Version 1.2 NDBC SOS service changes include:.

  1. The service now includes air temperature (air_temperature), conductivity (sea_water_electrical_conductivity) and sea level pressure (air_pressure_at_sea_level). These observed properties are available in CSV, TSV and KML format. They will not be offered in GML.
  2. Glider data were added to the data base. These data include water temperature and salinity. These data are only available in CSV and TSV format. These data may only be requested by station ID. Support for glider data in collections is not yet available.
  3. The script was updated to reflect the move of the GML schema from www.csc.noaa.gov to ioos.gov.

• July 15, 2010 - Version 1.1 NDBC SOS service changes include:.

  1. The trailing colons (:) have been removed from the station and sensor URNs. These colons separated station /sensor from an optional version (deployment date). Since the URN syntax does not allow trailing colons, these colons are removed until the optional versions are added at a later time.
  2. The GetCapabilities processing was modified to return a VersionNegotiationFailed exception code when the version parameter is invalid.
  3. The service now returns an OperationNotSupported exception code only when a non-supported but valid SOS method is requested. If an invalid method, e.g., GetLost, is requested, the response contains an InvalidParameterValue exception code.
  4. Converted SOS exception codes to constants to prevent coding errors.

• June 23, 2010 - Version 1.0 NDBC SOS service changes include:.

  1. Comma-separated values (CSV) output is now available. This output is obtained by specifying a responseformat parameter of text/csv on the GetObservation request. See more info on the CSV response format (PDF).
  2. Tab-separated values (TSV) output is now available. This output is obtained by specifying a responseformat parameter of text/tab-separated-values on the GetObservation request. See more info on the TSV response format (PDF).
  3. The names of scalar properties have been changed to use Climate and Forecast (CF) Standard Names where appropriate. Some composite (multi-valued) phenomena (winds, waves and currents) do not have CF equivalents. Where URLs instead of names are needed (e.g., om:observedProperty in GML response), Marine Metadata Interoperability (MMI/CF) URLs are used.
  4. To be more in line with the next version of SOS, the GetCapabilities response now lists a single procedure per station offering. The procedure is the station identifier. Previously, every sensor on a station was listed in the offering. Network offerings still list multiple procedures (one for each station in the network). In the future, this will change as well requiring a DescribeSensor request to find the stations in a given network.
  5. To accommodate OGC testing software, date/time values now include the seconds field. These values are formatted per ISO 8601 (yyyy-mm-ddThh:mm:ssZ). This does not imply accuracy of clocks to the nearest second.
  6. URNs now use the IOOS namespace and are formatted as follows:
     1. Network URNs are formatted as urn:ioos:network:authority:name where name is the name of the network and authority is the authority that named the network.
     2. Station URNs are formatted as urn:ioos:station:authority:stationid:version where authority is the authority that defined the station (wmo for NDBC defined stations), stationid is the station id (42001) and version is an optional version/deployment date formatted as yyyymmdd.
     3. Sensor URNs are formatted as urn:ioos:sensor:authority:station:version1:sensorid:version2 where sensorid is the senor Id and version2 is the optional sensor version date formatted as yyyymmdd.
  7. The old mysql DB class has been replaced with mysqli calls. This is internal to the code and does not affect usage.
  8. KML/JSON output is now available. This output is obtained by specifying a responseformat parameter of application/vnd.google-earth.kml+xml on the GetObservation request. Remember to urlencode the parameter value. The KML/JSON format is subject to change following additional testing. The KML/JSON response uses embedded Javascript which restricts it to Google Earth 5.

Access data via map
Access data via KML (Temporary Demo)
Access data via SOS