Bolla, Péter wrote: > 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? The rendering engine would set that Hints.FORCE_2D hint; and thus the DataStore would drop the excess ordinates before returning the data for rendering. The hard part for me is the handling of the CoordinateReferneceSystem ... - we really should have a CoordinateReferneceSystem of x,y,time - we really should drop down to a CoordinateReferneceSystem of x,y when FORCE_2D is applied
The CRS The editing of the data would not be effected; ie when editing the data would be requested as normal (x,y,time). Make no mistake we are going to find lots of bugs as we start paying attention to what the CRS means during editing; but it is work that is needed. Getting something on screen and visible is the first step... Jody ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
