Request for public metadata: Argoverse 2 Map Change Dataset

[bnucougar]

Hello Argoverse team,

We are conducting a metadata-only, fail-closed audit of the Argoverse 2 Map Change Dataset for an academic traffic-data validation study. We are not requesting dataset files or payload access. Public documentation links or a metadata-only response are sufficient.

Could you please point us to the authoritative public source for the following fields, or state NOT_AVAILABLE where a field is not published?

1. Release — exact dataset release/version, record date, and canonical release/download page.
2. License/rights — exact data license text or URL, non-commercial and attribution requirements, registration/access conditions, and redistribution restrictions.
3. Artifact manifest — official file list, filenames, byte sizes, and any documented archive/member structure.
4. Checksums — official algorithm, per-file digests, and checksum-manifest URL; if no official release digest is published, please state that explicitly.
5. Named task and estimand — official map-change task definition, estimand/target, metrics, units/scale/window, and evaluation protocol.
6. Split — train/validation/test membership rules, scenario-level identity separation, map-change placement policy, and any availability/late-arrival policy.
7. Independent anchor — the map/sensor reference or annotation source used as the independent reference, including its release/version and alignment relationship.
8. Identity/time/lineage — scenario/log identifiers, timestamp semantics and clock basis, map/sensor linkage keys, and revision/lineage fields.

Please do not include raw data, credentials, private links, or payload samples. Missing or conflicting fields will be retained as explicit abstentions. A metadata response would not itself authorize data acquisition or a named-task run.

If convenient, please copy and complete this public-safe response template. You may either provide the value/link directly or simply point to where it is documented (official page, section, file name, table, or repository path); we can extract and cite the value ourselves.

P21-ARGOVERSE-METADATA-RESPONSE-V1
release_ref: <value/link OR documented-location OR NOT_AVAILABLE>
rights_ref: <value/link OR documented-location OR NOT_AVAILABLE>
artifact_manifest_ref: <value/link OR documented-location OR NOT_AVAILABLE>
checksum_ref: <value/link OR documented-location OR NOT_AVAILABLE>
task_ref: <value/link OR documented-location OR NOT_AVAILABLE>
estimand_ref: <value/link OR documented-location OR NOT_AVAILABLE>
split_ref: <value/link OR documented-location OR NOT_AVAILABLE>
anchor_ref: <value/link OR documented-location OR NOT_AVAILABLE>
identity_time_ref: <value/link OR documented-location OR NOT_AVAILABLE>
disclosure_ref: <value/link OR documented-location OR NOT_AVAILABLE>
notes_or_conflicts:

Thank you for your assistance.

Sincerely,

Li Liang
PhD Student
School of National Security and Emergency Management
Beijing Normal University

Official dataset context: https://www.argoverse.org/av2.html