Thanks for all the information. I'll have to poke around some more with this information and see if I can pinpoint the issue.
Emily Andrea Aime wrote: > Jody Garnett ha scritto: >> There is a real difference (the axis order). The WFS 1.1 DataStore >> should be able to sort things out for you; or if you transform your >> initial ReferenceEnvelope into the CoordinateReferenceSystem provided >> by the WFS it should be able to swap the data value order around so it >> all lines up correctly. >> >> The WFS 1.0 DataStore had a filter visitor that performs this kind of >> check; I am not sure if it was used for the WFS 1.1 Implementation. If >> not it is something that should be done once in the renderer (ie the >> renderer should be making the correct request). > > Hum, I believe the renderer already reprojects the rendering > bounds into whatever is the SRS advertised by the feature type > before making the query. > And it should also concatenate a reprojection when reading data > whose SRS is not equals to the one used for rendering. > Both of the above are there simply because of the standard > reprojection support, which I know works, and axis flipping is > just a particular case of CRS change. > > If this does not work there is something broke in the chain, > but without testing I cannot say if that's in the renderer > or in the datastore. > > I don't have time now, but if I had to check, I would put > breakpoints in the code to see what WFS requests are made. > Remember that WFS 1.1 has flipped axis (lat/lon order) so > a proper request has bbox corners that have x/y flipped > compared to what you'd expect in uDig. > > Cheers > Andrea > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
