In the early 52°North days, we managed our source code on a public open source platform: SourceForge. We started with CVS (classic!), switched to SVN (wow, I can delete folders!) and after a while we decided to host all 52°North related source code in our own IT environment. However, keeping an eye on what was going in the VCS world, we felt that this approach was outdated and started to look into Git and GitHub. This initiative was mainly driven by 52°North staff developers’ curiosity and the promise of a better development work flow. We found GitHub provided very easy collaboration, communication and outreach dedicated to source code and very much in line with the 52°North philosophy. After a few test runs, we started to migrate the first of our active software projects to GitHub.
more >
A look into WPS branches – Today: Conflation with Provenance
The 52°North WPS implementation shares one important property with the specification – it is very flexible and can be used for many different use cases. A number of parties contribute, which results in a number of active development branches for code. We present a selection in blog posts in the series “A look into WPS branches”.
Conflation With Provenance – Custom WPS Processes
Similar to the efforts on Aviation-specific processing, 52°North developed processes for conflating two distinct data sets in the scope of the OWS 9 test bed. This article sheds some light on the details of the processes and the obstacles which need to be overcome.
Conflation is understood as a sophisticated process of unifying two or more separate data sets that share certain characteristics into one integrated all-encompassing dataset. In the process, different representations of a feature get folded into one feature. That target feature follows a particular model that is used to capture complementary information. In addition to the actual dataset conflation, the consistent capturing of provenance information was another goal of the project. The conflation processes developed represent a very customized and complex workflow. The test bed proved that the 52°North WPS framework fits perfectly into such use cases by providing an individual and flexible processing API.
A look into WPS branches – Today: Aviation
The 52°North WPS implementation shares one important property with the specification – it is very flexible and can be used for many different use cases. A number of parties contribute, which results in a number of active development branches for code. We will present a selection in blog posts over the next few months.
Processing for Aviation data.
In the scope of the overall succesful OWS-9 testbed 52°North developed a set of processes to support Client software settled in the Aviation domain. This article provides an overview on these processes and common use cases.
Aviation service architectures are naturally highly distributed service-oriented architectures. Common data is provided through Web Feature Services (WFS), updates on data can be obtained through Event Services (ES). All of these are made available through dedicated registries such as the Catalogue Service for the Web (CSW). Starting with OWS-9, the Aviation thread decided to integrate Web Processing Services into this heterogeneous service landscape. The WPS has been identified to provide support for classic Client use cases such as identifying certain airspaces which intersect a flight route (performed by pilots and flight dispatchers).
52°North Sensor Event Service 1.1.0 released
The Sensor Web community has released version 1.1.0 of the 52°North SES. This release introduces additional functionality and fixes several known problems.
New features include:
- Implemented Stored Filters for easy reusability of subscriptions (see Capabilities and WSDLs)
- Switched default Consumer Notification to usage of Apache HttpComponents HttpClient 4.x (embedded in OXF, including connection pooling)
- New mechanism to define the used Notification Parsers in the configuration file. This enables support for external parsers (implemented against the API)
- externalized SES/EML XML bindings (to OXF)
- migrated from Apache Muse to 52North amused (fork of Muse)
- Improved WSDL descriptions, now allows fully access to all operations through the WSDL definitions
- (Meta Feature) introduced Integration Testing to provide an improved stable service
The binary release including the complete sources can be obtained through our downloads page. A detailed changelog including a list of bugfixes is provided.