Re: [Geoserver-users] Time dimension min/max calculations
Hi, for the web UI changes you will need to look around this classes: src/web/core/src/main/java/org/geoserver/web/data/resource/Dimension Editor.java src/web/core/src/main/java/org/geoserver/web/data/resource/Dimension EditorBase.java src/web/core/src/main/java/org/geoserver/web/data/resource/ResourceC onfigurationPage.java src/web/core/src/main/java/org/geoserver/web/data/resource/ResourceD imensionsTabPanelInfo.html src/web/core/src/main/java/org/geoserver/web/data/resource/ResourceD imensionsTabPanelInfo.java for dealing whit the values obtained from the UI you will need to look around this classes: src/main/src/main/java/org/geoserver/catalog/ResourceInfo.java src/main/src/main/java/org/geoserver/catalog/util/FeatureTypeDimensi onsAccessor.java src/wms/src/main/java/org/geoserver/wms/GetMap.java src/wms/src/main/java/org/geoserver/wms/WMS.java src/wms/src/main/java/org/geoserver/wms/capabilities/DimensionHelper .java src/wms/src/main/java/org/geoserver/wms/dimension/impl/DimensionDefa ultValueSelectionStrategyFactoryImpl.java src/wms/src/main/java/org/geoserver/wms/featureinfo/VectorRenderingL ayerIdentifier.java Hope it helps, Nuno Oliveira On Mon, 2020-02-10 at 11:33 -0500, Jason Newmoyer wrote: > I definitely like the idea of the static presentation mode. I can > create a ticket for this. If you could give a quick pointer to right > modules I'll need to touch, I can try to fit it in over the next week > or so. > > Yes the data is in PostGIS, and the time column is indexed. But I > think what's happening is that the queries happen in serial (it > appears this way by observing the postgres log). And we have about a > dozen layers that have the setting. So 12 layers generates 24 round > trips to the db for this calculation, in addition to other things it > has to do generally to produce the capabilities doc. So even though > each query is sub-second, it adds up. > > For reference, with the time dimensions turned off, our capabilities > doc takes about 1s to produce. With them all turned on, about 20- > 25s. > > Jason Newmoyer > Newmoyer Geospatial Solutions > 843.606.0424 > ja...@newmoyergeospatial.com > > > > > On Tue, Feb 4, 2020 at 6:47 AM Andrea Aime > .it> wrote: > > Hi Jason, > > do you have the data in the database? And are the dimensions > > indexed? > > If so, getting just the min and the max should be two fast queries, > > direct read from the index. > > > > Cheers > > Andrea > > > > On Tue, Jan 28, 2020 at 2:40 AM Jason Newmoyer > > atial.com> wrote: > > > I've got some WMS layers, where the underlying tables can be > > > quite large - 10M+ records. I want to enable the Time Dimension > > > capability on this layer, but what I'm finding is that GeoServer > > > will attempt to calculate min/max values when producing the > > > Capabilities doc. > > > > > > This is true, even when using Continuous Values, Use the > > > reference value, and setting a static default value. I had hoped > > > that those settings would make it skip the min/max calculations. > > > > > > Is there any way to get it to do that? > > > > > > Thanks in advance. > > > > > > Jason Newmoyer > > > Newmoyer Geospatial Solutions > > > 843.606.0424 > > > ja...@newmoyergeospatial.com > > > > > > > > > ___ > > > 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.or > > > g/comm/userlist-guidelines.html > > > > > > If you want to request a feature or an improvement, also see > > > this: https://github.com/geoserver/geoserver/wiki/Successfully-re > > > questing-and-integrating-new-features-and-improvements-in- > > > GeoServer > > > > > > > > > Geoserver-users@lists.sourceforge.net > > > 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 indica
Re: [Geoserver-users] Time dimension min/max calculations
I definitely like the idea of the static presentation mode. I can create a ticket for this. If you could give a quick pointer to right modules I'll need to touch, I can try to fit it in over the next week or so. Yes the data is in PostGIS, and the time column is indexed. But I think what's happening is that the queries happen in serial (it appears this way by observing the postgres log). And we have about a dozen layers that have the setting. So 12 layers generates 24 round trips to the db for this calculation, in addition to other things it has to do generally to produce the capabilities doc. So even though each query is sub-second, it adds up. For reference, with the time dimensions turned off, our capabilities doc takes about 1s to produce. With them all turned on, about 20-25s. Jason Newmoyer Newmoyer Geospatial Solutions 843.606.0424 ja...@newmoyergeospatial.com On Tue, Feb 4, 2020 at 6:47 AM Andrea Aime wrote: > Hi Jason, > do you have the data in the database? And are the dimensions indexed? > If so, getting just the min and the max should be two fast queries, direct > read from the index. > > Cheers > Andrea > > On Tue, Jan 28, 2020 at 2:40 AM Jason Newmoyer < > ja...@newmoyergeospatial.com> wrote: > >> I've got some WMS layers, where the underlying tables can be quite large >> - 10M+ records. I want to enable the Time Dimension capability on this >> layer, but what I'm finding is that GeoServer will attempt to calculate >> min/max values when producing the Capabilities doc. >> >> This is true, even when using Continuous Values, Use the reference value, >> and setting a static default value. I had hoped that those settings would >> make it skip the min/max calculations. >> >> Is there any way to get it to do that? >> >> Thanks in advance. >> >> Jason Newmoyer >> Newmoyer Geospatial Solutions >> 843.606.0424 >> ja...@newmoyergeospatial.com >> >> >> ___ >> 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 >> >> >> Geoserver-users@lists.sourceforge.net >> 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Time dimension min/max calculations
Hi Jason, do you have the data in the database? And are the dimensions indexed? If so, getting just the min and the max should be two fast queries, direct read from the index. Cheers Andrea On Tue, Jan 28, 2020 at 2:40 AM Jason Newmoyer wrote: > I've got some WMS layers, where the underlying tables can be quite large - > 10M+ records. I want to enable the Time Dimension capability on this layer, > but what I'm finding is that GeoServer will attempt to calculate min/max > values when producing the Capabilities doc. > > This is true, even when using Continuous Values, Use the reference value, > and setting a static default value. I had hoped that those settings would > make it skip the min/max calculations. > > Is there any way to get it to do that? > > Thanks in advance. > > Jason Newmoyer > Newmoyer Geospatial Solutions > 843.606.0424 > ja...@newmoyergeospatial.com > > > ___ > 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 > > > Geoserver-users@lists.sourceforge.net > 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Time dimension min/max calculations
Hi, GeoServer needs to know the min and max values to build the final interval (independently of the selected presentation method), even for the continuous mode it needs to know them (although I may be missing something): 2019-08-31T23:00:00.000Z/2019-08-31T23:50:00.000Z/PT1S ... the referenced value has only an effect on the default value, so the answer to your question is: no, there is no currently to skip the min and max computation. That say, thinking out loud, I see the following options: * Allow the admin to enter the min and max manually. * Allow the admin to enter the full interval manually, so a new static presentation mode. * Both of the above :-) A contribution for this is welcome. Kind regards, Nuno Oliveira On Mon, 2020-01-27 at 20:31 -0500, Jason Newmoyer wrote: > I've got some WMS layers, where the underlying tables can be quite > large - 10M+ records. I want to enable the Time Dimension capability > on this layer, but what I'm finding is that GeoServer will attempt to > calculate min/max values when producing the Capabilities doc. > > This is true, even when using Continuous Values, Use the reference > value, and setting a static default value. I had hoped that those > settings would make it skip the min/max calculations. > > Is there any way to get it to do that? > > Thanks in advance. > > Jason Newmoyer > Newmoyer Geospatial Solutions > 843.606.0424 > ja...@newmoyergeospatial.com > > > ___ > 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://w > ww.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: http://geoserver.org/co > mm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: ht > tps://github.com/geoserver/geoserver/wiki/Successfully-requesting- > and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Regards, Nuno Oliveira == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Time dimension min/max calculations
I've got some WMS layers, where the underlying tables can be quite large - 10M+ records. I want to enable the Time Dimension capability on this layer, but what I'm finding is that GeoServer will attempt to calculate min/max values when producing the Capabilities doc. This is true, even when using Continuous Values, Use the reference value, and setting a static default value. I had hoped that those settings would make it skip the min/max calculations. Is there any way to get it to do that? Thanks in advance. Jason Newmoyer Newmoyer Geospatial Solutions 843.606.0424 ja...@newmoyergeospatial.com ___ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
