You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently interval searches are possible via datetime, but as written in Swagger UI "If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties."
It would be good to have the possibility to limit single intervall searches to a specific date field. Can this be defined via the URI itself? Updated, for example, is optional and created mandatory. So it makes sense to use both fields for datetime searches in general.
If a limitation via URI is not possible, where can you look up (and change) which fields are currently used for datetime searches?
Currently interval searches are possible via datetime, but as written in Swagger UI "If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties."
It would be good to have the possibility to limit single intervall searches to a specific date field. Can this be defined via the URI itself? Updated, for example, is optional and created mandatory. So it makes sense to use both fields for datetime searches in general.
If a limitation via URI is not possible, where can you look up (and change) which fields are currently used for datetime searches?
(A search limited to created field searches for string match, so you need to know the exact string, e.g.
https://wis2.dwd.de/gdc/collections/wis2-discovery-metadata/items?f=json&limit=100&created=2018-08-19T08:10:00Z )
The text was updated successfully, but these errors were encountered: