WCS Wrapper Configuration
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)
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.
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 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 OWS/web/static/testprovider\index.html which will be displayed from http://localhost:8080/testprovider, index of an external provider front page is here
Every provider should have wcs_capabilities.conf that lists keywords and contact information. The format is simple, copy one from the testprovider and edit it.
Windows Implementation Bug
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 /OWS/web/owsadmin.py unix_nl filename.html
for every html file you serve.
