ESA > Join & Share > KEO > OGC KUFFIA Modules

OGC KUFFIA Modules

OGC KUFFIA Modules

KUFFIA modules are the factory Java processor modules provided with the KEO system and available if administrator ingests and configures them. Among others, theOGC KUFFIAmodules are intended to deal with generic OGC services. Three OCG standards have been implemented in the KEO context: WCS, WFS, WMS.

WCS

The Web Coverage Service (WCS) Interface Standard is a standard created by the OGC (http://www.opengeospatial.org/standards/wcs) which refers to the geospatial information provided as ‘coverages’: digital geospatial information representing space-varying phenomena. WCS provides a standard interface for how to request the raster source of a geospatial image.The results of a WCS can be used for complex modeling and analysis, as it often contains more information. It also allows more complex querying - clients can extract just the portion of the coverage that they need.

Below for a brief description of available modules.

KEO WCS Capabilities Getter: Retrieves capabilities from specified WCS Server

KEO WCS Getter: Retrieves geospatial data from specified WCS Server

KEO WCS Getter 1.0.0 BBOX: Retrieves geospatial data from specified WCS Server version 1.0.0 and a input Bounding BOX

KEO WCS Getter 1.0.0 Time: Retrieves geospatial data from specified WCS Server version 1.0.0 and an input Time

KEO WCS Getter 1.1.0: Retrieves geospatial data from specified WCS Server version 1.1.0 or newer.

KEO GeoServer WCS Inserter: Save a coverage into a GeoServer WCS via GeoServer RESTful API.

WFS

The Web Feature Service (WFS) Interface Standard (http://www.opengeospatial.org/standards/wfs) provides an interface allowing requests for geographical features across the web using platform-independent calls. One can think of geographical features as the "source code" behind a map, whereas the WMS interface or online mapping portals like Google Maps return only an image, which end-users cannot edit or spatially analyze. The XML-based GML furnishes the default payload-encoding for transporting the geographic features, but other formats like shapefiles can also serve for transport.

Below for a brief description of available modules.

KEO WFS Capabilities Getter: Retrieves capabilities from specified WFS Server.
KEO WFS Getter: Retrieves features from specified WFS Server.
KEO WFS Inserter: Inserts a layer into a WFS Server.

WMS

The Web Map Service (WMS) Interface Standard (http://www.opengeospatial.org/standards/wms) is a standard protocol for serving georeferenced map images over the Internet that are generated by a map server using data from a GIS database. The specification was developed and first published by the Open Geospatial Consortium in 1999. A WMS server usually serves the map in a bitmap format, e.g. PNG, GIF or JPEG.

Below for a brief description of available modules.

KEO WMS Capabilities Getter: Retrieves capabilities from specified WMS Server.
KEO WMS Getter1: Retrieves map from specified WMS Server.
KEO WMS Getter2: Retrieves map from specified WMS Server.

Contributors to this page:

Michele Iapaolo
fspinelli
Luisa Zizi .

Page last modified on Wednesday 30 of October 2013 09:24:57 CET by Michele Iapaolo.

Category: KEO

History

Search Help

Non Advanced Search or Natural Search

The documents are returned sorted on relevance depending on order, proximity, frequency of terms.

Advanced Search or Boolean Search

Default search behavior

By default, all search terms are optional. It behaves like an OR logic. Objects that contain the more terms are rated higher in the results and will appear first in their type. For example, wiki forum will find:

objects that include both terms
objects that include the term wiki
objects that include the term forum

Requiring terms

Add a plus sign ( + ) before a term to indicate that the term must appear in results. Example: +wiki forum will find objects containing at least wiki. Objects with both terms and many occurences of the terms will appear first.

Excluding terms

Add a minus sign ( - ) before a term to indicate that the term must not appear in the results. To reduce a term's value without completely excluding it, use a tilde. Example: -wiki forum will find objects that do not contain wiki but contain forum

Grouping terms

Use parenthesis ( ) to group terms into subexpressions. Example: +wiki +(forum blog) will find objects that contain wiki and forum or that contain wiki and blog in any order.

Finding phrases

Use double quotes ( " " ) around a phrase to find terms in the exact order, exactly as typed. Example: "Alex Bell" will not find Bell Alex or Alex G. Bell.

Using wildcards

Add an asterisk ( * ) after a term to find objects that include the root word. For example, run* will find:

objects that include the term run
objects that include the term runner
objects that include the term running

Reducing a term's value

Add a tilde ( ~ ) before a term to reduce its value indicate to the ranking of the results. Objects that contain the term will appear lower than other objects (unlike the minus sign which will completely exclude a term). Example: +wiki ~forum will rate an object with only wiki higher that an object with wiki and forum.

Changing relevance value

Add a less than ( < ) or greater than ( > ) sign before a term to change the term's contribution to the overall relevance value assigned to a object. Example: +wiki +(>forum < blog) will find objects that contain wiki and forum or wiki and blog in any order. wiki forum will be rated higher.