What is the OGC?- OGC® Standards
- Cat: ebRIM App Profile: Earth Observation Products
- Catalogue Service
- CityGML
- Coordinate Transformation
- Filter Encoding
- GML in JPEG 2000
- GeoAPI
- GeoSparql
- Geographic Objects
- Geography Markup Language
- Geospatial eXtensible Access Control Markup Language (GeoXACML)
- KML
- Location Services (OpenLS)
- NetCDF
- Observations and Measurements
- Open GeoSMS
- Ordering Services Framework for Earth Observation Products
- PUCK
- SWE Common Data Model
- SWE Service Model
- Sensor Model Language
- Sensor Observation Service
- Sensor Planning Service
- Simple Features
- Simple Features CORBA
- Simple Features OLE/COM
- Simple Features SQL
- Styled Layer Descriptor
- Symbology Encoding
- Table Joining Service
- WaterML
- Web Coverage Processing Service
- Web Coverage Service
- Web Feature Service
- Web Map Context
- Web Map Service
- Web Map Tile Service
- Web Processing Service
- Web Service Common
- OGC Standards List
- Specification Profiles
- Abstract Specification
- OGC Reference Model
- OGC Schema Updates
- Public Engineering Reports
- TC Policy Directives
- GeoDRM Reference Model
- Best Practices
- Discussion Papers
- Deprecated Documents
- Retired Documents
- Requests (RFP's, RFQ's...)
- White Papers
- Change Requests
- Submit Change Request or Requirement
OGC® PUCK Protocol Standard
1) Overview
2) Downloads
3) Related Links
4) Related News
Most sensor networks require careful manual installation and configuration by technicians to assure that software components are properly associated with the physical instruments that they represent. Instrument driver software, configuration files, and metadata describing the instrument and its capabilities must be manually installed and associated with a physical instrument port. Sometimes these manual procedures must be performed under physically challenging conditions, increasing the chances of human error. PUCK addresses these challenges by defining a standard instrument protocol to retrieve metadata and other information from the device itself. This information can include OGC SWE SensorML and IEEE 1451 Transducer Electronic Data Sheet (TEDS) documents, as well as actual instrument driver code. Computers on the network can use the PUCK protocol to retrieve this information from installed instruments and utilize it appropriately, e.g. to automatically identify, configure and operate the instruments. Thus PUCK enables automatic self-configuring "plug-and-work" sensor networks.
The PUCK standard is relatively simple, and several manufacturers have already implemented the protocol in their instruments' firmware. PUCK augments but doesn't replace existing instrument command sets, so it can be implemented without abandoning existing firmware and software applications.
PUCK was originally developed by the Monterey Bay Aquarium Research Institute (MBARI) for oceanographic applications, but is useful in any sensor network containing RS232 or Ethernet-connected instruments. PUCK-enabled instruments have been deployed on ocean observatories in the USA and Europe, and the protocol is being considered for adoption by other projects as well. With the approval by the OGC membership of the OGC PUCK Protocol Standard, and with the OGC Technical Committee's PUCK Standards Working Group in place to provide future support, the PUCK standard is expected to be adopted by an even wider sensor community.
2) Downloads
3) Related Links
4) Related News
1) Overview
This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself.Most sensor networks require careful manual installation and configuration by technicians to assure that software components are properly associated with the physical instruments that they represent. Instrument driver software, configuration files, and metadata describing the instrument and its capabilities must be manually installed and associated with a physical instrument port. Sometimes these manual procedures must be performed under physically challenging conditions, increasing the chances of human error. PUCK addresses these challenges by defining a standard instrument protocol to retrieve metadata and other information from the device itself. This information can include OGC SWE SensorML and IEEE 1451 Transducer Electronic Data Sheet (TEDS) documents, as well as actual instrument driver code. Computers on the network can use the PUCK protocol to retrieve this information from installed instruments and utilize it appropriately, e.g. to automatically identify, configure and operate the instruments. Thus PUCK enables automatic self-configuring "plug-and-work" sensor networks.
The PUCK standard is relatively simple, and several manufacturers have already implemented the protocol in their instruments' firmware. PUCK augments but doesn't replace existing instrument command sets, so it can be implemented without abandoning existing firmware and software applications.
PUCK was originally developed by the Monterey Bay Aquarium Research Institute (MBARI) for oceanographic applications, but is useful in any sensor network containing RS232 or Ethernet-connected instruments. PUCK-enabled instruments have been deployed on ocean observatories in the USA and Europe, and the protocol is being considered for adoption by other projects as well. With the approval by the OGC membership of the OGC PUCK Protocol Standard, and with the OGC Technical Committee's PUCK Standards Working Group in place to provide future support, the PUCK standard is expected to be adopted by an even wider sensor community.
2) Downloads
| Version | Document Title (click to download) | Document # | Type |
|---|---|---|---|
| 1.4 | OGC® PUCK Protocol Standard | 09-127r2 | IS |
Submit a Change Request, Requirement, or Comment for this OGC standard.
3) Related Links
- MBARI's PUCK page - http://www.mbari.org/pw/
- PUCK reference design kit (detailed code that implements and uses PUCK) - http://www.mbari.org/pw/devtoolkit.htm
- Smart Ocean Sensor Consortium (SOSC) - http://sites.google.com/site/soscsite/
4) Related News
| OGC PUCK standard enables `plug and work` sensor networks 2012-01-30 |
| OGC seeks comment on PUCK standard for sensors and transducers 2011-06-23 |
| Go To OGC Press Page |
Join OGC LinkedIn
Follow OGC on Twitter
RSS Feeds