Service TypesΒΆ

This guidance covers setting up some different kinds of service which provide different levels of access to your data and different functionality.

Simple WMS
This may just show the map image in its correct location. The map colours may be data provider specific or standard. A GetFeatureInfo enabled WMS will also provide the ability to query any point on the map and retrieve a set of properties for that point in text, HTML, XML or other formats.
SLD enabled WMS
This allows the map to be coloured depending on values of some data underlying the WMS. The OneGeology Portal can ask an SLD enabled WMS to highlight units of particular ages or lithologies if it has underlying data with the GeoSciML-Lite age and lithology fields and using either IUGS-CGI vocabularies or INSPIRE vocabularies.
Simple feature WFS
This often goes together with the SLD enabled WMS. The features may be created to reflect whatever data fields exist in the source data table or there may be some level of standardisation of some or more of the fields and the values they can contain. OneGeology currently deals specifically with two simple feature standards: GeoSciML-Lite and ERML-Lite. Setting up a simple feature WFS will enable many clients to query and download your data.
Complex feature WFS
This can supply data for spatial features with complex properties that may have complex structure, multiple values, alternative value types etc. Using a standard schema for these features and standard vocabularies for categorical properties potentially enables interoperable sophisticated application processing of data from different providers. The OneGeology Portal can currently query services using the GeoSciML schema and associated vocabularies from the IUGS-CGI or INSPIRE.
WCS
This is a more recent addition to OneGeology and the Portal currently can handle raster grids that can be returned in an image format only. Other applications might be able to consume other grid data formats.

Finally, for all these service types we have additional notes for providers wishing to comply with the EU INSPIRE directive on how to make their services INSPIRE compliant as well as being usable in OneGeology.

The next section on the OneGeology Profile assumes you have a reasonable understanding of the OGC service that you wish to setup and specifies some conventions on metadata, naming etc. that we require services registered with OneGeology to fulfil. (Also, some reference to INSPIRE compliant services.) Following that is a section on preparing your data, including scanning a paper map and then a series of sections that cover how to implement a OneGeology service with a number of different software applications.