Timestamp Epoch Offset Transform
Translate integer timestamps between explicitly supplied epoch origins expressed in the same units; no calendar or leap-second conversion.
Description
Translate integer timestamps between explicitly supplied epoch origins expressed in the same units; no calendar or leap-second conversion.
Changing an integer timestamp's epoch changes its offset while preserving the represented instant in common units.
When to use this tool
Translate integer timestamps between explicitly supplied epoch origins expressed in the same units; no calendar or leap-second conversion.
- Prepare the supplied timestamp, sourceEpoch, targetEpoch fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter timestamp, sourceEpoch, targetEpoch. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.timestamp. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse timestamp, sourceEpoch and targetEpoch as exact signed decimal integers. Return timestamp+sourceEpoch-targetEpoch as decimal text.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| timestamp | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| sourceEpoch | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| targetEpoch | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.timestamp | The timestamp value under the stated formula or text convention. |
{
"input": {
"timestamp": "10",
"sourceEpoch": "100",
"targetEpoch": "50"
},
"output": {
"result": {
"timestamp": "60"
}
}
}Limitations and assumptions
- All three must already use the same unit and absolute epoch reference. No named epoch, timezone or timescale is looked up.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Keep elapsed durations, circular clocks, calendar months and epoch offsets distinct. Use a date/time method with explicit timezone and timescale rules for dated instants; arithmetic on one representation does not supply the others.
References
Similar or alternative tools
- Calendar Quarter Month Offset
Locate an ordinary calendar month within its calendar quarter; zero-based month offset, not a fiscal-quarter mapping.
- Clock Offset with Day Carry
Offset civil seconds of day and retain signed day carry; no time-zone transitions or date interpretation.