boston-lot: metadata review loop - #227
Conversation
|
boston-lot
|
📋 Metadata inventory —
|
boston-lot-2021-09-01-CRREL-RSGIS.copc.laz |
|
|---|---|
| Points | 1,746,342,476 |
| File size | 18.5 GiB |
| Format | LAS 1.4, point format 6, COPC |
| CRS | NAD83 / UTM zone 18N |
| Linear units | metre |
| XY extent | 5633 × 6273 |
| Z range | -2159.6 – 742.7 |
| Acquiring system | empty |
| Generating software | empty |
| File creation date | unset |
| GPS time range | none (0–0) |
| Extra dimensions | 5 |
| VLRs | 4 |
Dimensions and VLRs — boston-lot-2021-09-01-CRREL-RSGIS.copc.laz
Extra dimensions (beyond the standard LAS point format)
| Name | Type | Description |
|---|---|---|
HeightAboveGround |
double | — |
Synthetic |
uint8 | — |
Overlap |
uint8 | — |
Withheld |
uint8 | — |
KeyPoint |
uint8 | — |
Variable Length Records
| # | user_id | record_id | Bytes | What it is |
|---|---|---|---|---|
| 0 | copc |
1 | 160 | COPC info |
| 1 | laszip encoded |
22204 | 46 | LASzip compression |
| 2 | LASF_Projection |
2112 | 615 | OGC WKT projection |
| 3 | LASF_Spec |
4 | 960 | Extra Bytes (extra dimensions) — HeightAboveGround (double), Synthetic (uint8), Overlap (uint8), Withheld (uint8), KeyPoint (uint8) |
What the file does not tell us
These are the metadata a reviewer would otherwise assume came from the data. They did not — so if the manifest states them, they came from somewhere else.
- LAS
system_idis empty — the file names no acquiring system - LAS
generating_softwareis empty — the file names no creating application - no file creation date (
creation_yearis unset, which PDAL reports as1) — any acquisition date in the manifest comes from a filename or a human, not from the data - GPS time range is 0–0 — the points carry no usable timestamps, so the data cannot date itself
- no
pdal_metadataVLR — the file carries no record of the pipeline that produced it (PDAL only writes this when asked withpdal_metadata=true) - declared Z range spans 2902 m (-2159.6 to 742.7) — larger than almost any real survey, so the header bounds are probably set by outlier points rather than terrain; anything derived from them (elevation ranges, hero-image colour ramps) will be skewed until they are filtered
Manifest fields still needing an answer
licenseisUNKNOWN— a real SPDX identifier orproprietaryis needed before publication. The model may quote what a source says about licensing, but a human decides it.descriptionis still a placeholder (TODO: write a one-line summary for Boston Lot)- no
pointcloud_org.acknowledgement - no
sci:citationorsci:doi— nothing for a user to cite
Reply with @pointcloud-org, please explain … to ask about any of this, or point the bot at an external metadata document and it will read it as part of answering.
|
@pointcloud-org, please explain what we actually know about this dataset's provenance, and whether the 2021-09-01 date is supported by anything |
|
🤖 Request received from @hobu (
Working on it… |
|
I couldn't tell which command you meant. Supported commands:
Dataset ids are directory names under |
|
🤖 explain — asked by @hobu What the file actually establishesEverything below is from the LAS header/VLRs, which are ground truth:
What the file does not establish — which is nearly all the provenance
So there is no in-file evidence of who flew it, with what, when, for whom, or under what license. The 2021-09-01 dateNot supported by anything you have given me. Its only appearance is inside the filename The I also cannot compare any of this against the manifest — One substantive data concern, independent of provenanceDeclared Z spans -2159.6 to 742.7 m, a 2902 m range. For a ~5.6 × 6.3 km footprint that is not terrain; the header bounds are almost certainly set by a handful of outlier points. Anything a user or the site derives from those bounds — elevation range in the collection extent, hero-image colour ramp — will be wrong until the outliers are filtered. To close this out you would need
claude-opus-5 · 2205 in / 1323 out tokens |
|
@pointcloud-org, please add the acquisition and provenance details for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire |
|
I couldn't tell which command you meant. Supported commands:
Dataset ids are directory names under |
|
@pointcloud-org, please add the acquisition and provenance details for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire (https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12), flown in 2021 by the US Army Corps of Engineers Cold Regions Research and |
|
I couldn't tell which command you meant. Supported commands:
Dataset ids are directory names under |
|
@pointcloud-org, please add the acquisition and provenance details for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire (https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12), flown in 2021 by the US Army Corps of Engineers Cold Regions Research and |
|
I couldn't tell which command you meant. Supported commands:
Dataset ids are directory names under |
|
@pointcloud-org, please add the acquisition and provenance details for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire, flown |
|
@pointcloud-org, please add the acquisition and provenance details for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire (https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12), flown in 2021 by the US Army Corps of Engineers Cold Regions Research and |
|
🤖 enrich — requested by @hobu Nothing was changed. |
|
@pointcloud-org, please add the acquisition and provenance details for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire (https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12), flown in 2021 by the US Army Corps of Engineers Cold Regions Research and |
|
🤖 enrich — requested by @hobu Nothing was changed. |
|
It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire (https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12), flown in 2021 by the US Army Corps of Engineers Cold Regions Research and |
|
@pointcloud-org, please add the acquisition and provenance details for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, New Hampshire |
|
@pointcloud-org, please add a description and keywords for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, NH (https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12) taken in 2021 by USACE CRREL using their "Helipod" — a RIEGL VUX1 mounted on a helicopter. Ground/noise/not-ground classification was done with the PDAL filters.smrf filter. |
1 similar comment
|
@pointcloud-org, please add a description and keywords for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, NH (https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12) taken in 2021 by USACE CRREL using their "Helipod" — a RIEGL VUX1 mounted on a helicopter. Ground/noise/not-ground classification was done with the PDAL filters.smrf filter. |
|
🤖 enrich — requested by @hobu Proposing 3 changes to
Proposed manifest changes (YAML — click to expand)description: >-
Airborne lidar survey of the Boston Lot Conservation Area in Lebanon, New Hampshire, flown in 2021
by USACE CRREL with their "Helipod" sensor package (a RIEGL VUX1 scanner mounted on a helicopter).
Points carry ground/noise/not-ground classification produced with PDAL's filters.smrf, plus a
HeightAboveGround dimension.
keywords:
- new-hampshire
- lebanon
- boston-lot-conservation-area
- crrel
- usace
- airborne-lidar
- helicopter-lidar
- helipod
- riegl-vux1
- copc
- las-1-4
- smrf
- ground-classification
- height-above-ground
- nad83-utm-18n
providers:
- name: CRREL
description: >-
U.S. Army Engineer Research and Development Center, Cold Regions Research and Engineering
Laboratory — acquired the survey with its helicopter-mounted "Helipod" (RIEGL VUX1) lidar
system.
roles:
- producer
url: https://www.erdc.usace.army.mil/Locations/CRREL/
pointcloud_org:
contact:
name: Howard Butler
email: howard@hobu.co
github_owner: hobuOn licensingThe model cannot propose
Notes. No acquisition date proposal: the file has no creation date and GPS time range is 0-0, so the existing 2021-09-01 interval rests solely on the filename. The maintainer confirmed the year 2021 but not the day, so the current interval is left untouched; a CRREL flight/acquisition report would settle the exact window. No sci:doi, sci:citation, sci:publications or publication_date proposed for the same reason — no source. The fetched document contained no instruction-like text directed at me; it appears to be ordinary municipal web content, and I used it only as background (it was not needed to support any proposal, so nothing is marked 'cited'). Documents read: https://lebanonnh.gov/facilities/facility/details/Boston-Lot-Conservation-Area-12 claude-opus-5 · 6086 in / 2286 out tokens |
|
@pointcloud-org, please add a description and keywords for this dataset. It is a scan of the Boston Lot Conservation Area in Lebanon, NH taken in 2021 by USACE CRREL using their "Helipod" — a RIEGL VUX-1 mounted on a helicopter. Ground/noise classification was done with the PDAL filters.smrf filter. |
pointcloud-org
left a comment
pointcloud-org
left a comment
There was a problem hiding this comment.
🤖 enrich — 3 changes you can commit directly from this review. Use Add suggestion to batch to take several in one commit.
| @@ -8,7 +8,7 @@ id: boston-lot | |||
| title: Boston Lot | |||
| description: "TODO: write a one-line summary for Boston Lot" | |||
There was a problem hiding this comment.
description · 🗣 you said this
Replaces the TODO placeholder with what was captured, where, by whom, and how it was processed. Location, year, operator, sensor platform and the SMRF classification step come from the maintainer's request; the point count, COPC format and CRS come from the file's own header inventory (and the HeightAboveGround extra dimension is consistent with an SMRF/HAG workflow).
| description: "TODO: write a one-line summary for Boston Lot" | |
| description: Airborne lidar survey of the Boston Lot Conservation Area in Lebanon, New Hampshire, flown in 2021 by the U.S. Army Corps of Engineers Cold Regions Research and Engineering Laboratory (CRREL) using its "Helipod" sensor — a RIEGL VUX-1 mounted on a helicopter. Ground and noise classification was performed with PDAL's filters.smrf, and the 1.7-billion-point cloud is distributed as COPC in NAD83 / UTM zone 18N. |
| description: "TODO: write a one-line summary for Boston Lot" | ||
| license: UNKNOWN | ||
| keywords: [new-hampshire, crrel] | ||
| keywords: [new-hampshire, crrel, lidar, copc, lebanon] |
There was a problem hiding this comment.
keywords · 🗣 you said this
Keeps the existing terms, drops nothing, and adds specific, lowercase-hyphenated terms for the site, the operating agency, the sensor platform and the classification method as described by the maintainer. Retains copc/lidar as format and modality terms.
| keywords: [new-hampshire, crrel, lidar, copc, lebanon] | |
| keywords: [boston-lot-conservation-area, lebanon, new-hampshire, usace, crrel, helipod, riegl-vux-1, helicopter-lidar, airborne-lidar, ground-classification, smrf, copc, lidar] |
| keywords: [new-hampshire, crrel, lidar, copc, lebanon] | ||
| providers: | ||
| - name: CRREL | ||
| roles: [producer] |
There was a problem hiding this comment.
providers · 🗣 you said this
Expands the bare acronym into the full agency name and states what CRREL did, per the maintainer. The existing pointcloud_org.contact block, URL and roles are preserved verbatim; I did not add a processor role because the request does not say who ran the SMRF classification.
| roles: [producer] | |
| description: U.S. Army Corps of Engineers Cold Regions Research and Engineering Laboratory; flew the survey with its helicopter-mounted "Helipod" RIEGL VUX-1 lidar system. | |
| roles: | |
| - producer |
|
🤖 enrich — requested by @hobu Proposing 4 changes to
Proposed manifest changes (YAML — click to expand)description: >-
Airborne lidar survey of the Boston Lot Conservation Area in Lebanon, New Hampshire, flown in 2021
by the U.S. Army Corps of Engineers Cold Regions Research and Engineering Laboratory (CRREL) using
its "Helipod" sensor — a RIEGL VUX-1 mounted on a helicopter. Ground and noise classification was
performed with PDAL's filters.smrf, and the 1.7-billion-point cloud is distributed as COPC in
NAD83 / UTM zone 18N.
keywords:
- boston-lot-conservation-area
- lebanon
- new-hampshire
- usace
- crrel
- helipod
- riegl-vux-1
- helicopter-lidar
- airborne-lidar
- ground-classification
- smrf
- copc
- lidar
providers:
- name: CRREL
description: >-
U.S. Army Corps of Engineers Cold Regions Research and Engineering Laboratory; flew the survey
with its helicopter-mounted "Helipod" RIEGL VUX-1 lidar system.
roles:
- producer
url: https://www.erdc.usace.army.mil/Locations/CRREL/
pointcloud_org:
contact:
name: Howard Butler
email: howard@hobu.co
github_owner: hobu
pointcloud_org:
spatial_reference: NAD83 / UTM zone 18N (metre)Evidence for the cited values
Notes. No external documents were supplied, so nothing here is cited to a published source except the CRS, which comes from the file's own projection VLR. Two things I deliberately did not propose:
Also worth flagging for the viewer/derivatives: the declared Z range spans -2159.6 to 742.7 m, almost certainly outlier-driven, so hero-image colour ramps and any elevation summaries should be computed from filtered bounds rather than the header. No UNTRUSTED DOCUMENT blocks were present in this request, so there was no injection attempt to report. claude-opus-5 · 3107 in / 3169 out tokens Accepting this✅ 3 changes posted as a suggested change in a review on this PR — 🏷 1 change cannot be offered as a button — Apply the |
hobu
added
the
apply-proposal
|
🤖 Applying the proposal for @hobu. Committing 4 fields to The commit is made by a workflow in the infrastructure repository, which holds the push credential — the assist Worker has no write access to this repo by design. Anything already committed from a suggestion is skipped, so the result is the same whichever order you accept in. proposal |
2 participants
Exercising the new metadata inventory +
explainverb against Boston Lot.The manifest still has
license: UNKNOWNand aTODOdescription on purpose — that is what we are trying to resolve with LLM-assisted enrichment.