% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/bdsolos.R
\name{inspect_bdsolos_csv}
\alias{inspect_bdsolos_csv}
\title{Diagnostic inspection of a BDsolos CSV before loading}
\usage{
inspect_bdsolos_csv(path, sep = NULL)
}
\arguments{
\item{path}{Path to the CSV downloaded from BDsolos.}

\item{sep}{Field separator (default \code{","}; some BDsolos exports
use \code{";"} or tab).}
}
\value{
Invisibly, a list with \code{mapped}, \code{unmapped},
        \code{munsell_present}, \code{taxon_column}.
}
\description{
Reads the CSV header, attempts to map each column to the soilKey
horizon schema via \code{\link{.bdsolos_match_column}}, and prints
three sections:
}
\details{
\itemize{
  \item \strong{Mapped columns} -- BDsolos name -> soilKey name
  \item \strong{Unmapped columns} -- columns the loader will ignore
        (review these before running \code{load_bdsolos_csv} to make
        sure no critical attribute is silently dropped)
  \item \strong{Munsell coverage} -- whether matiz / valor / croma
        are present in either umido or seco variants
}

Run this before \code{\link{load_bdsolos_csv}} on any new CSV from
BDsolos, especially if the export schema looks unfamiliar (BDsolos
has shipped multiple schema versions over the years).
}
