Great, thanks for the clarification guys, I knew i did not have it right.
On Fri, Dec 3, 2010 at 4:53 AM, Gabriel Roldán <[email protected]> wrote:
> It looks like EPSG ones are lat/lon for the WMS 1.3 spec.
>
> Check the following excerpt from page 16, section 6.7.3.1. My read is it
> basically says axis order shall be respected and EPSG geographic CRS's are
> latitude/longitude:
>
> "The Layer CRS has two axes, denoted x and y. The x axis is the first axis
> in the CRS definition, the y axis is the
> second axis. Depending on the particular CRS, the x axis may or may not be
> oriented West-to-East, and the y axis
> may or may not be oriented South-to-North. The WMS portrayal operation
> shall account for axis order, origin and
> direction in the Layer CRS when projecting geographic information from a
> Layer CRS to the Map CS.
>
> *Coordinates shall be listed in the order defined by the CRS *and shall be
> mapped appropriately to the Map CS i
> and j axes, *swapping axis order as needed during the projection operation
> *. Many projected coordinate reference
> systems have an axis and coordinate order other than easting, northing. For
> example, the Uniform Coordinate
> System used in Finland (EPSG:2393) orders northing before easting. *EPSG
> geographic coordinate reference*
> *systems follow ISO 6709 and always list latitude before longitude.*"
>
>
> On Fri, 2010-12-03 at 12:32 +0100, Bart van den Eijnden (OSGIS) wrote:
>
> Hi Justin,
>
> wrt axis order, the description does not seem right to me.
>
> "The WMS 1.3 spec itself only mandates support for two default geographic
> projections. Named CRS:84 and EPSG:4326 respectively. Both of these define
> the "regular" axis order of longitude, latitude or x,y."
>
> EPSG:4326 should be y,x instead.
>
> Best regards,
> Bart
>
> > Thanks for putting this up Justin. Looks very promising.
> >
> > Just a quick note, I think the ExtendedCapabilitiesProvider interface
> > getSchemaLocation() method should return multiple schema locations, and
> > it doesn't say which namespace the schema location is for, so I guess
> > you mean it returns the complete definition like in "<namespace>
> > <location>"?
> >
> > perhaps it could better be getSchemaLocation():Map<String, String> where
> > the return value maps namespaces to schema locations.
> >
> > my 2c/
> > Gab
> >
> > On Thu, 2010-12-02 at 18:31 -0700, Justin Deoliveira wrote:
> >> Hi all,
> >>
> >>
> >> Recently some fellow developers have started to look at implementing
> >> wms 1.3 support in geoserver. So I wanted to spark some design and
> >> general discussion about how to go about implementation. I wrote down
> >> some quick thoughts on this wiki page:
> >>
> >>
> >> http://geoserver.org/display/GEOS/WMS-1.3
> >>
> >>
> >> I welcome to anyone interested to chime in with thoughts, feedback,
> >> and opinions. But note that the above is still very rough and by no
> >> means complete. But the hope is with all the feedback to come up with
> >> a good implementation strategy.
> >>
> >>
> >> Also note that a few things (like axis ordering) i am still not sure I
> >> fully understand. So I am hoping those much wiser than myself can
> >> correct me where i am wrong.
> >>
> >>
> >> -Justin
> >>
> >> --
> >> Justin Deoliveira
> >> OpenGeo - http://opengeo.org
> >> Enterprise support for open source geospatial.
> >>
> >>
> >> ------------------------------------------------------------------------------
> >> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> >> Tap into the largest installed PC base & get more eyes on your game by
> >> optimizing for Intel(R) Graphics Technology. Get started today with the
> >> Intel(R) Software Partner Program. Five $500 cash prizes are up for
> >> grabs.
> >> http://p.sf.net/sfu/intelisp-dev2dev
> >> _______________________________________________ Geoserver-devel mailing
> >> list [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> >
> > --
> > Gabriel Roldan
> > [email protected]
> > Expert service straight from the developers
> >
> >
> > ------------------------------------------------------------------------------
> > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> > Tap into the largest installed PC base & get more eyes on your game by
> > optimizing for Intel(R) Graphics Technology. Get started today with the
> > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> > http://p.sf.net/sfu/intelisp-dev2dev
> > _______________________________________________
> > Geoserver-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> >
>
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for
> grabs.http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Geoserver-devel mailing
> [email protected]https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
> --
> Gabriel [email protected]
> Expert service straight from the developers
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
