search

52North / helgoland

Visual Exploration and Analysis of Sensor Web Data
Apache License 2.0
59 stars 44 forks source link

Compatibility with Sos ? #44

Open nicolas-f opened 6 years ago

nicolas-f commented 6 years ago

Hi,

I'm using a SOS endpoint named OpenSensorHub.

The getCapability url is in my case: http://192.168.1.100:8181/sensorhub/sos?service=SOS&version=2.0&request=GetCapabilities

Fetching a sensor metadata: http://192.168.1.100:8181/sensorhub/sos?service=SOS&version=2.0&request=DescribeSensor&procedure=urn:osh:sensor:simweather:B8-27-EB-74-CD-A8&procedureDescriptionFormat=http://www.opengis.net/sensorml-json/2.0

I'm not able to declare this SOS endpoint to helgoland, is it expected ?

Helgoland is querying "stations/&locale=de&service=srv_3dec8ce040d9506c5aba685c9d134156" url. But this is not SOS standard ?

Thanks

rogierc commented 5 years ago

Hi Nicolas,

Run into a similar issue. After some puzzling I solved it. Cause is confusion about different ReST-API's. Helgoland seems to use the so called Series API (see: https://52north.github.io/series-rest-api/develop/api.html )

SOS exposes this API on the /api/ path. At least on my instance.(You can see what path is used in the web.xml file) In your case the url would probably be: http://192.168.1.100:8181/sensorhub/api/

This API is different from API's exposed on the /sos or /service path's. Documentation could be more explicit about this, I think.

nicolas-f commented 5 years ago

Hi,

Yes I found out that helgoland is not OGC compatible, it needs a home made api served by 52North server.

simonjirka commented 5 years ago

Hi all,

yes, the Helgoland Viewer does not directly talk to SOS servers. The reasoning behind this is, that Helgoland was designed as a lightweight viewer, so that we did not want to do more complex tasks such as XML parsing and metadata caching directly in the web browser or on a mobile device.

Instead, SOS servers can be integrated through a separate proxy component (the server module of the Sensor Web client). This proxy connects to the SOS servers, caches their metadata and then exposes this to the Helgoland Client via the REST API.

In addition, we are currently working on an enhancement of Helgoland so that it can directly talk to OGC compliant SensorThings API instances.

Best regards Simon