It currently takes 6 transformers to read JSON or CSV or whatever from HTTPCaller with FeatureReader, because the http result `_reponse_body` needs to be written to an intermediate file before FeatureReader can utilize it. This is a lot of extra work when all the information needed is already present. FeatureReader should be able to take `_response_body` (or any string for that matter) as input in addition to files and urls.
Archived
FeatureReader read from directly HTTPCaller response body
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.
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.
+21- Safer
Updated idea statusGathering Interest→Archived
Idea merged into:Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.