NcSOS

Stable version: v1.4.3 for THREDDS version 4.5+

Stable version: v1.1.1 for all other THREDDS versions

NcSOS adds an OGC SOS service to datasets in your existing THREDDS server. It complies with the IOOS SWE Milestone 1.0 templates and requires your datasets be in any of the CF 1.6 Discrete Sampling Geometries.

NcSOS acts like other THREDDS services (such an OPeNDAP and WMS) where as there are individual service endpoints for each dataset. It is best to aggregate your files and enable the NcSOS service on top of the aggregation. i.e. The NcML aggregate of hourly files from an individual station would be a good candidate to serve with NcSOS. Serving the individual hourly files with NcSOS would not be as beneficial.

You will need a working THREDDS installation of at least version 4.3.16 to run NcSOS v1.1.1 or ealrier You will need a working THREDDS installation of at least version 4.5 to run NcSOS v1.4.2

Quick Links

1. Mailing list: https://groups.google.com/forum/#!forum/ncsos
2. Documentation wiki: https://github.com/asascience-open/ncSOS/wiki
3. Source repository: https://github.com/asascience-open/ncSOS/
4. Issues and Ideas: https://github.com/asascience-open/ncSOS/issues?state=open
5. Get source/installers: https://github.com/asascience-open/ncSOS/releases
6. Deployed Servers:

ChangeLog

v1.4.3

• Added the ability to enable/disable ncSOS globally in the threddsConfig.xml file
• To enable ncSOS add the following to the threddsConfig.xml:

<NCSOS>
  <allow>true</allow>
</NCSOS>

v1.4.2

• Added response formats to return data in CSV or JSON
• Get observations for GRID feature type when latitude/longitude is specified
• Addresses all issue from Milestone 1.4

v1.2.1 / v1.1.1

• Fixes an issue with attributes not being set correctly in the Describe Sensor response - see issue #171

v1.2

• Works with version 4.5 of the THREDDS data server. Please note that this version contains all of the same functionality as v1.1 and that it is not backwards compatible with previous versions of the THREDDS data server.

v1.1

• Addressed defects identified in the November 2014 test report (#156).

v1.0

• Added support for GetObservation requests on TimeSeriesProfile datasets.

RC9

• Makes use of THREDDS Spring implementation. Modifications to the web.xml and sos-servlet.xml files are no longer needed.
• Bug fixes for issues detected during IOOS validation tests.

RC8

• Better/automatic workaround for aggregation caching problem (software will automatically detect aggregations and disable caching support. This is only necessary until the problem is fixed in THREDDS, hopefully in 4.4.1)
• Bug fixes for bugs deteected during OGC and IOOS validation tests.

RC7

• Testing refactor
• Better class names
• Lots of cleanup in code and comments
• Now uses JDOM and XML objects instead of strings
• Jenkins integration

RC6

• Testing cleanup
• Lots of bug schema related bug fixes

RC5

• IOOS SWE Milestone 1.0 support
• Code cleanup and documentation
• Hosten in Maven
• Caching bug fix (see Known Issues below)

RC3-4

• Updated DescribeSensor formatting to match new IOOS DescribeSensorPlatform and DescribeSensorNetwork
• Added new response format for time series datasets
• New IOOS reponse format for GetObservation requests
• Templates for new IOOS formats found here: https://code.google.com/p/ioostech/source/browse/trunk/templates/Milestone1.0
• New system for logging missing variables and attributes in datasets

RC2:

• Expanded metadata reporting from files.
• Began updating the responses to the SOS 2.0 response format.
• Fixed formatting.
• Fixed many, many smaller bugs.
• Added error handling for large datasets.

RC1:

• Added support for GetCapabilities, DescribeSensor and GetObservation requests.
• Added caching for GetCapabilities requests
• Supports CF 1.6 convention files including: TimeSeries, TimeSeriesProfile, Trajectory, Profile, TrajectoryProfile (Section) and Grid datasets.

Known Issues

• Aggregating files using NcML does not work with the built in THREDDS caching system. This is an issue on Unidata's side. NcSOS has a built-in workaround that will disable caching when an aggregated dataset is detected.