Hi Andrea, thank you for the feedback, I replied in-line: On Wed, Mar 13, 2024 at 6:32 PM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote:
> Hi Nuno, > that code you reference returns a collection, which is then used to > collect the values in another method, using heavily feature visitors to get > min/max/unique values in an efficient way: > > https://github.com/geoserver/geoserver/blob/8444491f439892aeb3ffea5de6e91e4330f798c7/src/wms/src/main/java/org/geoserver/wms/WMS.java#L1396 > > Wondering if the app-schema store is able to support those visits, some > specific points about it: > > - MappingFeatureCollectin does not seem to be able to delegate the > visit downstreams, so it will run it in memory (inefficient) > > Yes, the App-Schema PostgreSQL store (and ideally others) would need to be extended to support it. > > - The visitors are built with local attribute names, without namespace > context. Would a lookup in that condition work, against a complex feature? > > Humm, good point, I'm not sure, this could be indeed why it fails. > Cheers > Andrea > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > 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 > > > On Wed, Mar 13, 2024 at 7:19 PM Nuno Oliveira < > nuno.olive...@geosolutionsgroup.com> wrote: > >> Hi Kamilla, >> I haven't encountered a scenario where I've worked with App-Schema >> complex data alongside time dimensions, so I can't provide firsthand >> experience on that topic. >> That being said, upon reflection, I can't immediately think of a reason >> why it wouldn't work. I've checked the code where the dimension values are >> collected, and at first glance, it seems that it should function properly >> with complex features: >> >> - >> >> https://github.com/geoserver/geoserver/blob/8444491f439892aeb3ffea5de6e91e4330f798c7/src/wms/src/main/java/org/geoserver/wms/WMS.java#L1677-L1691 >> >> Hence, based on my initial assessment, I believe this functionality >> should work. However, I haven't used dimensions with complex features >> before, so it's possible that there could be an undetected bug within that >> integration. >> This situation would require a debugging session to fully understand >> what's happening. >> >> Kind regards, >> Nuno Oliveira >> >> On Tue, Mar 12, 2024 at 8:22 PM Kamilla Kisova < >> kamilla.kis...@microstep-mis.com> wrote: >> >>> Hi team, >>> >>> I've been trying to adjust an App Schema layer we have. We are trying to >>> bring this layer alive with current data, since so far it has been >>> sitting on the server with only two whole timestamps' worth of test data >>> available. >>> >>> So far we have relied on the WMS GetCapabilities to get appropriate >>> dimension information, but this time we noticed that the App Schema >>> layer's capabilities only states "<Dimension name="time" >>> default="current" units="ISO8601"/>", no matter the interval and default >>> value we set. This layer is based on a Postgres database, and I can see >>> in the configuration files that the time dimension is set appropriately, >>> very similarly to SQL views. >>> >>> Where could I find more information about App Schema stores/layers and >>> dimensions? I've tried looking around on the Geoserver documentation for >>> App Schema, but haven't found anything on the dimensions. >>> >>> Best regards, >>> Kamilla Kisova >>> >>> >>> _______________________________________________ >>> 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, >> >> Nuno Oliveira >> >> == >> GeoServer Professional Services from the experts! >> >> Visit http://bit.ly/gs-services-us for more information. >> == >> >> Nuno Miguel Carvalho Oliveira >> @nmcoliveira >> Technical Lead / Project Manager >> >> >> GeoSolutions Group >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> https://www.geosolutionsgroup.com/ >> 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 >> > -- Regards, Nuno Oliveira == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for more information. == Nuno Miguel Carvalho Oliveira @nmcoliveira Technical Lead / Project Manager GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272 https://www.geosolutionsgroup.com/ 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
