Difference between revisions of "Custom Coverage Processor for Points"
| Line 1: | Line 1: | ||
{{WCS Glossary | {{WCS Glossary | ||
| − | |TermDesc= | + | |TermDesc=Some point data is not necessarily in such a database that if could be turned into a service by just listing table and column names. A custom processor may help in the SQL query generation, the SQL execution or data retrieval when it has to be done in a non-supported manner. |
|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]] | |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]] | ||
}} | }} | ||
Revision as of 11:36, September 3, 2010
< Back to Glossary | Edit with Form
Custom_Coverage_Processor_for_Points Description: Some point data is not necessarily in such a database that if could be turned into a service by just listing table and column names. A custom processor may help in the SQL query generation, the SQL execution or data retrieval when it has to be done in a non-supported manner.
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.
By writing a custom processor, anything can be used as a data source.
