Copyright © 2013 Open Geospatial Consortium.
33
7.10 Additional Implementation Examples
Some additional example uses of the SWE standards include: CitySense sensor network City of Cambridge, MA: A real-time data integration
and analysis system for air quality assessment. Smart Cities various: An architecture implementation based on Sensor Web
Enablement standard specifications and makes use of the Contiki Operating System for accomplishing the Internet of Things.
Indian National Centre for Ocean Information Services INCOIS: Tsunami Early Warning System
Asian Institute of Technology, Thailand - Nepal Wireless Project: Monitoring Climate Change in the Himalayas
Taiwan – Debris Flow Monitoring and Alerting system Japan National Institute of Advanced Industrial Science Technology AIST:
Earthquake Monitoring and Warning System QuiQuake Europe Emergency Response:
http:www.ess-project.eu an infrastructure based
on SOS, SPS, and SES to provide real-time information to crisis managers during abnormal events to improve the management between forces on the ground e.g.,
police and firefighters and the control centers. Climatology-Hydrology Information Sharing Pilot, Phase 1: US and Canadian
agencies demonstrated cross-border hydrologic modeling for stream flow and also modeling and assessment of nutrient load into the Great Lakes using SWE
standards with the OGC WaterML 2.0 Encoding standard to overcome delays and obstacles imposed by different and incompatible software systems, data stores,
data models, sensor interfaces, etc.
PATS and SAP: Systems designed at the Jet Propulsion Laboratory to meet the sensor web needs and requirements of wild land firefighters as defined by the Fire
Research Working Group FRWG of the United States Department of Homeland Security DHS. SAP can additionally post emergency management information,
derived from PATS sensor data, to the Unified Incident Command and Decision Support UICDS network operated by DHS.
34
Copyright © 2013 Open Geospatial Consortium.
8 Software Implementations 8.1
Certified and Registered Implementations
OGC maintains a registry
20
of publicly available implementations of the OGC Standards. The registry includes both 1 OGC Compliant implementations and 2 self-registered
implementations. There is no requirement to register with OGC and many products that implement OGC standards are not registered. Vendors who have had their products
passed the OGC compliance tests and who have obtained an OGC Trademark License may advertise their products as OGC Compliant.
Table 3 provides summary statistics for the SWE standards implementations registered in the registry. The “n.a.” indicates that compliance certification is not yet possible as the
compliance test suite has not yet been deployed for that standard.
Table 3. Compliant and Registered Implementations of SWE
OGC Standard Compliant
Implementations Registered
Implementations SOS v1.0.0
3 35
SOS v2.0 n.a.
4 SPS v1.0.0
3 14
SPS v2.0 n.a.
2 SensorML v1.0.1
n.a. 15
OM Part 2 v1.0 n.a.
6 OM XML v2.0
n.a. 4
As part of the Compliance Program reference implementations Table 4 are confirmed as compliant and are freely available from the OGC for use by developers.
Table 4. SWE Reference Implementation Standard
Ver. Product
Developed by
SOS 1.0.0 52°North
52°North SOS
2.0 52°North
52°North SPS
1.0 52°North
52°North SPS
2.0 52°North
52°North
20
http:www.opengeospatial.orgresource
Copyright © 2013 Open Geospatial Consortium.
35
8.2 The 52°North SWE Implementation Suite
Kategori