Re: [Geotools-gt2-users] Failed to execute request to WMTS

Roar: I think you could also try patching geotools to be forgiving in this case. -- Jody Garnett On Mon, Dec 5, 2022 at 7:07 AM Roar Brænden wrote: > Hi, > > I've looked more into how to handle this irregular capabilities document > within GeoTools, and found a solution that works without cont

Re: [Geotools-gt2-users] Failed to execute request to WMTS

Hi, I've looked more into how to handle this irregular capabilities document within GeoTools, and found a solution that works without contacting NASA. It isn't the prettiest thing, but it works. The main point is to make a custom WMTSConfiguration that overrides the binding for positiveInteger.

Re: [Geotools-gt2-users] Failed to execute request to WMTS

Looking further into this specific service, apparently this WMTS capabilities document is generated by a Lua script that just copies the width and height values from a YAML configuration file, without making sure the resulting capabilities valid according to the WMTS schema. The Lua code is he

Re: [Geotools-gt2-users] Failed to execute request to WMTS

XML Schema says Capabilities are invalid.                                                          Width (in pixels) of the legend image                                                                                            Height (in pixels) of

Re: [Geotools-gt2-users] Failed to execute request to WMTS

But that's for the legend image (and again probably should be an integer) - I can't think of any reason why the WMTS reader would be using that. You really need to turn logging up to fine or finest and see how it is getting there. Ian On Wed, 30 Nov 2022 at 14:55, Roar Brænden wrote: > Hi, > >

Re: [Geotools-gt2-users] Failed to execute request to WMTS

Hi, It seems like this height=85.5 is coming from the capabilities document. Here for instance: default default Re: [Geotools-gt2-users] Failed to execute request to WMTS

2022-11-30 Thread Ian Turton

Height is in pixels and is an integer value so your value of 85.5 is a problem, your code example doesn't show how you are generating the size request but I would expect a height/width of 255 or 512 for a WMTS request. It's possible that the GeoTools WMTS code doesn't understand the TIME dimension