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
QGIS Server currently supports Dimensions ( TIME, ELEVATION etc.) for vector layers only and does not integrate with the (newer) temporal properties API of QGIS.
This PR exposes the temporal properties to the server: the server will expose the TIME dimension from the temporal properties to GetCapabilities and accept a TIME query string parameter to activate the time filtering.
Accepted TIME syntax
The OAPIF implementation will be used to parse the time instants and ranges:
Note that a list of instants and ranges will not be supported at this time.
Potential conflicts with defined TIME dimension
To solve the conflict, if a TIME dimension was explicitly defined for a vector layer, the temporal properties for that layer will not be activated and the explicitly set TIME dimension will be considered instead, this will solve compatibility issues with older projects.
TODO
Tests
Decide how to handle open ending/beginning interval and how to expose them in the capabilities
Expose "Default" to capabilities
Funded by: Gis3W
Commits tagged with [need-docs] or [FEATURE]
The text was updated successfully, but these errors were encountered:
Request for documentation
From pull request qgis/QGIS#48497
Author: @elpaso
QGIS version: 3.26
Server WMS temporal properties support
PR Description:
Server WMS temporal properties
QGIS Server currently supports Dimensions (
TIME
,ELEVATION
etc.) for vector layers only and does not integrate with the (newer) temporal properties API of QGIS.This PR exposes the temporal properties to the server: the server will expose the
TIME
dimension from the temporal properties toGetCapabilities
and accept aTIME
query string parameter to activate the time filtering.Accepted TIME syntax
The OAPIF implementation will be used to parse the time instants and ranges:
Note that a list of instants and ranges will not be supported at this time.
Potential conflicts with defined TIME dimension
To solve the conflict, if a
TIME
dimension was explicitly defined for a vector layer, the temporal properties for that layer will not be activated and the explicitly setTIME
dimension will be considered instead, this will solve compatibility issues with older projects.TODO
Funded by: Gis3W
Commits tagged with [need-docs] or [FEATURE]
The text was updated successfully, but these errors were encountered: