Difference between revisions of "Glossary"
| Line 11: | Line 11: | ||
== Capabilities Processor == | == Capabilities Processor == | ||
| − | This component creates the standard XML documents for WCS and WFS services. It operates on [[#Metadata|Metadata]] and [[#Configuration|Configuration]]. This is all that is needed to create Capabilities and DescribeCoverage Documents for WCS and Capabilities and DescribeFeatureType Documents for WFS. Due to standardized nature of those documents there's no need to customize any of this. Also, WCS and WFS documents are guaranteed to match. | + | This component creates the standard XML documents for WCS and WFS services. |
| + | |||
| + | It operates on [[#Metadata|Metadata]] and [[#Configuration|Configuration]]. | ||
| + | |||
| + | This is all that is needed to create Capabilities and DescribeCoverage Documents for WCS and Capabilities and DescribeFeatureType Documents for WFS. Due to standardized nature of those documents there's no need to customize any of this. Also, WCS and WFS documents are guaranteed to match. | ||
== Coverage Processor == | == Coverage Processor == | ||
Revision as of 11:41, August 31, 2010
Glossary for Common Terms and Standard Names in Datafed WCS Wrapper Framework
AQ_uFIND
A front end to GEOSS Clearinghouse. Currently can be used to find WMS services.
Example use: AQ_uFIND.aspx?datatype=point
Capabilities Processor
This component creates the standard XML documents for WCS and WFS services.
It operates on Metadata and Configuration.
This is all that is needed to create Capabilities and DescribeCoverage Documents for WCS and Capabilities and DescribeFeatureType Documents for WFS. Due to standardized nature of those documents there's no need to customize any of this. Also, WCS and WFS documents are guaranteed to match.
Coverage Processor
The Coverage Processor is a component that performs three different activities:
- WCS Query Parser. The syntax is checked and output is binary object of all the query elements.
- Subsetter. This component finds the desired coverage and applies filters to read a subset of the data:
- Fields: A client querying wind data may be interested in speed and direction, but reject air pressure.
- Bounding Box: restrict response to certain geographical area.
- Time: Default time, One time, list of times, periodic range of times.
- Grid size and interpolation: High resolution data can be interpolated to lower resolution.
- By dimension: Select only one or some wavelengths,elevations,locations
- Formatter. The binary data is returned in desired format. Currently supported are NetCDF-CF for cubes and CSV for points.
NetCDF-CF based processor is completely generic for any file. SQL processors can be either configured to supported DB schema types, or custom written for esoteric databases.
By writing a custom subsetter, anything can be used as a data source.
Configuration
Programmed instructions for the framework how to access data. This includes but is not limited to
- For Cube Coverages:
- Information of variables and dimensions automatically extracted from netCDF-CF files.
- Hand-edited python dictionaries describing the netCDF files, their variables and dimensions.
- Configuring NetCDF based Cube Data
- For Point Coverages:
- Hand-edited python dictionaries describing Names and Columns of Location and Data tables.
- Location Table Configuration
- Data Table Configuration
Datafed Browser
TODO: describe classic browser
TODO: describe browsing WCS without df catalog http://webapps.datafed.net/datafed.aspx?wcs=http://128.252.202.19:8080/CIRA&coverage=VIEWS¶m_abbr=SO4f
TODO: Describe GE Plugin browser
Feature Processor
TODO: gerate location table
GEOSS Clearinghouse
TODO: Describe
Google Earth
TODO: describe standalone and plugin
describe images and static points
describe dynamic points
ISO 19115 Metadata
TODO: describe
ISO 19115 Maker
TODO: describe
KML Keyhole Markup Language
TODO: dfescribe
KML Maker
TODO: dfescribe
Location Table
TODO: Purpose and naming
Metadata
Abstract, Contact Information, Keywords and any other such documentation that is needed in classifying or finding the service. The metadata is accessible for the user via capabilities and coverage description documents.
NetCDF-CF
TODO: describe
http://wiki.esipfed.org/index.php/Creating_NetCDF_CF_Files
SQL Database for Points
Currently the datafed WCS for points supports one kind of point data: Fixed locations and regular intervals.
Storing Point Data in a Relational Database
WCS Capabilities Document
The document contains all the high level information about a service
The Document contains:
- Description of the Service
- Machine Readable and Human Readable Name.
- Keywords
- Contact Information
- HTTP access information
- List of coverages in the service
- Machine Readable and Human Readable Name.
- Keywords
- Latitude and Longitude bounds.
- Time range in version 1.0.0
WCS Describe Coverage Document
The document describes the coverage in detail, so that the user knows what the data is and what are the dimensions of the data.
- Description of the Coverage
- Machine Readable and Human Readable Name.
- Keywords
- Latitude and Longitude bounds.
- Grid bounds in the projection of the data, if applicable
- Grid size in the projection of the data, if applicable
- Time dimension.
- Supported Coordinate Systems
- Supported Formats
- Supported Interpolations
- Fields of Coverage in versions 1.1.x
- Name
- Units
- Other dimensions, like elevation or wavelength, if applicable
- Reference to location dimension, if applicable
WCS GetCoverage Query
The main query to get data from a WCS
TODO: samples
WFS Capabilities Document
The document contains all the high level information about a service
TODO: samples
WFS DescribeFeatureType
ASOS The document contains all the high level information about a service
TODO: samples
WFS GetFeature Query
The main query to get data from a WFS
TODO: samples
sample
