Hi Jody, I have to admit that I have not had much time to follow the discussion for GeoServer 1.4 (my fault). I will take a look as soon as possible and I will also try to participate the IRC meetings.
Just a clarification, with these emails, I am trying to understand how management of features works inside geoserver, I am not focusing on WMS or WFS specifications. Assumptions made which work for features might not work for coverages (and in fact they do not work). The past versions of the WCS branch have been based on too many tricks in order to bypass problems, I personally hate that but there was no time (and not enough knowledge on our side I have to confess) to make things better. What I am trying to do now, since now I am responsible for the two branches (geoserver and geotools), is understanding clearly how the official geoserver works otherwise the time spent on the coverage branch will be wasted. Thanks a lot, Simone. On 2/20/06, Jody Garnett <[EMAIL PROTECTED]> wrote: > Simone Giannecchini wrote: > > I am ansering the two previous email from Martin. > > On 2/18/06, Martin Desruisseaux <[EMAIL PROTECTED]> wrote: > > > >> Simone Giannecchini a écrit : > >> > >>> In the getmap request, if I am right, the envelope is lon-lat > >>> regardless the crs. This means that if I request a map with SRS > >>> epsg:4326 we receive a bbox with lon first but we should internally > >>> handle with lat first. > >>> > >> If I'm understanding right, the WMS specification always put longitude > >> first. But I was at the OGC meeting last September, and the CRS working > >> group insisted loudly that the WMS specification is wrong in this > >> regards, and the official order should really be (latitude,longitude). I > >> don't know how they plan to do that. > >> > I do - for OWS-3 we did the following (after much discussion)... > > For the SRS URI: > - EPSG:4326 - traditional WMS use easting/esting > - urn:ogc:def:crs:EPSG:6.6:4979 use what the EPSG database says > > Thus the client/server can tell what is going on (if I have the 2nd uri > format wrong it is simply a mistake).... > >> I have not yet looked at RenderUtilities, but if it assumes that CRS is > >> always (longitude,latitude), than I think that RendererUtilities would > >> need to be improved. A good renderer should always work with arbitrary > >> axis order for every operations. > >> > > I think the source of all my problems is the usage of the JTS envelope > > plus epsg_wkt. The JTS envelope does not carry along a crs while the > > espg_wkt uses lon,lat instead of lat,lon. > User ReferencedEnvelope, created to solve this problem. > > of all this discussion is see if we can reamove this depency and adopt > > the GeneralEnvelope as we do in the WCS. > > > In geoapi/geoserver1.4/geotools we just created BoundingBox (extrends > Envelope) to solve this api problem ... please check a revent WMS or WFS > specification for the details. > > Jody > > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
