Thanks for the info Christian, I assume you replied directly to me by accident so re-including the list.
My initial thought was that there would be just one "time column" composed of discrete timestamps, or at least that is the use case I currently have. I am also kind of going off of what the core mosaic reader does and unless I am mistaken (which is very possible to someone please let me know :) ) there is just a single time attribute for each entry of the mosaic and you can specify the time resolution to essentially create an interval. That said a start/end date also makes sense to me. I haven't started digging into the code yet but I will keep this in mind in the approach and perhaps add support for both modes if people think that makes sense? Thanks! On Sun, Nov 18, 2018 at 10:09 AM Christian Mueller < christian.muel...@os-solutions.at> wrote: > Hi Justin and Andrea > > Sorry for the late reply. IMHO it would make sense to add the business > time support as described in SQL 2011. At the end of the day you need 2 > attrilbutes of type DATE, one for the start and one for the end. (The open > end may be something like 2999-12-31). The important issue is that the > start date is included in the time period and the end date is NOT included. > > I know about support in DB2 and Oracle, Postgres provides an intervall > data type, and I think Andrea mentioned MS Sqlserver some time ago. > > Just my 2 cents. > > > > > > On Sun, Nov 18, 2018 at 6:04 PM Christian Mueller < > christian.muel...@os-solutions.at> wrote: > >> Hi Justin and Adrea >> >> Sorry for the late >> >> >> On Wed, Nov 14, 2018 at 9:14 PM Justin Deoliveira <jdeol...@gmail.com> >> wrote: >> >>> Ok great. Thanks for the info Andrea! >>> >>> On Wed, Nov 14, 2018, 11:57 AM Andrea Aime <andrea.a...@geo-solutions.it >>> wrote: >>> >>>> On Tue, Nov 13, 2018 at 5:30 PM Justin Deoliveira <jdeol...@gmail.com> >>>> wrote: >>>> >>>>> One thing you could help me with is a quick sanity check on the >>>>> approach. I was basically just planning to add a "timeAttribute" element >>>>> to >>>>> the mapping file, and when present have the coverage reader declare the >>>>> appropriate metadata in support of the time domain. Let me know if you >>>>> think that is the wrong way to go. >>>>> >>>> >>>> Sounds reasonable to me. The situation now is a bit fluid, there are >>>> some methods accessing dimension domains >>>> that use the StructuredCoverageGridReader interface to allow for >>>> certain database optimizations, but the metadata >>>> entries are still supported and in some cases they are the only ones >>>> still used. >>>> >>>> Some examples of both approaches in this class: >>>> >>>> https://github.com/geoserver/geoserver/blob/2e681e2a74f0754e294bbb481ecf7ad33552b3e6/src/main/src/main/java/org/geoserver/catalog/util/ReaderDimensionsAccessor.java >>>> >>>> Cheers >>>> Andrea >>>> >>>> == >>>> >>>> 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.* >>>> >>> >> >> -- >> DI Christian Mueller MSc (GIS), MSc (IT-Security) >> OSS Open Source Solutions GmbH >> >> > > -- > DI Christian Mueller MSc (GIS), MSc (IT-Security) > OSS Open Source Solutions GmbH > >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
