Add an option to the TimeStamper to create a global time stamp, similar as the counter creates a global count. Also add an option to create the timestamp attribute only once for the time of the first or last feature passing the transformer. This is relevant, for example, when fanning out on a filename with a timestamp where different timestamps on the filename result in separate files.
Archived
TimeStamper: Add option for global timestamp or first/last feature time
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.
+17- Contributor
This would be very helpful. I've had the exact same case, using timestamps as fan out resulting in separate files.
I usually use a variable setter and retriever for this use case. Set the timestamp once with the first or last feature or with a creator and then use the variable retriever to pass on the timestamp to the relevant attribute used for the fanout.
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.