/**
 * GMW (Grondwatermonitoringput / groundwater monitoring well) resolvers.
 *
 * The GMW registration object is array-heavy: a well has one or more
 * {@link MonitoringTube}s (each with optional geo-ohm cables and electrodes) and
 * a chronological log of {@link GMWIntermediateEvent}s. These resolvers turn
 * those repeating subtrees into typed arrays; the flat scalar fields are bound
 * directly in `gmw-schema.ts`.
 *
 * Every leaf path here is derived from the official dsgmw/1.1 XSD (verified with
 * `npm run check:xsd-coverage`).
 */
import type { ResolverContext, MonitoringTube, GMWIntermediateEvent } from "../types/index.js";
/**
 * Parse all monitoring tubes of the well.
 *
 * Bound with `xpath: "."` so the resolver receives the registration-object node
 * and iterates its `dsgmw:monitoringTube` children. The XSD's `materialUsed`,
 * `screen`, `plainTubePart`, `sedimentSump` and `insertedPart` sub-structures are
 * flattened onto each tube.
 */
export declare function processMonitoringTubes(_value: string | null, context: ResolverContext): Array<MonitoringTube>;
/**
 * Parse the well's intermediate-event log (what changed after construction).
 *
 * Only the event identity (name + date) is exposed. The XSD's per-event
 * `eventData` diff is intentionally not expanded: the changed properties are the
 * same fields modelled on {@link MonitoringTube} / the well itself, and the
 * current-state values are already available there.
 */
export declare function processIntermediateEvents(_value: string | null, context: ResolverContext): Array<GMWIntermediateEvent>;
/**
 * Parse the broIds of borehole-research objects (CPT/BHR) surveyed at this well.
 * The `broId` leaf sits under a namespace-varying wrapper, so match by local name.
 */
export declare function processSurveyBoreholeResearchIds(_value: string | null, context: ResolverContext): Array<string>;
//# sourceMappingURL=gmw-resolvers.d.ts.map