- Integration of Spring Data and QueryDSL
- #121 Implement next/previous values beyond requested timespan
offering
andprocedure
are now hierarchical- result time extension
- add SOS
om:parameter
tofeature
/platform
- SOS named parameters are mapped to data output
- separated project into own repository project
service
is now a full qualified entity- Support for pluralized filter parameters
- output includes href property
- more consistent filter handling
- result filtering via OData $filter
- #129 Implement Paging for DAO SPI implemenation
- #232 possibility to use
domainId
instead of database id - #251 allow offering to be full qualified parameter
- #266 observations having time intervals
- #320 register configurable timezone type
- #31 support for profile observations
- [#391](https://github.com/52North/series-rest-api/issues/391] support spatial filter for data requests
- [#161](https://github.com/52North/series-rest-api/issues/161] support alternative GeoJSON
bbox
format
- #246 no use of deleted flag in
series
table - #279 Querying multiple (time-)series causes race condition
Below v2.x
the project was part of the series-rest-api. You can find the SPI implementation by following the v1.x
development line.