**Component**: OPC-UA extractor · `EUInformation` handling

**Component**: OPC-UA extractor · `EUInformation` handling

**Current behaviour** (confirmed by Cognite): the extractor never reads `NamespaceUri` or

`UnitId` from `EUInformation`. The only value that reaches any config surface is the

composed `DisplayName: Description` string. The UNECE code is dropped before

`metadata-mapping` can see it, so `unit` / `unitExternalId` resolution to a

`CogniteUnit` from the source unit is impossible today and is not planned.

**Request**: carry `UnitId` through, and resolve the CDF `unit` direct relation from it.

**Why it matters to us**: across our fleet the `unit` direct relation is populated on

**0 of 2772** time series, while 528 of 854 at one line carry the composed string in

`sourceUnit`. The only path available is post-processing that string-matches against the

CDF unit catalogue. That is brittle in exactly the way a code-keyed lookup is not —

`kW·h: kilowatt hour` has to be parsed and matched by display text, and it will differ

by server locale, by punctuation (`kW·h` vs `kWh`), and by however each gateway's

engineer typed the description. `UnitId` is an integer-ish UNECE code designed for

precisely this lookup.

**Also useful even without resolution**: expose `UnitId` as a `metadata-mapping` source

so consumers can do the mapping themselves deterministically.