OffsetBy / Temporal Layer

Apply calendar-aware time offsets to datetime values, similar to pandas datetime offset operations or SQL DATEADD(). Handles calendar complexities like varying month lengths, leap years, and daylight savings transitions.

Example operations:

Input DateTimeOffsetResult DateTimeNote
2024-01-31 12:00:00+1 Month2024-02-29 12:00:00Leap year Feb
2024-03-09 02:30:00+1 Day2024-03-10 02:30:00DST spring ahead
2024-12-31 00:00:00+1 Quarter2025-03-31 00:00:00Quarter boundary

Common applications:

  • Period-over-period analysis
  • Forward/backward date rolling
  • Time series forecasting
  • Schedule generation
  • Event planning
  • Subscription management
Table
0
0
Table

Select

column

Datetime column to apply offset to. Must be datetime type compatible with specified offset unit.

Configuration for temporal offset calculation combining operation type, time unit, and value.

Add

Arithmetic operation to apply with the offset value.

Add ~

Add offset to move forward in time. Example: +3 months from now.

Sub ~

Subtract offset to move backward in time. Example: -2 weeks from now.

Nanosecond

Time units for offset calculations. Calendar units account for real-world time complexities like DST and varying period lengths.

Nanosecond ~

Nanosecond precision (10⁻⁹ seconds). For high-precision timing and scientific data.

Microsecond ~

Microsecond precision (10⁻⁶ seconds). For system timestamps and performance metrics.

Millisecond ~

Millisecond precision (10⁻³ seconds). For application timing and user interactions.

Second ~

Second precision. For human-scale timing and basic time calculations.

Minute ~

Minute precision. Common for scheduling and duration calculations.

Hour ~

Hour precision. Handles DST transitions in calendar calculations.

Day ~

Calendar day units. Maintains same time next day, adjusting for DST.

Week ~

Calendar week units (7 days). Preserves day-of-week and handles DST.

Month ~

Calendar month units. Handles varying month lengths and year boundaries.

Quarter ~

Calendar quarter units (3 months). For fiscal and seasonal analysis.

Year ~

Calendar year units. Handles leap years and maintains month/day position.

IndexCount ~

Row index based offset. For relative position calculations in the dataset.

0

Amount to offset by in specified units. Positive integers for time shifts of any size.

Name for the new column. If not provided, the system generates a unique name. If AsColumn matches an existing column, the existing column is replaced. The name should follow valid column naming conventions.