|
|
| (129 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| | [[WCS_Access_to_netCDF_Files| Back to WCS Wrapper]] | | [[WCS_Access_to_netCDF_Files| Back to WCS Wrapper]] |
| | | | |
| − | Glossary for Common Terms and Standard Names in Datafed WCS Wrapper Framework
| + | __TOC__ |
| | + | [[WCS General Intro]] |
| | | | |
| − | == AQ_uFIND ==
| + | [[WCS Server StationPoint Data]], [[:Category:StationPoint]] |
| | | | |
| − | A front end to GEOSS Clearinghouse. Currently can be used to find WMS services.
| + | [[WCS Server Cube Data]] [[:Category:Cube]] |
| | | | |
| − | Example use: [http://webapps.datafed.net/AQ_uFIND.aspx?datatype=point AQ_uFIND.aspx?datatype=point]
| + | [[WCS Mediators and Clients]] [[:Category:Mediator]] or [[:Category:Client]] |
| | | | |
| − | == Capabilities Processor ==
| + | [[AQ Infrastructure]] |
| − | | |
| − | This component creates the standard XML documents for WCS and WFS services.
| |
| − | | |
| − | It operates on Metadata and data configuration. From Metadata the capabilities document gets Title, Abstract, Keywords, Contact person etc... From data configuration the processor gets full information of each coverage.
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Cubes WCS Wrapper Configuration for Cubes] | |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Point_Data WCS Wrapper Configuration for Point Data]
| |
| − | | |
| − | == 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, Comma Separated Values for points.
| |
| − | | |
| − | NetCDF-CF based processor is completely generic for any compatible netCDF-CF file.
| |
| − | | |
| − | SQL processors can be either configured to supported DB schema types, or custom written for esoteric databases.
| |
| − | | |
| − | By writing a custom processor, anything can be used as a data source.
| |
| − | | |
| − | == Cube Data Configuration ==
| |
| − | | |
| − | For standard netCDF-CF files, the configuration is automatic. Each file becomes a coverage, and each variable becomes a field. This is by far the easiest way to create a WCS service. Examples are [http://128.252.202.19:8080/static/testprovider/index.html testprovider] which comes with the installation package, and
| |
| − | [http://128.252.202.19:8080/static/NASA/index.html NASA] which serves some datasets downloaded from NASA.
| |
| − | | |
| − | For daily netCDF-CF files it is possible to create a service without compiling them into single file. See [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Cubes#Serving_data_from_periodic_collection_of_NetCDF_files Serving data from periodic collection of NetCDF files] as an example.
| |
| − | | |
| − | By creating a custom handler, it is possible to store data anywhere.
| |
| − | | |
| − | == 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 ==
| |
| − | | |
| − | The WFS, Web Feature Service, is used to publish the location table for point data, because WCS DescribeCoverage Document does not support such rich dimensions well.
| |
| − | | |
| − | The Feature Processor is a component that performs three different activities:
| |
| − | | |
| − | * WFS Query Parser. The syntax is checked and output is binary object of all the query elements.
| |
| − | | |
| − | * Subsetter.
| |
| − | ** Each field may have different location table. If a the data is sparse, some fields have data only in a few locations, it makes sense to return only those locations.
| |
| − | ** Locations may also be filtered by geographic bounding box.
| |
| − | ** Other WFS filters are not implemented.
| |
| − | | |
| − | * Formatter. The data is returned in desired format. Currently the only supported is CSV, Comma Separated Values
| |
| − | | |
| − | == GEOSS Clearinghouse ==
| |
| − | | |
| − | TODO: Describe
| |
| − | | |
| − | == Google Earth ==
| |
| − | | |
| − | http://earth.google.com/
| |
| − | | |
| − | 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
| |
| − | | |
| − | == Point Data Configuration ==
| |
| − | | |
| − | Programmed instructions for the framework how to access data. This includes but is not limited to
| |
| − | | |
| − | * For Cube Coverages:
| |
| − | ** Automatic: Information of variables and dimensions extracted from netCDF-CF files.
| |
| − | ** Manual: Hand-edited python dictionaries describing the netCDF files, their variables and dimensions.
| |
| − | | |
| − | | |
| − | * For Point Coverages:
| |
| − | ** Hand-edited python dictionaries describing Names and Columns of Location and Data tables.
| |
| − | ** Custom modules for databases that are too esoteric configure in pure declarative manner.
| |
| − | | |
| − | Cube:
| |
| − | [[WCS_Wrapper_Configuration_for_Cubes| Configuring NetCDF based Cube Data]]
| |
| − | | |
| − | | |
| − | Point:
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Point_Data#Location_Table_Configuration Location Table Configuration]
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Point_Data#Data_Table_Configuration Data Table Configuration]
| |
| − | | |
| − | == Point Location Configuration ==
| |
| − | | |
| − | Programmed instructions for the framework how to access data. This includes but is not limited to
| |
| − | | |
| − | * For Cube Coverages:
| |
| − | ** Automatic: Information of variables and dimensions extracted from netCDF-CF files.
| |
| − | ** Manual: Hand-edited python dictionaries describing the netCDF files, their variables and dimensions.
| |
| − | | |
| − | | |
| − | * For Point Coverages:
| |
| − | ** Hand-edited python dictionaries describing Names and Columns of Location and Data tables.
| |
| − | ** Custom modules for databases that are too esoteric configure in pure declarative manner.
| |
| − | | |
| − | Cube:
| |
| − | [[WCS_Wrapper_Configuration_for_Cubes| Configuring NetCDF based Cube Data]]
| |
| − | | |
| − | | |
| − | Point:
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Point_Data#Location_Table_Configuration Location Table Configuration]
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Point_Data#Data_Table_Configuration Data Table Configuration]
| |
| − | | |
| − | == SQL Database for Points ==
| |
| − | | |
| − | Currently the datafed WCS for points supports one kind of point data: Fixed locations and regular intervals.
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Point_Data#Storing_Point_Data_in_a_Relational_Database 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
| |
| − | | |
| − | [http://128.252.202.19:8080/NASA?service=WCS&acceptversions=1.1.2&Request=GetCapabilities Example Version 1.1.2]
| |
| − | | |
| − | [http://webapps.datafed.net/OMAERO_G.ogc?SERVICE=WCS&REQUEST=GetCapabilities&VERSION=1.0.0 Example 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
| |
| − | | |
| − | [http://128.252.202.19:8080/NASA?service=WCS&version=1.1.2&Request=DescribeCoverage&identifiers=modis4 Example Version 1.1.2]
| |
| − | | |
| − | [http://webapps.datafed.net/OMAERO_G.ogc?VERSION=1.0.0&SERVICE=WCS&REQUEST=DescribeCoverage&Coverage=AOTMW Example Version 1.0.0]
| |
| − | | |
| − | == WCS GetCoverage Query ==
| |
| − | | |
| − | The main query to get data from a WCS
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Point_Data#GetCoverage GetCoverage for points]
| |
| − | | |
| − | TODO: samples
| |
| − | | |
| − | == WFS Capabilities Document ==
| |
| − | | |
| − | The document contains all the high level information about a service
| |
| − | | |
| − | TODO: samples
| |
| − | | |
| − | == WFS DescribeFeatureType ==
| |
| − | | |
| − | [http://128.252.202.19:8080/NCDC?Service=WFS&version=1.0.0&request=DescribeFeatureType&typename=ASOS 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
| |
| | | | |
| | + | Glossary for Common Terms and Standard Names in Datafed WCS Wrapper Framework |
| | + | This is the 'WCS Glossary' form. To add a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. |
| | + | {{#forminput:Glossary}} |
| | | | |
| − | TODO: samples
| + | {{#ask: [[TermDesc::+]][[Category:Glossary]] |
| − | [http://128.252.202.19:8080/NCDC?Service=WFS&version=1.0.0&request=GetFeature&typename=ASOS&outputformat=text/csv sample] | + | |mainlabel=Term |
| | + | |?TermDesc=Description |
| | + | |?Glossary Domain=Tags |
| | + | |limit=500 |
| | + | |order=asc |
| | + | }} |
