Re: [Geoserver-users] Date parsing problem‏

On Mon, Oct 26, 2015 at 7:27 PM, okusax wrote: > Ok, I redefine the rule as dd/MM/ but the dates before 1930 now are > show > as dd/MM/00yy... > i.e: 12/01/1929 -> 12/01/0029 and 12/01/2029 -> 12/01/0029. > > feature.fc_res.value?date?string["dd/MM/"] > >

Re: [Geoserver-users] Date parsing problem‏

Ok, I redefine the rule as dd/MM/ but the dates before 1930 now are show as dd/MM/00yy... i.e: 12/01/1929 -> 12/01/0029 and 12/01/2029 -> 12/01/0029. feature.fc_res.value?date?string["dd/MM/"] In the database the comun is defined as Date (without hour and sec) Using

Re: [Geoserver-users] Date parsing problem‏

Hi, I'm not sure, but I believe there is something going on with the usage of the Freemarker built-in formatting functions. See here, the bottom of the page actually suggests not to use those built-ins with formatting patterns: http://freemarker.org/docs/ref_builtins_date.html Have you tried

[Geoserver-users] Date parsing problem‏

Hi, we have a postgres+posgis database using a column of type Date. Using geoserver we define a time.ftl for parsing and display the info in the format dd/MM/yy using ${feature.fc_res.value?date("dd/MM/yy")} but when the year is less than 1930 WMS GetFeatureInfo request returns some like