Search results

• WCS Distributors
  Rudolf Husar Kari Hoijarvi WCS 1.1.2 Point Station, Grid Distributor NILU Aasmund Vik Paul Eckhardt WCS 1.1.2 Point Station
  770 bytes (67 words) - 15:17, September 13, 2011
• Distributor DataFed
  Community Server Other OGC Protocol(s) : WFS, WMS Data Types Served : Point Station, Grid Data in Catalog Data Registered, Description : This is a subset
  1 KB (100 words) - 06:09, September 7, 2011
• Distributor NILU
  Comm. Server Other OGC Protocol(s) : WFS 2.0 for Station Description Data Types Served : Point Station Data in Catalog Data Registered, Description : This
  4 KB (504 words) - 08:38, September 8, 2011
• Solta 2011 Workshop in a Nutshell
  co-developing a WCS server for gridded (model, satellite, emission) and point-station data with special consideration to AQ applications. CF-netCDF plays a
  1 KB (137 words) - 03:56, July 19, 2011
• 060512Report NCDCGlobalWinds
  wiki which describes our implementation of a WCS service for grid and point-station data. http://wiki.esipfed.org/index.php/WCS_Service_Implementation_-_DataFed
  3 KB (509 words) - 06:19, December 20, 2007
• HTAP Data Network: Background, Status
  server was implemented at NILU to test the methodology for accessing point monitoring-station monitoring data. The Pilot Network also included the NEISGEI server
  13 KB (1,925 words) - 20:15, May 28, 2013
• Candidate Technical Topics (section Delivery of station-point data)
  In AComServ, WCS for transferring ndim grid and point-station data; WFS for deliver monitoring station descriptions. Issue: WMS interface for preview;
  10 KB (1,293 words) - 08:55, August 30, 2011
• Solta Technical Topics (section Delivery of station-point data)
  In AComServ, WCS for transferring ndim grid and point-station data; WFS for deliver monitoring station descriptions. Issue: WMS interface for preview;
  4 KB (337 words) - 04:07, July 28, 2011
• Encoding Relational Tables in NetCDF
  variables: char station_code(station, station_code_length) ; table_name = "station"; primary_key = "T"; float lon(station) ; table_name = "station"; float lat(station) ;
  14 KB (1,883 words) - 12:39, September 1, 2011
• Glossary
  Back to WCS Wrapper WCS General Intro WCS Server StationPoint Data, Category:StationPoint WCS Server Cube Data Category:Cube WCS Mediators and Clients
  706 bytes (75 words) - 09:53, October 8, 2021
• WCS Server Software (section WCS Server for Station-Point Data Type)
  CSV file. Used for station point data in WFS GetFeature Query. WFS Capabilities: This is the top-level document of a station point data location dimension
  34 KB (5,082 words) - 02:53, September 16, 2011
• HTAP Data Network Pilot
  WCS Server for Station-Point Data Type Description of Station-Point Data Server Components Implementation of WCS Server for Station-Point Data Additional
  1 KB (140 words) - 05:37, July 6, 2011
• Location Table for Points
  Location_Table_for_Points Description: [[TermDesc::This table describes the Station Point Data location dimension. It contains at least loc_code, lat and lon columns
  2 KB (302 words) - 13:01, September 6, 2010
• Coverage Processor for Points (category StationPoint)
  Coverage_Processor_for_Points Description: This component reads a subset of Station Point Data out of an SQL database. It gets the requested coverage from the
  1 KB (185 words) - 16:09, August 17, 2012
• SQL Database for Points (category StationPoint)
  Description: [[TermDesc::This document describes how to create views in your station point data database so that it can be service by simply configuring it. It
  4 KB (510 words) - 13:36, September 6, 2010
• Feature Processor for Points (category StationPoint)
  database engine, and the resulting rows are written to a CSV file. Used for station point data in WFS GetFeature Query.]] Glossary Domain: WCS Links to this page
  2 KB (239 words) - 13:25, September 6, 2010
• ASOS STI
  Aerosol | Platform: Network | Instrument: No Instrument | Method: Point | Type: POINT | Periodicity: HOUR | GeoRange: US | Time Period: HIST Key Use: No
  927 bytes (83 words) - 13:55, January 24, 2008
• SURF MET
  the ASOS forward scattering visibility sensor (actually Bscat). The 1,200 station visibility data are particularly useful for delineating the spatial-temporal
  2 KB (217 words) - 10:03, April 18, 2013
• Example SQL for Stations (section Configuring the WFS Service and WCS Service for point data)
  Back to WCS Access to netCDF Files This is an example on how to serve Station-Point data through WCS data access protocol. The basis of the use case is the
  13 KB (1,716 words) - 10:05, September 19, 2012
• Questions and Comments about CF-1.6 Station Data Convention (section Station Data at Datafed with CF 1.5 draft)
  00:00:00" ; float lon(station) ; long_name = "station longitude"; units = "degrees_east"; float lat(station) ; long_name = "station latitude" ; units = "degrees_north" ;
  12 KB (1,546 words) - 16:43, April 23, 2012
• AQS h
  contains meteorological data, descriptive information about each monitoring station (including its geographic location and its operator), and data quality assurance/quality
  14 KB (179 words) - 11:13, December 4, 2021
• WFS Capabilities Document (category StationPoint)
  WFS_Capabilities_Document Description: [[TermDesc::This is the top-level document of a station point data location dimension. It contains Metadata Data and a list of location
  472 bytes (83 words) - 13:52, September 6, 2010
• Interoperability (section WFS_Station (optional))
  Function: Extraction of a station description record. Inputs: Station ID, output format. Outputs: Station description record in XML, KML snippet, netCDF or
  8 KB (1,256 words) - 13:03, November 28, 2008
• Capabilities Processor (category StationPoint)
  for WCS and WFS services. For input It reads the Metadata Data and Cube or Point Data Configuration. It is used to produce the results for GetCapabilities
  2 KB (197 words) - 09:05, September 6, 2010
• Subcommittee on Interoperability
  to have the following advantages: It is geared toward point observations from monitoring stations and not at a complete geographic coverage. It addresses
  20 KB (3,141 words) - 09:56, July 4, 2011
• WCS Access to netCDF Files
  information about the server WCS_Wrapper_Configuration_for_Point_Data: How to serve SQL-based point data. WCS_Wrapper_Configuration_for_Cubes: How to serve
  35 KB (5,236 words) - 12:07, July 29, 2012
• Rational for WCS and WFS Combination for point data
  those two it is possible to deliver complete metadata of a station network. Typical station network looks like 2D, but is in reality 1D. In cube data,
  6 KB (760 words) - 23:07, August 23, 2011
• CF-netCDF
  contain conventions for cube data and 1.5 contains some station data. Unofficial CF-1.5 contains point data encoding. Expired certificate, add security exception
  2 KB (312 words) - 16:41, April 23, 2012
• Data Configuration for Points (category StationPoint)
  manual configuration is needed. From file point_config.py Coverage information and it's descriptions: point_info = { 'SURF_MET': { 'Title':'Surface Meteorological
  3 KB (411 words) - 14:26, September 6, 2010
• Metadata Data (category StationPoint)
  < Back to Glossary | Edit with Form Metadata_Data Description: [[TermDesc::This is a text file filled out by a person. Contains Abstract, Contact Information
  2 KB (312 words) - 13:35, September 6, 2010
• NARSTO 5min
  description from original metadata too long? For this dataset the dataset point of contact are people (i.e. the scientist) not an organization. Do we modify
  13 KB (1,353 words) - 13:36, December 15, 2009
• AQ Community server software
  created such filters, but so far they are outside the standard Delivery of station-point data Issue: use WCS or WFS, Combination of both/which combination? Issue:
  5 KB (666 words) - 00:57, September 6, 2011
• WCS GetCoverage Query (category StationPoint)
  < Back to Glossary | Edit with Form WCS_GetCoverage_Query Description: [[TermDesc::This is the main data query for a WCS service. The request contains
  4 KB (447 words) - 14:36, September 6, 2010
• 0908SoCalFire copy
  | Participants | Discussion 2013-04-10: EventSpace cleaned up 2009-08: Station Fire Updates 2009-08: Fire Started Event Info | What's New | Data | Analysis
  6 KB (276 words) - 10:18, April 10, 2013
• Location Configuration for Points (category StationPoint)
  Processor for Points python dictionary]] No Contributors No History Available point_config.py In it's simplest case, SQL views are used to create required location
  2 KB (209 words) - 13:20, September 6, 2010
• WCS Mediators and Clients
  netCDF-CF Coverage Processor for Points This component reads a subset of Station Point Data out of an SQL database. It gets the requested coverage from the
  618 bytes (5 words) - 09:53, October 8, 2021
• Attribute Convention for Data Discovery 1-3
  29))'. geospatial_bounds_crs The coordinate reference system (CRS) of the point coordinates in the geospatial_bounds attribute. This CRS may be 2-dimensional
  35 KB (944 words) - 10:12, September 5, 2023
• Agclimate telecon 2014-11-04
  (level 2 and level 3) working on spatial tools that will do point to point, point to swath, point to grid, and swath to grid he could introduce tool and give
  3 KB (422 words) - 15:10, November 4, 2014
• DataFed Data Access Services
  types. The three main data types in DataFed are point, grid, and seqimage, shown pictorially in Fig.4. Point data arise from monitoring sites at fixed geographic
  12 KB (953 words) - 14:35, June 18, 2006
• CF Coordinate Conventions (section Timeseries of Station Data)
  1990-01-01" This is begin revised in unofficial Point Observation Conventions. The conventions describe how to code point and and trajectory data into a netCDF file
  9 KB (1,294 words) - 16:32, April 23, 2012
• Solta 2011 Agenda
  Use of netCDF and other data formats Gridded data service through WCS Station-point data service (SQL) Data server performance issues/solutions; Server co-development
  17 KB (2,368 words) - 10:22, July 28, 2012
• WCS Capabilities Document (category StationPoint)
  < Back to Glossary | Edit with Form WCS_Capabilities_Document Description: [[TermDesc::This is the top-level document of a service. It contains Metadata
  1 KB (151 words) - 11:34, September 8, 2010
• Sensor Data Quality
  single data point is checked against predetermined standards (such as range checks) point-to-point evaluation, whereby a single data point is compared
  33 KB (4,946 words) - 16:26, June 25, 2014
• WCS Describe Coverage Document For Points (category StationPoint)
  < Back to Glossary | Edit with Form WCS_Describe_Coverage_Document_For_Points Description: [[TermDesc::This document is the detailed description of a WCS
  3 KB (365 words) - 13:47, September 6, 2010
• WCS Outline (section WCS Server Software for Grid and Point Data)
  Drawing from the GEO Work Plan (Task DA-09-02d)Task Demonstrate the use of web services to compare global and regional atmospheric models (including atmospheric
  9 KB (1,059 words) - 11:39, September 8, 2010
• Point Data Example
  to Glossary | Edit with Form Point_Data_Example Description: [[TermDesc::This is an example how to create a Station Point WCS Service. It shows how to
  1 KB (178 words) - 13:34, September 6, 2010
• AQ Community Metadata Discussion
  quantitiy without its representation predefined values: satellite, surface station, sonde, aircraft, model, emission (/!\ CHANGED) -- check common data model;
  3 KB (325 words) - 10:44, October 20, 2011
• WCS Server StationPoint Data
  Glossary for WCS | WCS Outline
  448 bytes (5 words) - 09:53, October 8, 2021
• Preservation Use Cases
  minute) Horizontal Coverage: Point - above top of the atmosphere Horizontal Sampling: Point - don't need more than one point Vertical Coverage: Top of Atmosphere
  10 KB (1,540 words) - 07:53, May 15, 2011
• Air Quality Management in Lagos (category StationDoc)
  monitoring NEEDS NOx, PM10, CO CO2, SO2, VOC Description of Document: Power Point
  435 bytes (57 words) - 16:41, October 21, 2009

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)