I think in this instance x just means 1st axis and y means 2nd axis.
Ian
On 11 Dec 2017 16:57, "Jonathan Moules" <jonathan-li...@lightpear.com>
wrote:
> Hi Jukka,
> It doesn't help that I bolded the wrong part. It should have been the
> miny and maxy for EPSG:4326:
>
> <BoundingBox CRS="EPSG:4326" minx="-90.0000018" *miny="-180.0000036"*
> maxx="-59.9999988" *maxy="180.0000036"*/>
>
> Because convention suggests that miny/maxy can't be above (-)90 but that
> is indeed what the WMS specification says. I was hoping they'd learnt from
> the switching lat/lon and lon/lat fiasco. Flipping the X and Y axis like
> that is just... wrong. Another edge case to try and remember.
>
> Thanks for the spot. GeoServer is indeed implementing the standard.
> Cheers,
> Jonathan
>
>
> ---- On Mon, 11 Dec 2017 13:24:46 +0000 *Rahkonen Jukka
> (MML)<jukka.rahko...@maanmittauslaitos.fi
> <jukka.rahko...@maanmittauslaitos.fi>>* wrote ----
>
> Hi,
>
>
>
> What do you mean with “explicit x/y statements?”
>
> Here is an excerpt from the WMS 1.3.0 standard, section 6.7.4:
>
>
>
> EXAMPLE 1 A <BoundingBox> metadata element for a Layer representing the
> entire Earth in the CRS:84 Layer CRS
>
> would be written as
>
> <BoundingBox CRS="CRS:84" minx="-180" miny="-90" maxx="180" maxy="90">.
>
> A BBOX parameter requesting a map of the entire Earth would be written in
> this CRS as
>
> BBOX=-180,-90,180,90.
>
> EXAMPLE 2 A <BoundingBox> representing the entire Earth in the EPSG:4326
> Layer CRS would be written as
>
> <BoundingBox CRS="EPSG:4326" minx="-90" miny="-180" maxx="90" maxy="180">.
>
> A BBOX parameter requesting a map of the entire Earth would be written in
> this CRS as
>
> BBOX=-90,-180,90,180.
>
>
>
> For me it seems that Geoserver follows the standard literally.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
> *Lähettäjä:* Jonathan Moules [mailto:jonathan-li...@lightpear.com]
> *Lähetetty:* 10. joulukuuta 2017 20:57
> *Vastaanottaja:* geoserver-users@lists.sourceforge.net
> *Aihe:* [Geoserver-users] CRS84, EPSG4326, and min/max x/y
>
>
>
> 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
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-
> requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
------------------------------------------------------------------------------
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
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
