I don't think that your issue is the same as the one you link to, that is to do with changing times to UTC before storing them, where as yours is a formatting issue. If you are storing the date as a timestamp then the formatting of the getFeatureInfo is controlled by the freemarker template. >From a quick look at the documentation ( https://freemarker.apache.org/docs/ref_builtins_date.html#ref_builtin_date_datetype) it looks like you need to use something like ${aDate?iso_utc}
Ian On Wed, 9 Sep 2020 at 08:24, Erik Böhm <erik.bo...@bsh.de> wrote: > Dear Geoserver Community, > > > > I have a problem that has already been addressed several times, but > unfortunately the solution suggested in theses threads doesn’t help solving > our problem. > > > > What I do is publishing a time enabled WMS with Geoserver 2.16.0 from a > PostGIS DB. The features are stored with an time attribute that is > formatted in the ISO date format %Y-%m-%d (2019-04-09). > > > > When calling the GetFeatureInfo, Geoserver returns the date in the > following date-time format: 4/9/19 12:00 AM. > > Looking into the GetCapabilties, I get the following for the time > dimension: > > > > <Dimension name="time" default="current" units="ISO8601"> > > 2012-09-11T22:00:00.000Z/2019-04-08T22:00:00.000Z/P1D > > </Dimension> > > > > As mentioned in other posts, when looking at the GeoJSON representation, > the format is alright. > > > > As suggested in this post > https://gis.stackexchange.com/questions/173375/date-format-in-geoserver-wms-requests-strange > , > > We set the server to local time handling, but the displayed format is > still the same. > > > > Has anyone experienced the same and has a suggestion, how we can solve > this? > > > > Thank you very much in advance! > > > > Kind regards! > > > > Mit freundlichen Grüßen > > i.A. Erik Böhm > > > > > ------------------------------------------------------------------------------------------------------------------------- > > > > [image: BSH] <http://www.bsh.de/> > > *Erik Böhm, *M4209 > > *Open Data Koordination* > > > > Tel +49-40-3190-3429 (Neue Nummer ab 1.4.20) | *erik.bo...@bsh.de > <erik.bo...@bsh.de>* > > Fax +49-40-3190-5000 > > Bernhard-Nocht-Straße 78, 20359 Hamburg > > > > Das Bundesamt für Seeschifffahrt und Hydrographie (BSH) > <https://www.bsh.de/DE/Home/home_node.html> ist eine Bundesoberbehörde im > Geschäftsbereich des Bundesministerium für Verkehr und digitale > Infrastruktur <http://www.bmvi.de/> > > > > > > > _______________________________________________ > 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 > -- Ian Turton
_______________________________________________ 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
