Jody Garnett wrote: > Oh! We have actual progress to report on that front; I have been trying > to let GeoServer work with 3D data; and one of the optimizations Andrea > asked for was the ability to throw away any data beyond X and Y (since > it was not going to be used for rendering). > > Thus was born the Hints.FORCE_2D - so if your datastore can support this > hint (which is used by the renderer) we should be able to cut off the > data before the render gets confused.
So this would be a hint for the DataStore, and if this hint is present, then the DS would drop the coordinates by itself? That's one of my ideas too :) This way presenting the data would work, but you would not be able to edit it. Or the does the rendering engine drop the excess ordinates? Peter ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
