The problem is that different communities came together and all of them just assumed that the axis order they had always used before was obviously the one true order that everyone agreed on, so there was no need to be specific or check with each other to make sure. By the time anyone realized there was a problem, we had plenty of legacy software to worry about.
> Really wish OGC would have never dabbled in allowing different axis > ordering. Cartesian x/y and that's it! Would have saved me a lot of > time over my career! I'm sure somebody will now explain to me the > reason after this post! > > > Jason Newmoyer > Newmoyer Geospatial Solutions > 843.606.0424 > ja...@newmoyergeospatial.com <mailto:ja...@newmoyergeospatial.com> > > > > On Fri, Oct 13, 2017 at 11:25 AM, Rahkonen Jukka (MML) > <jukka.rahko...@maanmittauslaitos.fi > <mailto:jukka.rahko...@maanmittauslaitos.fi>> wrote: > > After reading a bunch of other documents from the web I believe > that I was wrong and TopLeftCorner should really be expressed in > the official axis order and what left-to-right and what > top-to-bottom must be interpreted by looking at the SupportedCRS. > > -Jukka Rahkonen- > ------------------------------------------------------------------------ > Lähettäjä: Rahkonen Jukka (MML) > <mailto:jukka.rahko...@maanmittauslaitos.fi> > Lähetetty: 13.10.2017 18:13 > Vastaanottaja: robkhe <mailto:robinhoutmey...@gmail.com>; > geoserver-users@lists.sourceforge.net > <mailto:geoserver-users@lists.sourceforge.net> > Aihe: Re: [Geoserver-users] Incorrect coordinate axis order for a > custom tile matrix > > Hi, > > I think that you have found a bug but I am not sure where it is > exactly. > > The WMTS 1.0 standards defines the Well Known scale set > "GlobalCRS84Pixel" in CRS84 > > <TileMatrixSet> > <ows:Identifier>WholeWorld_CRS_84</ows:Identifier> > <ows:SupportedCRS>urn:ogc:def:crs:OGC:1.3:CRS84 > </ows:SupportedCRS> > <WellKnownScaleSet>urn:ogc:def:wkss:OGC:1.0:GlobalCRS84Pixel > </WellKnownScaleSet> > <TileMatrix> > <ows:Identifier>2g</ows:Identifier> > <ScaleDenominator>795139219.9519541</ScaleDenominator> > <!-- top left point of tile matrix bounding box --> > <TopLeftCorner>-180 90</TopLeftCorner> > <!-- width and height of each tile in pixel units --> > > Geoserver WMTS shows GlobalCRS84Pixel like this, using EPSG:4326 > > <TileMatrixSet> > <ows:Identifier>GlobalCRS84Pixel</ows:Identifier> > <ows:SupportedCRS>urn:ogc:def:crs:EPSG::4326</ows:SupportedCRS> > <TileMatrix> > <ows:Identifier>GlobalCRS84Pixel:0</ows:Identifier> > <ScaleDenominator>7.951392199519542E8</ScaleDenominator> > <TopLeftCorner>90.0 -180.0</TopLeftCorner> > > Geoserver is using wrong SupportedCRS but I think that is is also > giving the TopLeftCorner with wrong axis order. It is not really > explicitly written in the standard but it seems to me that the top > left corner coordinates in WMTS are not supposed to follow the > official coordinate order of the CRS. In all images and texts X is > presenting the dimension of columns (left to right) and Y is > presenting the dimensions of rows (top to bottom). See Figure 2, > Tile space on page 24 of the standard. > It can also be that those who wrote the standard knew that this > may be a difficult thing to handle and therefore there are no > examples about Lat-Lon systems not Northing-Easting ones. > > -Jukka Rahkonen- > > > > > > ________________________________________ > Lähettäjä: robkhe <robinhoutmey...@gmail.com > <mailto:robinhoutmey...@gmail.com>> > Lähetetty: 13. lokakuuta 2017 12:41 > Vastaanottaja: geoserver-users@lists.sourceforge.net > <mailto:geoserver-users@lists.sourceforge.net> > Aihe: [Geoserver-users] Incorrect coordinate axis order for a > custom tile matrix > > Hi, > > I am trying to define a custom tile grid in my Geoserver > installation, but > the axis order of the TileMatrix' TopLeftCorner elements seems > incorrect. > > I am using reference urn:ogc:def:crs:EPSG::4326, which has a lat / > lon axis > order. > However, the resulting TopLeftCorner elements inside the > TileMatrixSet use > lon / lat axis order, i.e. -180 90 (I am using world bounds for > now) instead > of the expected 90 -180. > > When I look at the predefined tile grid GlobalCRS84Pixel, which > uses the > exact same reference urn:ogc:def:crs:EPSG::4326, the coordinate > order is as > expected: 90 -180. > > Any idea why the coordinate axis order is not correct for my own > tile grid? > This can be easily reproduced by creating a tile grid for the > reference and > by entering world bounds; afterwards, you can verify the incorrect > axis > order in the capabilities. > > See also > > http://demo.luciad.com:8080/geoserver/gwc/service/wmts?REQUEST=GetCapabilities > > <http://demo.luciad.com:8080/geoserver/gwc/service/wmts?REQUEST=GetCapabilities> > => my custom tile grid is called 'test' > > Thanks! > > > > > -- > Sent from: > http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html > <http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html> > > > ------------------------------------------------------------------------------ > 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#/ > <http://www.ianturton.com/talks/foss4g.html#/> > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > <http://geoserver.org/comm/userlist-guidelines.html> > > Geoserver-users@lists.sourceforge.net > <mailto:Geoserver-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/geoserver-users > <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#/ > <http://www.ianturton.com/talks/foss4g.html#/> > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > <http://geoserver.org/comm/userlist-guidelines.html> > > Geoserver-users@lists.sourceforge.net > <mailto:Geoserver-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/geoserver-users > <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#/ > <http://www.ianturton.com/talks/foss4g.html#/> > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > <http://geoserver.org/comm/userlist-guidelines.html> > > Geoserver-users@lists.sourceforge.net > <mailto:Geoserver-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/geoserver-users > <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 > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Kevin Michael Smith <smit...@draconic.ca>
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
