@nextera.one/tes-tps-bridge
v1.0.0
Published
TES-TPS Bridge — bidirectional mapping between TES resolved dates and TPS canonical coordinates
Maintainers
Readme
@nextera.one/tes-tps-bridge
TES-TPS Bridge
Bidirectional mapping between TES (Temporal Expression Standard) resolved dates and TPS (Temporal Positioning Standard) canonical coordinates.
Install
npm install @nextera.one/tes-tps-bridgeUsage
TES → TPS
import { toTPS } from "@nextera.one/tes-tps-bridge";
const result = toTPS("tes://2026/April[5^50]@10:00", {
lat: 31.9539,
lng: 35.9106,
});
// {
// kind: 'span',
// resolved: {
// startGregorian: '2026-04-05T10:00:00',
// endGregorian: '2026-05-24T10:00:00',
// startTps: 'tps://L:31.9539,35.9106/T:TPS.y28.M4...',
// endTps: 'tps://L:31.9539,35.9106/T:TPS.y28.M5...'
// }
// }TPS → TES (Point Render)
import { fromTPS } from "@nextera.one/tes-tps-bridge";
const tes = fromTPS("tps://L:31.9539,35.9106/T:TPS.y28.M5.W21.D3.H10.m00", {
year: 2026,
});
// 'tes://2026/May[20]@10:00'Rules
- TES → TPS is deterministic and canonical
- TPS → TES is guaranteed only for resolved points
- Span restore requires original TES metadata
License
MIT — Nextera.one
