Hi Jonathan, the situation is indeed strange... I'm not sure if that filter fails to evaluate at the SQL level or in memory. Memory wise the code doing the PropertyIsEqualTo should be the same in the two cases... Try to set the logging level to "GEOTOOLS_DEVELOPER_LOGGING" and check both the generated SQL (which might on might not contain that filter, based on how complex your style is) and if there is any interesting log regarding the evaluation of the filters in memory.
Cheers Andrea On Wed, Sep 14, 2022 at 9:24 PM Jonathan D <jonathanr...@gmail.com> wrote: > I have had an issue with trying to use integer values in SLD filter > logical expressions (tested with "Or" expressions) for fields that are > floating point numbers in the database. > > For example, the following DOES match features that have a float type > "diameter" column with value "2.0" in PostgreSQL > > <ogc:Filter> > <ogc:PropertyIsEqualTo> > <ogc:PropertyName>diameter</ogc:PropertyName> > <ogc:Literal>2</ogc:Literal> > </ogc:PropertyIsEqualTo> > </ogc:Filter> > > However, the following does not match features with value "2.0": > > <ogc:Filter> > <ogc:Or> > <ogc:PropertyIsEqualTo> > <ogc:PropertyName>diameter</ogc:PropertyName> > <ogc:Literal>2.5</ogc:Literal> > </ogc:PropertyIsEqualTo> > <ogc:PropertyIsEqualTo> > <ogc:PropertyName>diameter</ogc:PropertyName> > <ogc:Literal>2</ogc:Literal> > </ogc:PropertyIsEqualTo> > </ogc:Or> > </ogc:Filter> > > I would expect Integers to be converted to floating point numbers in all > cases when the column is a float type, as in SQL where clauses. I am > converting lyrx styles into SLDs programmatically using GeoCat's > bridge-style, and the fieldValues in uniqueValueGroups that get converted > to filters are all given as string values, so I don't have a way to > determine the type of the values solely from the styling information. > > I just wanted to get thoughts before I submit a bug report. > > Thanks, > Jonathan > > _______________________________________________ > 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 > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 https://www.geosolutionsgroup.com/ http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
_______________________________________________ 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
