Difference between revisions of "Custom Coverage Processor for Points"

From Earth Science Information Partners (ESIP)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{WCS Glossary
 
{{WCS Glossary
|TermDesc=A custom module for point data storage that is not supported directly.
+
|Glossary Domain=WCS
|ExampleURL=http://128.252.202.19:8080/static/CIRA/CIRA_wcs.py
+
|TermDesc=This processor extracts a subset of station point data from a data source that cannot be turned into a service by just listing table and column names. Such sources requires this kind of custom processor. It may do it's own SQL query generation, SQL query execution and data retrieval. Used in [[WCS_GetCoverage_Query|WCS GetCoverage Query]].
 +
|Links=[[Coverage_Processor_for_Points|Coverage Processor for Points]] [[Data_Configuration_for_Points|Data Configuration for Points]] [[SQL_Database_for_Points|SQL Database for Points]] [[WCS_GetCoverage_Query|WCS GetCoverage Query]]
 
}}
 
}}
 +
The CIRA/VIEWS cannot access the database directly due to firewall. The SQL query can still be compiled by with configuration, but it has to be executed via a proxy server. The CIRA/VIEWS custom processor overrides ''getcoverage'' method and does just that.
  
The service [http://128.252.202.19:8080/static/CIRA/CIRA_wcs.py CIRA/VIEWS] cannot access the database directly due to firewall. The SQL query can still be compiled by with configuration, but it has to be executed via a proxy server. The custom processor overrides ''getcoverage'' method and does just that.
+
[http://128.252.202.19:8080/static/CIRA/CIRA_wcs.py CIRA custom processor]
  
 
By writing a custom processor, anything can be used as a data source.
 
By writing a custom processor, anything can be used as a data source.

Latest revision as of 09:29, September 6, 2010

< Back to Glossary | Edit with Form

Custom_Coverage_Processor_for_Points Description: [[TermDesc::This processor extracts a subset of station point data from a data source that cannot be turned into a service by just listing table and column names. Such sources requires this kind of custom processor. It may do it's own SQL query generation, SQL query execution and data retrieval. Used in WCS GetCoverage Query.]]

Glossary Domain: WCS

Related Links

Links to this page
[[Links::Coverage Processor for Points Data Configuration for Points SQL Database for Points WCS GetCoverage Query]]

Contributors

No Contributors

History

No History Available

Term Details

The CIRA/VIEWS cannot access the database directly due to firewall. The SQL query can still be compiled by with configuration, but it has to be executed via a proxy server. The CIRA/VIEWS custom processor overrides getcoverage method and does just that.

CIRA custom processor

By writing a custom processor, anything can be used as a data source.