When variable returns a timestamp, then this converter can be applied:
utc reports timestamp in UTC instead of localtime, which is default.
apm reports timestamp as local time in AM/PM style. Example "201603011123344AM" indicates "2016 March 11, 12:33:44 AM".
It could be nice to get "timestamp" as epoch-time for further processing (i.e. external db inserts, jpa etc)
epoch is OK, but it is not converter or its is?
[epoch] as template documentation states, gives us epoch timestamp of current time.
How to get unix epoch time of i.ie [th0temp-maxtime]? all I can get is "201603011123344" it does not look like epoch ts does it?
[th0temp-maxtime=epoch] would do this that is why I kindly ask for such.
By the way you save it as unix epoch ts in sqlite DB don't you? so probably there is some conversion ongoing.
Mattk, your questions are confusing me are you anyway related with meteobrige product or its me, that I cannot express the problem?
I'm wondering, would the conversion to Unix Epoch time take extra processor time compared to using [th0temp-dmaxtime.ij:--]:[th0temp-dmaxtime.kl:--] for a time expression?
I like to keep the Meteobridge workload as low as possible, and can have the website server work on getting a "hour:minutes" printed when the page is called.
