SOS
SOS copied to clipboard
52°North Sensor Observation Service
Bumps [janino](https://github.com/janino-compiler/janino) from 3.1.7 to 3.1.8. Commits 5a872b0 Version 3.1.8 50d5b73 a9f953e Regression tests finally pass for target version 8! 85a48e6 63c8788 bd9e6a5 Disassembling of generated .class files now conditional...
Hi i have solved this issue and Requested to merge this PR **Issue / issue no. : Readme update #1240** Before ![image](https://user-images.githubusercontent.com/72294477/149815373-cf17da91-ddb5-4092-87e0-2d8bc88225c7.png) After ![image](https://user-images.githubusercontent.com/72294477/149815093-be549a27-debb-4820-bcc4-ef15ef8308fb.png)
Downloading of results from large GetObservation requests can be time-consuming, and it would be useful to provide the user with feedback on the progress of their request. One way 52N...
Add a hint that when observations are stored with a fix time offset (e.g. `+01:00`) configuration should not be set to time zones having a DST.
Hi i saw a small flaw in your [Readme.MD](https://github.com/52North/SOS#readme) file this is a link but not embedded properly Before ![image](https://user-images.githubusercontent.com/72294477/149815021-e9fa1907-55a3-4e7c-a624-bc10fc6fcb82.png)
## Problem When inserting an observation with an encoded feature of interest instance using an identifier that is already present in the SOS instance but having a different geometry, the...
I've observed a strange behaviour: if a parameter contains a comma (for example `6951 - PM2,5 GRIMM - procedure`) the KVP parser treats it like a list of identifiers. If...
Hello, We use Insertsensor, InsertResultTemplete, and InsertResult requests to insert time-series data of climate stations (52north SOS Version: 5.4.1, installed on Ubuntu 20.04 server). The station descriptions are prepared based...
One can choose between the *Default feature concept* and the *Extended feature concept* during installation. What does that mean? The description isn't really explanatory: *Select the feature concept this SOS...
It would be nice if the keys would be a little more consistent. Currently there is a wild mix of camel case, all lowercase, snake case, etc: ``` eReporting.featureOfInterest.prefix procedureDesc.ALTITUDE_UOM...