Reusable buyer-side registers for comparing construction-material import quotes without inventing supplier, freight, customs, tax, or compliance outcomes.
This repository is an owned distribution of selected datasets already published by LandedSpec. The linked LandedSpec HTML page is the authoritative landing page for each dataset, including its explanation, sources, professional-confirmation boundaries, and current version.
| Dataset | Use | Authoritative landing page | Download |
|---|---|---|---|
| Aluminium profile tooling and finish acceptance register | Join the controlled drawing and tool or die to the actual finishing plant, pretreatment/coating system, production batch, packing revision, and repeat-order release. | China aluminium profile pretreatment for Germany | CSV |
| Supplier document requirements list template | Build a 27-line supplier document requirements list/SDRL with milestones, formats, reviews, resubmissions, and final-dossier controls. | Supplier document requirements before deposit | CSV |
| FOB, CIF, and DAP construction quote comparison | Reconcile quote inclusions, physical handoffs, risk transfer, import responsibilities, destination charges, and buyer evidence across Incoterms® scopes. | FOB vs CIF vs DAP for construction materials | CSV |
manifest.json records each file's SHA-256 digest, byte size, row count, direct LandedSpec distribution, and HTML canonical.
datapackage.json describes the collection using the current Data Package Standard v2. It identifies all three immutable CSV release assets as tabular resources and publishes their byte sizes, SHA-256 digests, 175 total records, 43 ordered field definitions, missing-value treatment, and primary keys. This gives data tools a deterministic way to validate and load the registers without replacing the explanatory LandedSpec landing pages.
The descriptor improves machine-readable findability and interoperability. It does not represent acceptance by a data catalog, a DOI, an independent citation, or a Google ranking result.
- Treat blank,
buyer_to_confirm, and unresolved fields as unresolved—not as zero or approval. - Confirm the exact product, supplier, route, contract, customs, tax, compliance, insurance, and acceptance facts with the responsible professionals.
- The files do not recommend a supplier or origin, assign a customs code or duty, quote a freight rate, approve a shipment, or replace the official Incoterms® rules.
Incotermsis a registered trademark of the International Chamber of Commerce. LandedSpec is not affiliated with or endorsed by ICC or the source institutions named in the files.
Unless a dataset states otherwise, LandedSpec-authored selection, calculations, labels, and explanatory notes are available under CC BY 4.0. Attribute LandedSpec, link to the authoritative landing page, cite the named source dataset and date, and identify LandedSpec-added calculations or labels.
Underlying source data remains subject to its provider's rights and terms. See LandedSpec dataset reuse and source terms and LICENSE.md.
For software and research tooling, CITATION.cff provides a machine-readable collection citation. For an individual dataset, cite the title and authoritative landing page listed above.
The v2026.07.19 repository state is independently preserved by Software Heritage under the qualified persistent identifier swh:1:dir:8f1e848ada6d2288e00acaf2f4d9f25a47d24a9a;origin=https://github.com/vykut/landedspec-open-data;visit=swh:1:snp:acfc238f04fea6af66e9b73fdefd7ab584495e9f;anchor=swh:1:rev:20198a57ae4e469152178fc20a84d00a9327ed61. The archive snapshot also retains the release tag and Git revision and can generate a BibTeX citation from CITATION.cff.
This preservation record verifies an archived repository state. It does not represent an editorial endorsement, earned backlink, Google crawl, indexing, or ranking evidence.
The immutable v2026.07.19 release also publishes a complete landedspec-open-data-v2026.07.19.zip package, zenodo-metadata-v2026.07.19.json, and the reviewed datapackage.json descriptor as a separate deposit file. The ZIP preserves the tagged dataset state; the descriptor supplies machine-readable Data Package v2 schemas, missing-value rules, primary keys, hashes, licenses, and source metadata for the same three immutable CSV assets. The Zenodo metadata uses the dataset resource type, cc-by-4.0 license identifier, the three authoritative LandedSpec landing pages, the immutable GitHub release, and the Software Heritage content identifier. It validates against Zenodo's published legacy deposit schema.
This makes the frozen release ready for an authenticated Zenodo dataset deposit. It does not mean that a Zenodo record, reserved DOI, registered DataCite DOI, citation, or independent endorsement already exists. Until a DOI is published, cite the immutable GitHub release or Software Heritage identifier above.
Open a GitHub issue with the dataset filename, row or field, current source, and proposed correction. Do not include supplier quotes, prices, personal data, contracts, invoices, or other confidential commercial information. You can also use the LandedSpec corrections route.