Hi List,
While browsing public services, I came across a public GeoServer
instance (v2.9.1) that has this in its WMS GetCapabilities:
<CRS>EPSG:4326</CRS><CRS>CRS:84</CRS>
<EX_GeographicBoundingBox><westBoundLongitude>-180.0000036</westBoundLongitude><eastBoundLongitude>180.0000036</eastBoundLongitude><southBoundLatitude>-90.0000018</southBoundLatitude><northBoundLatitude>-59.9999988</northBoundLatitude></EX_GeographicBoundingBox>
<BoundingBox CRS="CRS:84" *minx="-180.0000036"* miny="-90.0000018"
*maxx="180.0000036"* maxy="-59.9999988"/>
<BoundingBox CRS="EPSG:4326" minx="-90.0000018" miny="-180.0000036"
maxx="-59.9999988" maxy="180.0000036"/>
The CRS:84 that's advertised has an invalid minx/maxx.
I know that EPSG:4326 and CRS:84 are the same except 4326 is lat/lon,
and 84 is lon/lat, but why is GeoServer swapping the CRS:84 values
around for explicit x/y statements?
Cheers,
Jonathan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
