Re: [Geoserver-users] encodeIfEmpty with string values length zero

Thanks, Gavin. Kind regards, Ben. On 24/10/17 10:21, Gavin Medley wrote: Bug report filed: https://osgeo-org.atlassian.net/browse/GEOS-8362 On Fri, Oct 20, 2017 at 3:24 PM, Ben Caradoc-Davies wrote: Gavin, that is interesting. I suspect that this situation was not

Re: [Geoserver-users] encodeIfEmpty with string values length zero

Bug report filed: https://osgeo-org.atlassian.net/browse/GEOS-8362 On Fri, Oct 20, 2017 at 3:24 PM, Ben Caradoc-Davies wrote: > Gavin, > > that is interesting. I suspect that this situation was not anticipated > (only nulls). Please file a bug report. > > Workarounds are to

Re: [Geoserver-users] encodeIfEmpty with string values length zero

Gavin, that is interesting. I suspect that this situation was not anticipated (only nulls). Please file a bug report. Workarounds are to convert empty strings to nulls in a database view or a CQL if_then_else expression in the mapping file. Kind regards, Ben. On 21/10/17 05:08, Gavin

[Geoserver-users] encodeIfEmpty with string values length zero

Hi, I am using App Schema to map to GeodesyML, a rather demanding schema in terms of validation. One of the problems I’m running into is missing child elements that are not generated by App Schema when the database field is blank. Specifically, the problem arises when the field I’m mapping