Hi all,

On trunk max number of decimals is stored on a per feature type basis, 
however its not hooked up to any of the encoders, only the global one is 
respected.

http://jira.codehaus.org/browse/GEOS-3332

Fixing is easy, however I began to think of what the behavior should be 
when the wfs query contains multiple types since the encoders only 
accept a single value for all features, not one per feature type.

I can think of a couple of different options:

1. use the minimum of all the per feature type values and the global
2. use the maximum ""
3. ignore the per feature type settings when multiple types are being 
queried and just use the global

Thoughts? Using maxFeatures as a guide it would seem #1 would be the 
most consistent. But I could also see a case made for #3 as well.

-Justin

-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to