The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
bluertopo_download() is for workflows where the durable
deliverable is the original NOAA BlueTopo source file set. The function
preserves NOAA basenames, keeps GeoTIFF and RAT sidecar files
unmodified, verifies SHA-256 checksums by default, and writes manifests
for future auditing.
plan <- bluertopo_download(
aoi,
path = file.path(tempdir(), "bluertopo-downloads"),
coverage = "fill",
dry_run = TRUE
)Dry runs return planned assets without creating the destination directory.
manifest <- bluertopo_download(
aoi,
path = file.path(tempdir(), "bluertopo-downloads"),
rat = TRUE,
verify = "sha256",
on_exists = "verify"
)Each row records the tile identifier, asset type, source URL,
destination path, verification status, SHA-256 value, attempts, and
timestamps. A fixed manifest is written at the download root for
convenience, and query-addressed manifest copies are written under
manifests/ when a query hash is available.
on_exists = "verify" reuses an existing file only when
verification succeeds. on_exists = "skip" records a skipped
file without verification. on_exists = "replace"
redownloads the asset.
bluertopo() uses the package cache for catalog files,
downloaded source assets, and VRTs. Cache roots are marked with
.bluertopo-cache.json before package-owned content is
written. The default cache is session-temporary; set
options(bluertopo.cache_dir = "/path/to/cache") when a
persistent cache is wanted.
bluertopo_cache_clear() clears only the configured
package cache. It refuses unmarked directories, suspicious roots, and
symlinked cache paths.
Downloads are currently deterministic and single-worker.
workers = NULL and workers = 1 are accepted;
higher values are rejected until bounded parallel downloads are
implemented. Individual assets still use retry/backoff behavior for
transient transfer failures.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.