sensorweb-server-helgoland
sensorweb-server-helgoland copied to clipboard
52North
Thin Web binding API to access series data.
The supported filter parameters for th efollowing endpoints. Should be taken over to the documentation. `/samplings` - measuringPrograms - timespan (**required!**) - datasets - features - procedures - phenomena -...
Check or enable the paging for REST-API version 3.x as it was implemented in v2.x.
Bumps [commonmarker](https://github.com/gjtorikian/commonmarker) from 0.23.6 to 0.23.7. Release notes Sourced from commonmarker's releases. v0.23.7 What's Changed C API stable test by @gjtorikian in gjtorikian/commonmarker#201 Update to 29.0.gfm.7 by @anticomputer in gjtorikian/commonmarker#224...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [jfreechart](https://github.com/jfree/jfreechart) from 1.5.3 to 1.5.4. Release notes Sourced from jfreechart's releases. JFreeChart 1.5.4 Version 1.5.4 (8 January 2023) add new methods to access maps for datasets, renderers and axes...
It would be nice if all entities would support generic query parameters corresponding with their result attributes or at least for selected attributes. Here in example for the features entity...
Lacking the time to integrate the explorer, I suggest to include a minimal landing page at `/api`, so that e.g. http://sensorweb.demo.52north.org/sensorwebclient-webapp-stable/api/ contains at least the following information: - deployed software...
The service representation of v3 shows the `total` number of datasets and of the specific types (timeseries, trajectories, profiles, ...). But if you query the service with a `datasetTypes` filter,...
-> delete rendering hints from /dataset/?expanded=true Endpoint Opinions?
Loading the /stations endpoint response directly into a DesktopGIS as a valid GeoJSON document is just two changes away. 1. Make the response a Feature collection, adding a wrapping JSON-Object...
Currently the API only supports the temporal filtering for `phenomenonTime`. A solution might be to add a `referenceValue` to the `timespan` query parameter, similar to the OGC SOS 2.0 KVP...