You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are testing out a wmts service that uses standard parameters. When we add the url, Terria is able to parse the getCaps of the service, including the bounding box and all contained layers. But when we add one of the layers, each tile requested returns 404, with response like the following:
No such resource: Requested extent {"north":18785164.071364917,"south":18158991.93565275,"west":-18158991.93565275,"east":-17532819.79994059} does not overlap {"north":-4683480.73742951,"east":15997778.12490643,"south":-4688344.633945917,"west":15992914.228390023}
The tile row and column appear to be very different when we loaded it in QGIS, which was able to render the tiles correctly.
During our research, we found this ticket and thought it might be related: #5503
Any help with this would be super appreciated.
Cheers,
Alex
The text was updated successfully, but these errors were encountered:
Hi team,
We are testing out a wmts service that uses standard parameters. When we add the url, Terria is able to parse the getCaps of the service, including the bounding box and all contained layers. But when we add one of the layers, each tile requested returns 404, with response like the following:
The tile row and column appear to be very different when we loaded it in QGIS, which was able to render the tiles correctly.
During our research, we found this ticket and thought it might be related:
#5503
Any help with this would be super appreciated.
Cheers,
Alex
The text was updated successfully, but these errors were encountered: