/**
 * Re-throw an entity query failure as this library's own error type.
 *
 * Entity queries are answered by `@dclimate/tabular`, whose errors descend from
 * its own base class rather than `DClimateClientError`. A caller writing one
 * `catch (error) { if (error instanceof DClimateClientError) ... }` around the
 * client would therefore miss every entity failure -- so the boundary translates
 * once, here, rather than each method wrapping its own body.
 *
 * The mapping follows the distinction the rest of this library draws, by who has
 * to act: a malformed request is an `InvalidSelectionError` (the caller's to fix),
 * a well-formed request that matched nothing is a `NoDataFoundError` (an empty
 * answer, nobody's fault), and bytes that do not describe a readable dataset are a
 * `DatasetCorruptError` (the publisher's). Tabular marks the first two on the
 * error itself, so this reads a field rather than matching on message text, which
 * would break the first time a message improved.
 *
 * Transport failures are deliberately left untranslated, because they are none of
 * those three: a gateway timeout is retryable and says nothing about the dataset.
 *
 * The original message is preserved verbatim: it is the only part that names the
 * station, column, or distance that actually failed.
 */
export declare const translateEntityError: (cause: unknown) => never;
//# sourceMappingURL=errors.d.ts.map