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 custom module for point data storage that is not supported directly. | ||
− | | | + | |Links=[http://128.252.202.19:8080/static/CIRA/CIRA_wcs.py CIRA custom processor] |
}} | }} | ||
− | 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 | + | 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. |
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 15:02, September 2, 2010
< Back to Glossary | Edit with Form
Custom_Coverage_Processor_for_Points Description: A custom module for point data storage that is not supported directly.
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::CIRA custom processor]]
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.
By writing a custom processor, anything can be used as a data source.