Ports and logistics hubs are where road, sea and handling interlock in one place. Aggregate each mode with a different methodology and a different system, and the same cargo gets counted again across systems — inflating or dropping the total.
The problem is boundaries and duplication. With no way to identify the same activity counted once in trucking and again at handling, the hub’s total emissions cannot be trusted. The more modes, the more the error compounds.
The LCS API calculates every transport mode under a single ISO 14083 methodology. The same activity is sealed with a record_hash so it is never counted twice, and boundaries between modes are defined explicitly. The whole hub sits on one rule.
The result is one ledger with no double counting. Road, sea and handling sum under the same methodology, so the same source-of-truth serves both hub-level reporting and per-mode breakdowns.
AS-ISNo measurement · estimatedTO-BEMeasured · transformedDrag to compareFrequently asked
The same activity is assigned the same hash. Even when records arrive from different modes or systems, overlapping hashes are sealed into one — so the same cargo is never aggregated twice.
LCS takes activity data over API and calculates it under a single methodology. The goal is to unify the calculation layer without tearing out existing systems.