On 24 June 2019 05:29:21 GMT-07:00, Ian Turton <[email protected]> wrote:
>definitely +1 from me for the idea, I'd love to help out too provided I
>don't get too bogged down on the ContentDataStore max feature/filter
>issue
>
>Ian
>
>On Mon, 24 Jun 2019 at 10:41, Andrea Aime
><[email protected]>
>wrote:
>
>> Hi all,
>> I'm writing to propose we add support for a TIME kvp parameter in all
>WFS
>> versions, mimicking
>> the existing WFS3 support, and taking into account eventual WMS time
>> settings.
>> In WFS3 one can just add a TIME query parameter and filter on that
>> dimension, while the valid
>> time range is exposed in the bbox (it's a space + time one, a novelty
>as
>> far as WFS is concerned).
>>
>> The intention is to make it easier to use time support across
>services in
>> older protocol versions,
>> so if the WMS client is already using TIME to filter data, it can use
>the
>> same off WFS by just adding a &TIME=... parameter.
>>
>> The parameter would also be exposed in the capabilites document, at
>the
>> global operations levels,
>> to allow clients to figure out its presence, but for the time being,
>> probably no time range would be exposed (not sure, might
>> not fit budget).
>> In any case, it would be possible to add that later by adding feature
>type
>> by feature type operation information
>> (which is possible, at least in WFS 1.1 onwards). In the meantime as
>a
>> work around clients could just look at the WMS caps.
>>
>> Opinions? Feedback? Anyone wants to help? :-D
>>
>> 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.*
>> _______________________________________________
>> Geoserver-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
>--
>Ian Turton
+1 one of my co-workers would have found this useful recently.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
