R/record_study_terrain_source.R
record_study_terrain_source.RdSaves one candidate, recorded-use account, or rejection in a new Study Area context. Source identity is explicitly namespaced; no catalog query, automatic matching, source download, terrain transformation or acceptance occurs.
record_study_terrain_source(
dsn,
output_file,
association_id,
artifact_id,
source_catalog,
source_record_id,
source_snapshot,
source_description,
status,
basis,
evidence,
analyst,
source_version = NA_character_,
report_file = NULL,
report_purpose = "definition"
)Existing saved Study Area context with a terrain manifest.
New context .gpkg beside dsn. Retain earlier snapshots.
Caller-supplied local claim ID. Reusing it explicitly revises status/evidence/description/attribution, not its target or source key.
Exact GeoTIFF artifact ID in the linked manifest. Its saved SHA-256 pins the derivative; availability remains a separate report finding.
Nonempty source namespace, such as WESM, USIEI, or a documented local archive namespace. No public catalog membership is required.
Exact identifier in that namespace, not an FG event ID.
Nonempty locator/reference for the metadata or archive record consulted. This is retained text, not fetched or checksum-verified.
Human-readable source/product description.
CANDIDATE, RECORDED_USE, or REJECTED. RECORDED_USE is an attributed account of use, not independently verified lineage or processing execution.
PROJECT_RECORD or OWNER_RECOLLECTION; both require evidence.
Nonempty account of support, limitations and competing claims.
Nonempty recorder attribution, not an approval signature.
Optional source edition/version; NA means unresolved. Neither a catalog ID nor a version string establishes exact source bytes.
Optional new HTML report; no fresh reference inspection is required to show saved source-use evidence.
definition (default), terrain, or staging.
List with context and report paths. Uses FLUVGEO_STUDY_CONTEXT_3; schema-1/2 contexts remain readable. Multiple sources per artifact and reuse across artifacts are supported without merging catalog identities or events. No in-file revision ledger is created. A later report failure retains the context for inspection/retry. Source products, recipes, source checksums, recoverability and cross-catalog reconciliation remain separate work.