Difference between revisions of "Glossary"

From Earth Science Information Partners (ESIP)
m (1 revision imported)
 
(164 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]]
  
== WCS Capabilities Document ==
+
[[WCS Server StationPoint Data]], [[:Category:StationPoint]]
  
The document contains all the high level information about a service
+
[[WCS Server Cube Data]] [[:Category:Cube]]
  
The Document contains:
+
[[WCS Mediators and Clients]] [[:Category:Mediator]] or [[:Category:Client]]
* 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]
+
[[AQ Infrastructure]]  
  
[http://webapps.datafed.net/OMAERO_G.ogc?SERVICE=WCS&REQUEST=GetCapabilities&VERSION=1.0.0 Example Version 1.0.0]
+
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.
== Capabilities Processor ==
+
{{#forminput:Glossary}}
 
 
TODO: compile metadata & stuff into capo and desc documents.
 
 
 
== 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
 
 
 
 
 
TODO: samples
 
[http://128.252.202.19:8080/NCDC?Service=WFS&version=1.0.0&request=GetFeature&typename=ASOS&outputformat=text/csv sample]
 
 
 
== 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.
 
** [[WCS_Wrapper_Configuration_for_Cubes| Configuring NetCDF based Cube Data]]
 
 
 
* For Point Coverages:
 
** Hand-edited python dictionaries describing Names and Columns of Location and Data tables.
 
** [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]
 
 
 
== 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.
 
 
 
== 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]
+
{{#ask: [[TermDesc::+]][[Category:Glossary]]
 +
|mainlabel=Term
 +
|?TermDesc=Description
 +
|?Glossary Domain=Tags
 +
|limit=500
 +
|order=asc
 +
}}

Latest revision as of 08:53, October 8, 2021

Back to WCS Wrapper


WCS General Intro

WCS Server StationPoint Data, Category:StationPoint

WCS Server Cube Data Category:Cube

WCS Mediators and Clients Category:Mediator or Category:Client

AQ Infrastructure

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.


TermDescriptionTags
AQ Community CatalogThe AQ Community Catalog is theAQInfrastructure
Coverage Processor for PointsThis component reads a subset of Station Point Data out of an SQL database. It gets the requested coverage from the query and gets the relevant SQL table and column names from the configuration information. Then it creates an SQL query according to filters, which is executed in the SQL database engine, and the resulting rows are written to a CSV file. Used in WCS GetCoverage Query.WCS
Datafed BrowserDatafed Browser is a web program for viewing WCS and WMS services.WCS
AQInfrastructure
GEOSS ClearinghouseThe GEOSS Clearinghouse is the engine that drives the entire system. It connects directly to the various GEOSS components and services, collects and searches their information and distributes data and services. The AQ Community records can be found in the clearinghouse and aq applications, like uFIND, search the clearinghouse.WCS
AQInfrastructure
Google EarthGoogle Earth lets you fly anywhere on Earth to view satellite imagery, maps, terrain, 3D buildings, from galaxies in outer space to the canyons of the ocean. You can explore rich geographical content, save your toured places, and share with others.WCS
ISO 19115 Metadata for Air QualityISO 19115 is the metadata standard for Geographic information. The AQ Community chose ISO 19115 because it is a standard accepted by GEOSS and being implemented widely around the world. It includes the ISO 19115 Core, 19119 metadata for describing the geospatial services and AQ-specific metadata for finding datasets.WCS
HTAP
AQInfrastructure
KML Keyhole Markup LanguageKML is a file format used to display geographic data in an Earth browser such as Google Earth, Google Maps, and Google Maps for mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. All tags are case-sensitive and must be appear exactly as they are listed in the KML Reference. The Reference indicates which tags are optional. Within a given element, tags must appear in the order shown in the Reference.WCS
Python DictionariesPython is a simple programming language. It contains the dictionary datatype, which is a simple key=value hierarchical database. Due to simple syntax, the datafed WCS uses it as a configuration file, instead of xml files or something similar.WCS
WCS StandardTerm DescriptionWCS
WCS-CF-netCDF MatchingTerm DescriptionWCS
HTAP