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