boston-lot: metadata review loop - #227
pointcloud-org wants to merge 4 commits into
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.- 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 |
There was a problem hiding this comment.
🤖 enrich — requested by @hobu
Proposing 3 changes to manifests/boston-lot/manifest.yaml. Nothing has been written — this is a suggestion for you to apply, reject, or edit.
| Field | Basis | What and why |
|---|---|---|
description |
🗣 you said | Uses the maintainer's supplied text for the TODO description. Two edits only: the typo 'multi-sensor. helicopter-mounted' is corrected to a comma, and the disparaging phrase 'a bunch of no-talent hacks from' is dropped from the NCALM clause, since the archive's descriptions are user-facing and the phrase makes a public claim about a named collaborating institution. All substantive content (location, campaign purpose, RSGIS, RaLiPod, sensor mix, NCALM collaboration) is unchanged. Restore the original phrasing if it was intended seriously. |
keywords |
🗣 you said | Keeps the keywords added on the anchored line and adds terms the maintainer's description supports: the second municipality (hanover), the site name, the payload name (ralipod), the collaborating centre (ncalm), the parent organisation (usace), and the campaign type (sensor-integration). All lowercase and hyphenated per conventions. |
providers |
🗣 you said | Adds the two organisations the maintainer names as responsible for the payload and the acquisition. The existing CRREL entry, including its pointcloud_org.contact block, is reproduced verbatim. No URLs are given for the two new entries because the maintainer did not supply them and I have no document to cite; a maintainer can add them. |
⚠️ These proposals were not checked againstmanifests/schema.json— it could not be read (Code generation from strings disallowed for this context). Treat them as unverified; CI is still the gate.
Proposed manifest changes (YAML — click to expand)
description: >-
Airborne lidar point cloud covering the Boston Lot Conservation Area in Lebanon and Hanover, New
Hampshire, collected as part of a sensor integration and testing campaign. The US Army Corps of
Engineers Remote Sensing & GIS Center of Expertise developed an integrated, multi-sensor,
helicopter-mounted payload — the RaLiPod — carrying lidar, visible-spectrum imagery, and synthetic
aperture radar, and flew local tests to confirm operation, check calibrations, and assess
performance and acquisition techniques. Data acquisition was carried out in collaboration with the
University of Houston's National Center for Airborne Laser Mapping (NCALM).
keywords:
- new-hampshire
- lebanon
- hanover
- boston-lot
- crrel
- usace
- ncalm
- ralipod
- airborne-lidar
- sensor-integration
- copc
- lidar
providers:
- name: CRREL
roles:
- producer
url: https://www.erdc.usace.army.mil/Locations/CRREL/
pointcloud_org:
contact:
name: Howard Butler
email: howard@hobu.co
github_owner: hobu
- name: US Army Corps of Engineers Remote Sensing & GIS Center of Expertise
description: >-
Developed the integrated multi-sensor helicopter payload (RaLiPod) and flew the test
acquisition.
roles:
- producer
- name: National Center for Airborne Laser Mapping (NCALM), University of Houston
description: Collaborated on data acquisition.
roles:
- producerOn licensing
The model cannot propose license. This is what it found; the decision is yours.
No supplied document mentions licensing for this dataset, so no licence statement can be quoted. The manifest's 'TODO: confirm license before publishing' should stand until an ERDC/CRREL release or distribution statement (and NCALM's terms, if their collection is covered) is obtained.
Notes. No external documents were supplied with this request, so several fields are deliberately left alone. (1) extent.temporal.interval is currently [[2021-09-01, 2021-09-01]]; the inventory confirms the file itself carries no creation date and GPS time 0-0, so that window comes only from the filename. I have not proposed a change — a CRREL/RSGIS flight log, mission report, or an acquisition-date statement from the maintainer would settle whether 2021-09-01 is the true (and single-day) acquisition window. (2) The file's license is still UNKNOWN and I am not permitted to propose it; no supplied source says anything about licensing, so there is nothing to quote in license_note. A data-distribution statement or public release notice from ERDC/CRREL (and, if NCALM-collected data are involved, NCALM's distribution terms) would settle it. (3) pointcloud_org.acknowledgement is unproposed for the same reason: a credit line must come from a data agreement or the data provider, not from me. (4) No DOI, citation, or publication is proposed — I have no document naming one. (5) Worth flagging to the maintainer, though it is outside the fields I may propose: the header Z range spans -2159.6 to 742.7 m (2902 m), almost certainly outlier-driven, so any derived elevation range or hero-image colour ramp will be skewed until those points are filtered. No prompt-injection attempts were present; the quoted diff and the inventory contained data only.
claude-opus-5 · 3511 in / 3212 out tokens
Accepting this
✅ 3 changes posted as a suggested change in a review on this PR — description, keywords, providers. Open the Files changed tab and use Commit suggestion, or batch several into one commit.
There was a problem hiding this comment.
@pointcloud-org, please update the description to the following text:
Airborne lidar point cloud covering the Boston Lot Conservation Area in Lebanon and Hanover, NH as part of a sensor integration and testing campaign. The US Army Corps of Engineers Remote Sensing & GIS Center of Expertise developed an integrated, multi-sensor. helicopter-mounted payload that includes lidar, visible spectrum imagery, and synthetic aperture radar. This system, called the RaLiPod, underwent local flight tests to confirm operation, check calibrations, and assess performance and acquisition techniques. Data acquisition was in collaboration with a bunch of no-talent hacks from the University of Houston's National Center for Airborne Laser Mapping (NCALM)
There was a problem hiding this comment.
🤖 enrich — requested by @hobu
Proposing 3 changes to manifests/boston-lot/manifest.yaml. Nothing has been written — this is a suggestion for you to apply, reject, or edit.
| Field | Basis | What and why |
|---|---|---|
description |
🗣 you said | Replaces the TODO placeholder on line 14 with the text the maintainer supplied. Two edits only: fixed the stray period in "multi-sensor. helicopter-mounted" to a comma and added the missing terminal period, and dropped the phrase "a bunch of no-talent hacks from" before the University of Houston, which reads as an in-joke and would be a disparaging public statement about a named collaborating institution in an archive-facing description. Substance is otherwise verbatim. If the phrase was intended seriously, say so and I will restore it. |
providers |
🗣 you said | The maintainer states acquisition was a collaboration with NCALM, so NCALM belongs in providers alongside CRREL. The existing CRREL entry, including its pointcloud_org.contact block, is reproduced unchanged. No url given for NCALM because I have no supplied document establishing the correct institutional URL. |
keywords |
🗣 you said | Keeps the existing terms, drops the generic "lidar" in favour of "airborne-lidar", and adds the specific place and campaign terms the maintainer's description supplies (Hanover, Boston Lot, RaLiPod, NCALM, sensor integration). All lowercase and hyphenated per conventions. |
Proposed manifest changes (YAML — click to expand)
description: >-
Airborne lidar point cloud covering the Boston Lot Conservation Area in Lebanon and Hanover, NH,
captured as part of a sensor integration and testing campaign. The US Army Corps of Engineers
Remote Sensing & GIS Center of Expertise developed an integrated, multi-sensor, helicopter-mounted
payload that includes lidar, visible spectrum imagery, and synthetic aperture radar. This system,
called the RaLiPod, underwent local flight tests to confirm operation, check calibrations, and
assess performance and acquisition techniques. Data acquisition was in collaboration with the
University of Houston's National Center for Airborne Laser Mapping (NCALM).
providers:
- name: CRREL
roles:
- producer
url: https://www.erdc.usace.army.mil/Locations/CRREL/
pointcloud_org:
contact:
name: Howard Butler
email: howard@hobu.co
github_owner: hobu
- name: National Center for Airborne Laser Mapping (NCALM), University of Houston
description: Collaborated on data acquisition for the RaLiPod flight tests.
roles:
- producer
keywords:
- new-hampshire
- lebanon
- hanover
- boston-lot
- crrel
- ncalm
- ralipod
- airborne-lidar
- sensor-integration
- copcNotes. No external documents were supplied with this request, and no document or file content contained anything resembling instructions to me — nothing to report on that front.
Deliberately not proposed:
- extent.temporal.interval: left as-is. The inventory is explicit that the file has no creation date and GPS time 0-0, so the 2021-09-01 window comes only from the filename. The maintainer's text describes the campaign but names no dates. A flight log, RaLiPod test report, or NCALM acquisition report would settle the real acquisition window; until then the interval is a filename artefact and should probably carry a comment saying so.
- pointcloud_org.acknowledgement: the maintainer's text names CRREL/USACE RSGIS and NCALM, but a credit line is what a data agreement expects verbatim, and I have no such document. The USACE/CRREL data-use or distribution agreement for this dataset (or NCALM's standard acknowledgement text, if the collaboration terms require it) would settle the wording.
- sci:doi, sci:citation, sci:publications, links, metadata_links, spatial_reference: no sources supplied. Note the header does carry an OGC WKT VLR declaring NAD83 / UTM zone 18N in metres, so pointcloud_org.spatial_reference could be filled from the data itself if you want it stated explicitly.
- license: out of scope for me, but the "TODO: confirm license before publishing" comment on line 6 is still unresolved and no supplied document says anything about licensing, so I have no license_note to offer. Worth resolving before publish since the producer is a US Army Corps of Engineers laboratory with a named external collaborator.
One data observation relevant to any description or hero image: the declared Z range spans -2159.6 to 742.7 m, far wider than the terrain around Boston Lot, so outliers are almost certainly present. I avoided putting any elevation or relief claim in the description for that reason.
claude-opus-5 · 3511 in / 2747 out tokens
Accepting this
✅ 2 changes posted as a suggested change in a review on this PR — description, keywords. Open the Files changed tab and use Commit suggestion, or batch several into one commit.
🏷 1 change cannot be offered as a button — providers. GitHub only allows a suggestion on lines that appear in this PR's diff, and these fall outside it.
Apply the apply-proposal label to this PR and the whole proposal will be committed to the branch. The commit is made by a workflow holding a push credential, not by the assist Worker — which deliberately has no write access. Anything you have already accepted by button is skipped, so committing a suggestion first is safe.
- Straddles the boundary of this PR's diff, so
providerscannot be offered as a button — GitHub can only place a suggestion on lines the PR already touches, and half a change committed is worse than none. Use theapply-proposallabel, which applies the whole edit.
|
🤖 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 |
pointcloud-org
removed
the
apply-proposal
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
Uses the maintainer's supplied text for the TODO description. Two edits only: the typo 'multi-sensor. helicopter-mounted' is corrected to a comma, and the disparaging phrase 'a bunch of no-talent hacks from' is dropped from the NCALM clause, since the archive's descriptions are user-facing and the phrase makes a public claim about a named collaborating institution. All substantive content (location, campaign purpose, RSGIS, RaLiPod, sensor mix, NCALM collaboration) is unchanged. Restore the original phrasing if it was intended seriously.
| description: "TODO: write a one-line summary for Boston Lot" | |
| description: Airborne lidar point cloud covering the Boston Lot Conservation Area in Lebanon and Hanover, New Hampshire, collected as part of a sensor integration and testing campaign. The US Army Corps of Engineers Remote Sensing & GIS Center of Expertise developed an integrated, multi-sensor, helicopter-mounted payload — the RaLiPod — carrying lidar, visible-spectrum imagery, and synthetic aperture radar, and flew local tests to confirm operation, check calibrations, and assess performance and acquisition techniques. Data acquisition was carried out in collaboration with the University of Houston's National Center for Airborne Laser Mapping (NCALM). |
| 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 keywords added on the anchored line and adds terms the maintainer's description supports: the second municipality (hanover), the site name, the payload name (ralipod), the collaborating centre (ncalm), the parent organisation (usace), and the campaign type (sensor-integration). All lowercase and hyphenated per conventions.
| keywords: [new-hampshire, crrel, lidar, copc, lebanon] | |
| keywords: [new-hampshire, lebanon, hanover, boston-lot, crrel, usace, ncalm, ralipod, airborne-lidar, sensor-integration, 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
Adds the two organisations the maintainer names as responsible for the payload and the acquisition. The existing CRREL entry, including its pointcloud_org.contact block, is reproduced verbatim. No URLs are given for the two new entries because the maintainer did not supply them and I have no document to cite; a maintainer can add them.
| roles: [producer] | |
| roles: | |
| - producer |
pointcloud-org
left a comment
pointcloud-org
left a comment
There was a problem hiding this comment.
🤖 enrich — 2 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 on line 14 with the text the maintainer supplied. Two edits only: fixed the stray period in "multi-sensor. helicopter-mounted" to a comma and added the missing terminal period, and dropped the phrase "a bunch of no-talent hacks from" before the University of Houston, which reads as an in-joke and would be a disparaging public statement about a named collaborating institution in an archive-facing description. Substance is otherwise verbatim. If the phrase was intended seriously, say so and I will restore it.
| description: "TODO: write a one-line summary for Boston Lot" | |
| description: Airborne lidar point cloud covering the Boston Lot Conservation Area in Lebanon and Hanover, NH, captured as part of a sensor integration and testing campaign. The US Army Corps of Engineers Remote Sensing & GIS Center of Expertise developed an integrated, multi-sensor, helicopter-mounted payload that includes lidar, visible spectrum imagery, and synthetic aperture radar. This system, called the RaLiPod, underwent local flight tests to confirm operation, check calibrations, and assess performance and acquisition techniques. Data acquisition was in collaboration with the University of Houston's National Center for Airborne Laser Mapping (NCALM). |
| 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 the generic "lidar" in favour of "airborne-lidar", and adds the specific place and campaign terms the maintainer's description supplies (Hanover, Boston Lot, RaLiPod, NCALM, sensor integration). All lowercase and hyphenated per conventions.
| keywords: [new-hampshire, crrel, lidar, copc, lebanon] | |
| keywords: [new-hampshire, lebanon, hanover, boston-lot, crrel, ncalm, ralipod, airborne-lidar, sensor-integration, copc] |
hobu
added
the
apply-proposal
|
🤖 Apply requested by @hobu. 3 fields queued for 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. The workflow will post the outcome here — including if it fails. If no follow-up comment appears within a couple of minutes, treat that as a failure and say so. proposal |
|
🤖 Could not apply the proposal. see the run log Nothing was committed. Run log |
pointcloud-org
removed
the
apply-proposal
hobu
added
the
apply-proposal
|
🤖 Apply requested by @hobu. 3 fields queued for 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. The workflow will post the outcome here — including if it fails. If no follow-up comment appears within a couple of minutes, treat that as a failure and say so. proposal |
Applied: `description`, `providers`, `keywords` Proposal 1789743951817, accepted with the apply-proposal label.
|
🤖 Proposal applied. Applied: Committed to this branch. The manifest checks will re-run on the new commit. |
pointcloud-org
removed
the
apply-proposal
|
🤖 enrich — requested by @hobu Every proposed change was dropped before reaching you. 1 proposal(s) dropped: they would not validateThese were on the permitted-field list, so the model was allowed to suggest them, but applying them produces a manifest that
|
|
@pointcloud-org set the license to CC0 |
|
🤖 enrich — requested by @hobu The maintainer's request concerns only On licensingThe model cannot propose
I cannot change that fieldYour request named a field I am not allowed to propose, so nothing below addresses it:
This is a rule in code, not a judgement about the value you asked for. Edit the manifest directly and the ordinary checks still apply. |
|
@pointcloud-org what license SPDX ID should be used for US government public domain data? |
|
🤖 enrich — requested by @hobu I am proposing no manifest changes on this request. The maintainer asked a licensing question rather than asserting a fact, so there is nothing here I can carry into the manifest as On licensingThe model cannot propose
I cannot change those fieldsYour request named fields I am not allowed to propose, so nothing below addresses them:
This is a rule in code, not a judgement about the value you asked for. Edit the manifest directly and the ordinary checks still apply. |
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.