feat: create gedi-tiled-v2 collection and copy assets to public bucket

[hrodmn]

Just a collection (no items) for now, with a manifest.txt asset that can be provided to duckdb to query the entire dataset without s3:ListBucket permissions. I also added a SQL script asset that shows how to set up collection-wide access in duckdb.

Here is what the SQL looks like for using the manifest file (hrodmn-scratch is a non-public bucket in the SMDC-MAAP AWS account):

INSTALL httpfs;
LOAD httpfs;

SET VARIABLE gedi_v2_files = (
    SELECT list(href)
    FROM read_csv(
        's3://hrodmn-scratch/file-staging/nasa-map/gedi-tiled-v2/manifest.txt',
        header = false,
        columns = {'href': 'VARCHAR'}
    )
);

CREATE OR REPLACE VIEW gedi_tiled_v2 AS
SELECT *
FROM read_parquet(
    getvariable('gedi_v2_files'),
    hive_partitioning = true
);

Then you can do things like:

select count(*) from gedi_tiled_v2 where year = 2020;

Resolves https://github.com/NASA-IMPACT/active-maap-sprint/issues/1426

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[jjfrench]

STAC Collection output looks good!

[hrodmn]

@jjfrench I added the iceberg metadata asset and ran the steps in the "prod" environment which copied the files to nasa-maap-data-store.

[jjfrench]

is it supposed to have two gedi-tiled-v2 prefixes?

"s3://nasa-maap-data-store/file-staging/nasa-map/gedi-tiled-v2/iceberg/gedi_tiled_v2/metadata/latest.metadata.json"

[hrodmn]

is it supposed to have two gedi-tiled-v2 prefixes?

"s3://nasa-maap-data-store/file-staging/nasa-map/gedi-tiled-v2/iceberg/gedi_tiled_v2/metadata/latest.metadata.json"

Yeah, I think that's an iceberg convention based on the table's name in the iceberg catalog.