Okay I take that back, I had to mess with the GetMapRequest object.
- setBounds( String ) and setSRS( String ) remain straight forward
- setBounds( Envelope ) now looks up an srsName, compares that with what the
server thinks that srsName means and transform the envelope as required (sigh)
On the bright side WMS client code is stable for WMS 1.1.1 and WMS 1.3.0,
irregardless of if the global forceXY hint is set.
Pull request is here:
- https://github.com/geotools/geotools/pull/39
Bugs:
- GEOT-4283 - WMS 1.3.0 GetMap Request
- GEOT-4286 CRS.toSRS handling of urn:ogc:def:crs:EPSG:4326
I did encounter one issue with CRS.toSRS( CoordinateReferenceSystem ) when
working with the longer URN syntax, it seems we had an extra ":" in the String,
which we could not decode? Checking the internets
(http://www.oostethys.org/best-practices/best-practices-ogc-urns)
Shows:
urn:ogc:def:crs:EPSG:6.5:4326
urn:ogc:def:crs:EPSG:6.15:4326
urn:ogc:def:crs:EPSG::4326
So I think we have the opposite problem, we are correctly making the SRS - but
we are unable to parse the more general format (where database version not
mentioned):
With global forceXY hint, when I parse:
- EPSG:4326 - XY order as expected
- urn:ogc:def:crs:EPSG:4326 --> CoordianteReferenceSystem EPSG database order
(what I want)
- urn:ogc:def:crs:EPSG::4326 --> CoordianteReferenceSystem with XY order
(unexpected)
--
Jody Garnett
On Thursday, 11 October 2012 at 11:00 PM, Jody Garnett wrote:
> Small update Andrea:
>
> The request object and response object are escaping unmodified, so cascading
> WMS is unchanged.
>
> What is changing is:
> 1) The GetCapabilities Layer information (it now reflects what the server
> provides, even if the global forceXY is on)
> 2) The Layer.getEnvelope( CoordinateReferenceSystem) method used to calculate
> a request for a client
>
> The getEnvelope code was blindly matching on identifier and copying the
> values into a GeneralEnvelope, using CRS.transform( envelope, crs ) give it a
> chance
> to notice if the axis are the other way around and swap the values
> accordingly.
>
> --
> Jody Garnett
>
>
> On Wednesday, 10 October 2012 at 10:01 PM, Andrea Aime wrote:
>
> > On Wed, Oct 10, 2012 at 9:44 AM, Jody Garnett <[email protected]
> > (mailto:[email protected])> wrote:
> > > Just a heads up that I am doing a QA run on the gt-wms client module. I
> > > have a couple of days to get WMS 1.3.0 support up and going.
> > > I know GeoServer cascading WMS was using it … anyone else?
> > >
> > > I am being careful to only change functionality for Version 1.3.0 - so
> > > far all the issues have been around axis order (as expected)
> > >
> > >
> > >
> >
> >
> > GeoServer had troubles cascading WMS 1.3 at the beginning, but we made
> > fixes to that and last time I checked
> > it seemed to be working.
> > Just tried cascading
> > http://demo1.geo-solutions.it/geoserver/ows?service=wms&version=1.3.0&request=GetCapabilities
> > in a local GeoServer, specifically the "geonetwork:world" layer, it appears
> > to be working fine here?
> >
> > Cheers
> > Andrea
> >
> >
> >
> > --
> > ==
> > Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
> > information.
> > ==
> >
> > Ing. Andrea Aime
> > @geowolf
> > Technical Lead
> >
> > GeoSolutions S.A.S.
> > Via Poggio alle Viti 1187
> > 55054 Massarosa (LU)
> > Italy
> > phone: +39 0584 962313
> > fax: +39 0584 1660272
> > mob: +39 339 8844549
> >
> > http://www.geo-solutions.it
> > http://twitter.com/geosolutions_it
> >
> > -------------------------------------------------------
>
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
