Re: [gdal-dev] How does WMTS driver detect DataWindow?

2016-12-02 Thread Even Rouault
On mardi 29 novembre 2016 11:49:36 CET Rahkonen Jukka (MML) wrote: > With a little help GDAL picks up correct extent. Removing the erroneous > WGS84BoundingBox hint from GetCapabilities made it. > > I consider that there is a bug in the WMTS server which is advertising > invalid bounding box but

Re: [gdal-dev] How does WMTS driver detect DataWindow?

2016-11-30 Thread Rahkonen Jukka (MML)
Hi, I got to understand why WMTS service has so large WGS84 bounding box in GetCapabilities. It is because the native EPSG:3067 bounding box is first converted into WGS84 by using a densified polygon geometry. The WGS84BoundingBox is then the envelope of this warped polygon. Because of

Re: [gdal-dev] How does WMTS driver detect DataWindow?

2016-11-29 Thread Rahkonen Jukka (MML)
@lists.osgeo.org Kopio: Rahkonen Jukka (MML) <jukka.rahko...@maanmittauslaitos.fi> Aihe: Re: [gdal-dev] How does WMTS driver detect DataWindow? On lundi 28 novembre 2016 15:33:31 CET Rahkonen Jukka (MML) wrote: > Hi, > > While playing with gdal_translate and WMST my colleague

Re: [gdal-dev] How does WMTS driver detect DataWindow?

2016-11-28 Thread Even Rouault
On lundi 28 novembre 2016 15:33:31 CET Rahkonen Jukka (MML) wrote: > Hi, > > While playing with gdal_translate and WMST my colleague found that GDAL was > picking a wrong DataWindow with > > > gdal_translate > "WMTS:http://xx.yy.fi/foo/service?REQUEST=GetCapabilities=WMTS,laye > r=bar" bar.xml