sensorweb-server-helgoland
sensorweb-server-helgoland copied to clipboard
52North
Thin Web binding API to access series data.
(this issue could be also related to [restful-timeseries-proxy](https://github.com/52North/restful-timeseries-proxy) project) Is there a feature that would allow dynamic SOS instances adding? I'm aware that similar process could manually be done by...
The flexible `/extra` endpoint would be interesting to use in the following scenario: A Geonetwork catalog harvests an SOS and create ISO metadata. This ISO metadata can easily be edited...
The API is capable of providing access to different data sources, e.g. database or SOS services. For applications where a list of SOS services is dynamic, it would be useful...
Extra metadata fields can have different types (string, boolean, number). If they would be extended with an additional mime type, a client could distinguish better what the content of the...
Currently axes ordering is assumed to be lon/lat but SOS provides a setting which lets the installing person decide which axes ordering will be used. So lat/lon ordering would be...
while transforming on [a station directly](http://sensorweb.demo.52north.org/sensorwebclient-webapp-stable/api/v1/stations/sta_1fc4317a239a6afecf3df40e249d80b4?crs=4326) is working, it will not work when geometries are embedded, e.g. [in a timeseries](http://sensorweb.demo.52north.org/sensorwebclient-webapp-stable/api/v1/timeseries/ts_d5291cd0435eefaa2c2134fd0ba87f1d/?crs=31566)
I use the TS-API in combination with an SOS (see EHJ-52n/sos-uol), When requesting binary output with `.../sos/api/v1/timeseries/2/getData.png?timespan=2014-02-17T09:56:56/2014-02-17T10:12:15` I get a black screen with an error message telling me that my...
If you use the REST-API with direct access to the database, the ids in the JSON responses does not contain prefixes like ts_, sta_, pro, ... as it is done...
Preferrably [WaterML2.0](http://www.opengeospatial.org/projects/groups/waterml2.0swg) encoding ... Interesting to note here that it is currently discussed to [rename WaterML2.0 to TimeSeriesML](https://portal.opengeospatial.org/files/?artifact_id=56304) eventually.
Have a look at this entry: http://www.jfree.org/phpBB2/viewtopic.php?f=3&t=10974 A fix would just use the `FixedMilliseconds` class instead of `Seconds` ...