WCS Wrapper Configuration

Back to WCS Wrapper

Project on SourceForge

Questions and comments should go to sourceforge discussions, bug reports to sourceforge tickets. Urgent issues can be asked from Kari Hoijarvi 314-935-6099(w) or 314-843-6436(h)

Last updated 2010-07-21

Structure of OWS/web

OWS/web is for system developers only.

OWS/web/static contains static web content. You can put any documentation here and it will be served as a web page or download. The home page index.html is pretty much mandatory, and you shoud change favicon.ico to reflect your organization. We highly recommend, that you customize these to document your WCS service.

OWS/web/static/cache is a folder for temporary files. The service uses it for output files. Anything you put there will be deleted when space is needed.

The installation contains an example datasets OWS/web/static/testprovider and OWS/web/static/point. The testprovider is a demo NetCDF dataset, point is an example how to server point data from a SQL database. Every service will have a folder with the same name here.

You may now check the provider page http://localhost:8080/testprovider which is served as a static file. Any file under static becomes accessible

The Human Interface: Create the index.html Front Pages for Visitors.

Edit index.html for users.

Edit wcs_capabilities.conf for keywords and contact information.

If no query is present, the server gives a default page index.html. You should provide pages for your server and for all the providers.

The server index.html is at C:\OWS\web\static\index.html, which will be displayed from url http://localhost:8080/, Index of an external server index.html is here.

Every provider folder should also have an index.html like C:\OWS\web\static\testprovider\index.html which will be displayed from http://localhost:8080/testprovider, index of an external provider front page is here

If you modify the default index.html, make sure not to overwrite' it next time you upgrade the WCS Wrapper package. Keep the main copy elsewhere and copy it back.

Important There is a bug deep in python core libraries that make serving text files tricky. The files need to be encoded with unix style line ending convention '\n', instead of windows style '\r\n'.

To fix this, issue command:

   python C:\OWS\web\owsadmin.py unix_nl "C:\OWS\web\static\testprovider\index.html"

for every html file you serve.

Serving data from periodic collection of NetCDF files

Sometimes you have accumulated a huge number of small NetCDF files, like daily slices from a model output. You could combine those into one big cube, but you for a terabyte of files, that may not be an option.

Download our HTAP test package custom-netcdf-1.2.0.zip. It only has two days of data to make download small. Then read the custom provider page

Serving Point Data:

Sometimes you have accumulated a huge number of small timeseries NetCDF files, like daily slices from a model output. You could combine those into one big cube, but you for a terabyte of files, that may not be an option.

Provider point is an example how to configure this service to use SQL database to serve point data.