http://geospatial.nomad-labs.com/2006/04/03/osgeo-racing-ahead-sensor-observation-service/ geospatial team at nomad labs Thu, 28 Aug 2008 14:40:09 +0000 http://wordpress.org/?v=2.5.1 http://geospatial.nomad-labs.com/2006/04/03/osgeo-racing-ahead-sensor-observation-service/#comment-11 shoaib Thu, 04 May 2006 03:40:17 +0000 http://geospatial.nomad-labs.com/?p=33#comment-11 Cool! I'll be giving it a try Cool! I’ll be giving it a try

]]> http://geospatial.nomad-labs.com/2006/04/03/osgeo-racing-ahead-sensor-observation-service/#comment-10 Alexander C. Walkowski Tue, 02 May 2006 06:50:23 +0000 http://geospatial.nomad-labs.com/?p=33#comment-10 You are right that OSS can take the lead in implementing upcoming standards. Another example is the OSS initative 52north (http://52north.org). They have already implemented the core profile of the current Sensor Observation Service specificaiton and published it as an quality assured release. 52N implements the entire set of SWE services. The SOS and the Web Notification Service (WNS) are already released, the Sensor Planning Service is currently in the 52N quality assurance process and will be published soon. The 52N Sensor Alert Service is an example how OSS initiavives can actively be involved in the desing and specification of service specifications. You are right that OSS can take the lead in implementing upcoming standards. Another example is the OSS initative 52north (http://52north.org). They have already implemented the core profile of the current Sensor Observation Service specificaiton and published it as an quality assured release. 52N implements the entire set of SWE services. The SOS and the Web Notification Service (WNS) are already released, the Sensor Planning Service is currently in the 52N quality assurance process and will be published soon. The 52N Sensor Alert Service is an example how OSS initiavives can actively be involved in the desing and specification of service specifications.

]]>