Justin Deoliveira ha scritto: > Gabriel Roldan wrote: >> Given the options I would say Use the maximum, using global only if at >> least one of the queried types has no numDecimals configured (is it >> Integer.MAX_VALUE in that case?). Rationale being it's the one going to >> cause least damage (ie, you may get some more decimals for a type, but >> won't loose precision for the ones with a higher numdecimals), and still >> respect the setting as much as possible? > > That is a good point, i never thought about it like that. Maximum number > does make more sense in that light.
I agree using the maximum looks like the most sensible choice, and agree on the algorithm proposed as well. >> I'm not sure what would be involved in making the encoder respect the >> settings for each one though... > Not that much work i suppose, just add a map of feature type to number > of decimals... Hmmm... interesting one. With this we would respect the user wish fully, but at the same time we'd produce a GML document that looks a little odd. If it's much more work than setting a single max let's just wait for someone to have a real need for this? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ 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
