Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client support for WMS-T #161

Closed
timlinux opened this issue Jan 6, 2020 · 5 comments
Closed

Client support for WMS-T #161

timlinux opened this issue Jan 6, 2020 · 5 comments

Comments

@timlinux
Copy link
Member

timlinux commented Jan 6, 2020

QGIS Enhancement: Title

Date 2020/01/04

Author Tim Sutton (@timlinux)

Contact tim@kartoza.com

maintainer @Samweli

Version QGIS 3.14+

Summary

We already have WMS-T support for QGIS Server (see #110). This QEP relates to adding WMS-T client related functionality in QGIS desktop.

Our work is funded by a client (and we are under contract to Mapgears) and is specific in its scope to the scoping document attached.

WMS-T support is important for organisations like meteorological agencies that work heavily with time sliced data.

There were broader possibilities for time related data management (beyond WMS-T) that were considered for this work piece that were ultimately not funded by our client. In particular 4 areas that we would like to work on - please contact me if you have funding to support these:

  1. Vector layer time filtering support (similar to how time manager does it)
  2. Directories containing file stamped raster files. The files matching the active time slice will be used.
  3. Hierarchical formats such as NetCDF which may contain temporal data.
  4. Printing atlas or reports using time series.

Note also that we only considered the time dimension in WMS-T - other dimensions such as height are not proposed at this time.

@nyalldawson will be contracted to provide oversight for our work and ensure that everything gets merged smoothly.

Proposed Solution

A detailed breakdown of the proposed changes / improvements are provided in the attached PDF document.

Detailed scoping document (redacted to remove some specific client details):

WMS-T User Stories _ Use Cases _ Requirements - Version 3 - Public QEP Version.pdf

Affected Files

See context diagram in scoping doc

Performance Implications

None expected

Further Considerations/Improvements

For the project wide time slicing, we probably need some wider discussion as there are other elements to QGIS that might benefit from this.

CC @nyalldawson @saberraz

Backwards Compatibility

Only QGIS 3.12 or later will be supported

Issue Tracking ID(s)

qgis/QGIS#33539
qgis/QGIS#33321 (crash relating to refreshing WMS metadata)
qgis/QGIS#33467
More coming...

Votes

(required)

@PeterPetrik
Copy link

PeterPetrik commented Jan 6, 2020

related to #128

I think the time settings & time panel from mesh layer could be generalised in a way that could be used for all mesh/vector/raster layer with respect to #128 too

@PeterPetrik
Copy link

I think it needs to be QGIS 3.14+, not sure if you can manage to implement it in 2 weeks time?

@timlinux
Copy link
Member Author

timlinux commented Jan 7, 2020

Update: We have had a little discussion with @PeterPetrik who is suggesting we re-use or use similar approach for data input handling to that used in mesh layers:

Screenshot from 2020-01-07 08-45-19

In the detailed properties it also includes a calendar widget in the time picker.

Screenshot from 2020-01-07 08-47-56

@timlinux
Copy link
Member Author

timlinux commented Jan 9, 2020

Thanks @PeterPetrik I corrected the version target.

@elpaso
Copy link

elpaso commented Jan 9, 2020

Nice!
Just to be sure you are aware of that, WFS3/OAPIF time queries support is also implemented in QGIS Server since: qgis/QGIS#32322

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants