Difference between revisions of "Data Configuration for Cubes"
| Line 1: | Line 1: | ||
{{WCS Glossary | {{WCS Glossary | ||
| − | |TermDesc=For standard netCDF-CF files | + | |TermDesc=Drop your files to the provider folder. For standard netCDF-CF files the configuration is automatic. |
|Links=[http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Cubes#Serving_data_from_periodic_collection_of_NetCDF_files Serving data from periodic collection of NetCDF files] | |Links=[http://wiki.esipfed.org/index.php/WCS_Wrapper_Configuration_for_Cubes#Serving_data_from_periodic_collection_of_NetCDF_files Serving data from periodic collection of NetCDF files] | ||
Revision as of 14:09, September 2, 2010
< Back to Glossary | Edit with Form
Data_Configuration_for_Cubes Description: Drop your files to the provider folder. For standard netCDF-CF files the configuration is automatic.
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::Serving data from periodic collection of NetCDF files
- Each file becomes a coverage.
- Each variable becomes a field.
This is by far the easiest way to create a WCS service. Examples are testprovider which comes with the installation package, and NASA which serves some datasets downloaded from NASA.
For daily netCDF-CF files it is possible to create a service without compiling them into single file. See Serving data from periodic collection of NetCDF files as an example.
By creating a custom handler, it is possible to use anything as a data source.]]
Contributors
No Contributors
History
No History Available
