Hi Mark, I left out the "Z" only in writing the examples in the mail: actually you can't even use time without "Z" notation in GetMap request because GeoServer rises an error. I also know that millisecond is the max resolution supported, perhaps I've created a misundestanding writing "accuracy less than a millisecond". Since it's an accuracy, a hundredth of second for me is "less" than a millisecond, though it's greater as pure number.
But that's not the point: I think there is a trivial error in parsing the decimal part of the time value. A fraction of second like ".27" is transformed in ".027" rather than ".270". Ciao, Stefano On Wed, Sep 4, 2019 at 1:12 PM mark <mc.pr...@gmail.com> wrote: > On 9/1/19 8:28 PM, stefano pezzi wrote: > > Hi list, > > > > I found what it may be a bug in the code that GeoServer uses to > > transform a reduced accuracy time query into a time range query when > > executing a WMS request with TIME dimension. > > > > If so, it would be surely a minor issue since it deals with millisecond, > > but in certain application fields even milliseconds matter. > > > > I have a v.11 PostGIS DBMS with GeoServer v.2.15.2 running inside a > > Tomcat v.9.22 in a OpenJDK Java v.11. Time dimension is specified with > > two fields (start and end time) of timestamptz data type. > > > > When you specify, in a WMS query, a value for the TIME parameter that > > has a reduced accuracy (less than a millisecond), > > the max resolution you can use is milliseconds as noted in the docs: > https://docs.geoserver.org/latest/en/user/services/wms/time.html > > Note that is you leave out the Z at the end of your time argument the > rules of reduced accuracy apply. > > -M > > > > _______________________________________________ > 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 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
