Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WMTS Time demo has lots of 400 Bad Request errors #6123

Open
mramato opened this issue Jan 17, 2018 · 5 comments
Open

WMTS Time demo has lots of 400 Bad Request errors #6123

mramato opened this issue Jan 17, 2018 · 5 comments

Comments

@mramato
Copy link
Member

mramato commented Jan 17, 2018

Run https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/index.html?src=Web%20Map%20Tile%20Service%20with%20Time.html&label=Showcases and open the debugger and you'll see a lot of 400 Bad Request errors. Going to one of the bad urls directly results in:

<ExceptionReport xmlns="http://www.opengis.net/ows/1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd" version="1.1.0" xml:lang="en">
<Exception exceptionCode="TileOutOfRange" locator="TILEROW">
<ExceptionText>TILEROW is out of range, maximum value is 2</ExceptionText>
</Exception>
</ExceptionReport>

@tfili any ideas? This happens without the new Resource stuff.

@tfili
Copy link
Contributor

tfili commented Jan 18, 2018

I'm wondering if the weather service only generates tiles with information. Since we don't parse the capabilities file, we just try to load every tile as if it was there even if the capabilities file says its not.

@mramato
Copy link
Member Author

mramato commented Jan 19, 2018

That sounds like a good explanation. If we think this is just a data issue, we can close it.

@ggetz
Copy link
Contributor

ggetz commented Feb 13, 2018

@lilleyse
Copy link
Contributor

lilleyse commented Feb 3, 2020

This is still a problem as of CesiumJS 1.66, no tiles get loaded in the WMTS demo.

@OmarShehata
Copy link
Contributor

I think the URL has since changed, which is why it currently isn't working: #8310

And this is fixed in this PR: #8352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants