It would be better if we have a range value in SchemaMapper filters. The request is explained well in the following link
https://knowledge.safe.com/questions/50554/schemamapper-attributerange.html
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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 a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.
+6Hi Navaneet!
We're revisiting the SchemaMapper over here, to see how we might be able to shave down it's long tooth. In digging into this transformer, it's evident there are a lot of questions about what exactly a new-n-improved SchemaMapper looks like. We're beginning to look at supporting simple functions and conditionals but still need to investigate/verify the following:
- Which functions and conditionals would be used? What would be helpful?
- Would these statements be specified in the external lookup table, the configuration fields, or apply to the incoming feature values themselves?
- What kind of UI help would the author expect for writing these statements?
Any and all feedback welcomed on these above points, if you would be game to share! I would greatly appreciate it!
Cheers,
Annabelle
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.