Difference between revisions of "Custom Coverage Processor for Points"

From Earth Science Information Partners (ESIP)
Line 1: Line 1:
 
{{WCS Glossary
 
{{WCS Glossary
|TermDesc=A custom module for point data storage that is not supported directly.
+
|TermDesc=A Coverage Processor for a point data storage that is not supported by the system.
|Links=[http://128.252.202.19:8080/static/CIRA/CIRA_wcs.py CIRA custom processor]
+
|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]]  
 
}}
 
}}
  
 
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 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.
 +
 +
[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.

Revision as of 09:26, September 3, 2010

< Back to Glossary | Edit with Form

Custom_Coverage_Processor_for_Points Description: A Coverage Processor for a point data storage that is not supported by the system.

Glossary Domain: {{{Glossary Domain}}}"{{{Glossary Domain}}}" is not in the list (WCS, HTAP, AQInfrastructure) of allowed values for the "Glossary Domain" property.

Related Links

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

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.