Hi there, how are you guys doing? Just came across what looks like a strange behavior, and wanted some input from you guys.
Whenever I do a WMS GetCapabilities request using version=1.3.0 (the default), I see that the BoundingBox for CRS=EPSG:4326 has swapped axis ordering. I'm looking at GeoServer 2.2.3 now, but I've seen this same behavior also on 2.1.1, 2.1.3, etc. For example, for the "tasmania" layer group we get this info: <EX_GeographicBoundingBox> <westBoundLongitude>143.83482400000003</westBoundLongitude> <eastBoundLongitude>148.47914100000003</eastBoundLongitude> <southBoundLatitude>-43.648056</southBoundLatitude> <northBoundLatitude>-39.573891</northBoundLatitude> </EX_GeographicBoundingBox> <BoundingBox CRS="EPSG:4326" minx="-43.648056" miny="143.83482400000003" maxx="-39.573891" maxy="148.47914100000003"/> As you can see, "minx" here is not equal to the <westBoundLongitude> value (as I think it should), but to the <southBoundLatitude> value. Funny enough, the response when specifying WMS version = 1.1.1 works looks OK: minx corresponds to minimum longitude there. So my question is: is this a bug, or is this some weird change in the 1.3.0 spec? I did see a related bug in the JIRA (http://jira.codehaus.org/browse/GEOS-4283), but I think this is something else. Cheers, Milton -- Milton Jonathan Grupo GIS e Meio Ambiente Tecgraf/PUC-Rio Tel: +55-21-3527-2502 ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
