Hi, You are right, the queries itself could be fast. I identified my SQL-View of the layer to be the problem.
When requesting the layer via WMS, the resulting SQL query made by geoserver will always contain an AND filter for the timestamp, which makes the service working fast. But when requesting capabilities, the SQL View seems not not be filtered (for obvious reasons) which then takes a lot of time. So i will discuss this with my colleagues, way may have some capacity left to develop such a feature (manual configuration) for geoserver. Maybe you could give me a hint where (files / classes) development for this should start off. Thanks, Johannes Am 31.10.2018 um 11:45 schrieb Andrea Aime: > Hi, > there is indeed no way to configure GeoServer with static time domain > values (could be done, needs coding, preventive discussion on the > devel list and then implementation according to the published > contribution rules). > However, finding min and max should be fast if you have an index on > the time column (unless the database in question is > Oracle, in that case there are fixes to speed that up on the > development branch only) > > Cheers > Andrea > > > On Wed, Oct 31, 2018 at 11:41 AM Johannes Weskamm > <[email protected] <mailto:[email protected]>> wrote: > > I have already checked that, and tried the different options, sadly it > does not change the time it takes to generate the capabilities > document. > > I tried dynamic values and also hardcoded timestamps, the result > is the > same (timeouts). > > I think geoserver is still asking the database for the min and max > values. > > > > Am 31.10.2018 um 11:28 schrieb [email protected] > <mailto:[email protected]>: > > How are you specifying the Default value strategy? > > > > If you change that to Reference Value, you can use a form like > > fromValue/toValue. It's also possible to use relative times like > > P1M/PRESENT, but note that the reference value is copied > verbatim into the > > capabilities document, which might not be what you want. > (Adapted from > > > > https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#data-web > > admin-layers-edit-dimensions) > > > > Brad > > > > > > -- > Dipl.-Geogr. Johannes Weskamm > — Anwendungsentwickler — > > terrestris GmbH & Co. KG > Kölnstraße 99 > 53111 Bonn > > Tel: +49 (0)228 / 96 28 99 -555 > Fax: +49 (0)228 / 96 28 99 -57 > > Email: [email protected] <mailto:[email protected]> > Web: https://www.terrestris.de > > Amtsgericht Bonn, HRA 6835 > Komplementärin: terrestris Verwaltungsgesellschaft mbH > vertreten durch: Torsten Brassat, Marc Jansen, > Hinrich Paulsen, Till Adams > > Informationen über Ihre gespeicherten Daten finden Sie auf > unserer Homepage unter folgendem Link: > https://www.terrestris.de/datenschutzerklaerung/ > > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before > posting to this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/geoserver-users > > > > -- > > Regards, Andrea Aime == GeoServer Professional Services from the > experts! Visit http://goo.gl/it488V for more information. == Ing. > Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di > Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 > 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it > http://twitter.com/geosolutions_it > ------------------------------------------------------- /Con > riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene > notizia. This email is intended only for the person or entity to which > it is addressed and may contain information that is privileged, > confidential or otherwise protected from disclosure. We remind that - > as provided by European Regulation 2016/679 “GDPR” - copying, > dissemination or use of this e-mail or the information herein by > anyone other than the intended recipient is prohibited. If you have > received this email by mistake, please notify us immediately by > telephone or e-mail./ >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
