[Geoserver-devel] Configuring WMS-Time range for capabilities document

[Johannes_Weskamm]

Dear list,

I am planning to integrate an option in the "Dimensions" Tab of the layer properties where one can configure a static start and end datetime.

Discussion on that topic happend back in 2018 on the users list (same subject), and now is the time to do the work

Reason for the change is that on some layers that are based on complex database views or inefficient tables, calculating of the min and max values of the time range geoserver does when generating the capabilities document takes a lot of time (several minutes in some cases), often resulting in timeouts.

So the plan is the following:

When the "Time Enabled" checkbox ist ticked, a new checkbox will appear in the time settings, named something like "configure static start / end values".

When checked, two additional form fields will be available to specify start and end (datetime).

Those will then be used to generate the information for the capabilities document, of course still respecting the other settings like interval etc.

The automatic detection of start and end values geoserver does at the moment will then be skipped in that case, which in turn should generate the capabilities nearly instantly.

Any objections on this?

Development is going to start next week, so any feedback is welcome.

Greetings,

Johannes

--
Dipl.-Geogr. Johannes Weskamm
   — Anwendungsentwickler —

   terrestris GmbH & Co. KG
   Kölnstraße 99
   53111 Bonn

   Tel: +49 (0)228 / 96 28 99 -51
   Fax: +49 (0)228 / 96 28 99 -57

   Email: weskamm@anonymised.com
   Web: https://www.terrestris.de

   Amtsgericht Bonn, HRA 6835
   Komplementärin: terrestris Verwaltungsgesellschaft mbH
   vertreten durch: Torsten Brassat, Marc Jansen
      Informationen über Ihre gespeicherten Daten finden Sie auf
   unserer Homepage unter folgendem Link:
   https://www.terrestris.de/datenschutzerklaerung/

[Richard_Duivenvoord1]

Oe, oe, can I make a FeatureRequest

Is it an idea to (also?) make an option to set the enddate to 'now'? (or maybe better: if left out, it defaults to 'now')

I'm working with rather large datasets (measurements) which keep on growing, and it would be useful to just always have the data "up onto now"...

Most wms-t clients I know base the time slider start and end on timerange from the capabilities document, so having a 'live' database, it's hard to set a 'static' end-time...

Regards,

Richard Duivenvoorde

On 9/15/22 10:54, Johannes Weskamm wrote:

Dear list,

I am planning to integrate an option in the "Dimensions" Tab of the layer properties where one can configure a static start and end datetime.

Discussion on that topic happend back in 2018 on the users list (same subject), and now is the time to do the work

Reason for the change is that on some layers that are based on complex database views or inefficient tables, calculating of the min and max values of the time range geoserver does when generating the capabilities document takes a lot of time (several minutes in some cases), often resulting in timeouts.

So the plan is the following:

When the "Time Enabled" checkbox ist ticked, a new checkbox will appear in the time settings, named something like "configure static start / end values".

When checked, two additional form fields will be available to specify start and end (datetime).

Those will then be used to generate the information for the capabilities document, of course still respecting the other settings like interval etc.

The automatic detection of start and end values geoserver does at the moment will then be skipped in that case, which in turn should generate the capabilities nearly instantly.

Any objections on this?

Development is going to start next week, so any feedback is welcome.

Greetings,

Johannes

[Richard_Duivenvoord1]

Oe, oe, can I make a FeatureRequest

Is it an idea to (also?) make an option to set the enddate to 'now'? (or maybe better: if left out, it defaults to 'now')

I'm working with rather large datasets (measurements) which keep on growing, and it would be useful to just always have the data "up onto now"...

Most wms-t clients I know base the time slider start and end on timerange from the capabilities document, so having a 'live' database, it's hard to set a 'static' end-time...

Regards,

Richard Duivenvoorde

(ps resending this message)

On 9/15/22 10:54, Johannes Weskamm wrote:

Dear list,

I am planning to integrate an option in the "Dimensions" Tab of the layer properties where one can configure a static start and end datetime.

Discussion on that topic happend back in 2018 on the users list (same subject), and now is the time to do the work

Reason for the change is that on some layers that are based on complex database views or inefficient tables, calculating of the min and max values of the time range geoserver does when generating the capabilities document takes a lot of time (several minutes in some cases), often resulting in timeouts.

So the plan is the following:

When the "Time Enabled" checkbox ist ticked, a new checkbox will appear in the time settings, named something like "configure static start / end values".

When checked, two additional form fields will be available to specify start and end (datetime).

Those will then be used to generate the information for the capabilities document, of course still respecting the other settings like interval etc.

The automatic detection of start and end values geoserver does at the moment will then be skipped in that case, which in turn should generate the capabilities nearly instantly.

Any objections on this?

Development is going to start next week, so any feedback is welcome.

Greetings,

Johannes