Hello, my name is Chris and I am new to the 52
North community and to SWE in general.
My first question relates to real time data streaming.
Specifically, what is the best practice for streaming real time
video ? We currently have a camera that uses a separate streaming
server, however it is outside the SWE architecture. Is there a
better way to be more "compliant" with the SWE/OGC set of
standards and make use of 52 North's open source software?
Christopher Parent wrote:
> My first question relates to real time data streaming. Specifically,
> what is the best practice for streaming real time video ? We currently
> have a camera that uses a separate streaming server, however it is
> outside the SWE architecture. Is there a better way to be more
> "compliant" with the SWE/OGC set of standards and make use of 52 North's
> open source software?
welcome to SWE mailinglist ;).
Do you want the streaming server to be available within the sensor web
by just offering live video data? Or will the server offer also bygone
data (a video database)?
However, 52North offers more than one solution for dealing with video
data, dependent to how your components look like, of shall behave.
1) The Sensor Planning Service for which we developed a video camera
plugin for a taskable network camera.
In fact, you task the camera (pan/tilt/zoom) via SPS and get the
data directly from the camera (a streaming server would also be
possible) via ResultAccessURL, which can be requested from the SPS
via the DescribeResultAccessRequest. Similary, you can register a
camera instance (for your specific camera plugin) with the streaming
server as the appropriate result access.
2) 52North has developed an Video on Demand SOS (VOD) as a proof of
concept to store video data in an SOS. However, this VOD was used
within the OWS-6 and OWS-7, so it was already applied in a broader
context. The SVN repository is at
The VOD uses a Berkeley Java database, but you can use your own
backend via implementing the DAO interfaces of the service.
ATM there are two branches (the trunk and one branch). Think of the
trunk as the proof of concept VOD and the 2010-03_OWS7_VOD branch as
the line of development which we will follow in the future.
However, both are different in how they offer video data. The VOD in
the trunk offers video via SDP (with HTTP and RTP/RTCP streaming),
the 2010-03_OWS7_VOD offers only HTTP streaming. However, the branch
offers a much better extensibilitiy for metadata, so we will follow
that branch by adding the functionality of the trunk by and by, and
put that line of development in the trunk in the end.
Unfortunately, the VOD lacks up-to-date documentation (installation
and Twiki). However, there is one (a bit outdated) documentation in
the trunk. Plese let me know, when you get stuck installing the VOD.
Within the Mobile Sensor Platform, we also put both services together.