Skip to main content
Archived

WMTS reader to handle HTTP errors

Related products:Transformers
  • June 25, 2021
  • 0 replies
  • 10 views

When using the new WMTS feature readers, if the service returns a 4xx or 5xx for a tile, it leaves it as blank and continues on with a warning message in the logs. When a tile returns a 200, but with unreadable content, it makes the full feature reject.

There should be an option for how to handle these errors. In my case the way a 200/invalid data tile is handled is what I would want for a 4xx or 5xx error.

I've had to create a little Lambda proxy inbetween FME server and the EMTS to make this happen.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.