Populate Landsat scene outlines with CID information

[jsolly]

Context

We need CIDs for each Landsat scene so that when the user clicks on a scene, a CID can be sent to an API for metadata. We should probably inject all the CIDs for all the assets within a scene (all the bands)

~Here is a CID of all the row/paths that intersect the continental us: QmRuTvbcvH7zifFmtezRDgLPHRAyodRKJgPChd9MxUwweJ~

Requirements

Each row/path will need the CID of one landsat scene that matches that row/path. You will need to find one landsat scene that match each of the row/paths that intersect the continental United States (See CID for the JSON file). Check the stac.json or the folder/filename to know what row column that scene is in. You might need to coordinate with Zheng to get all the landsat scene CIDs you need.

After figuring out all the scenes for each row/path (there should be around ~500~ ~850), you will need to place the CIDs for those scenes inside this ~GeoJSON file: Qma2c3Ne7E7MK9JbW3qVuTKHLWmPdsRErwmm9ip5D36xge~

This way, when we create the tileset, the CID will be one of the attributes of each landsat scene.

Things to consider

We will need to decide on which CIDs to include in the GeoJSON to facilitate querying the API. For example, this is a typical Landsat scene directory. Each asset has its own CID.

LC09_L1TP_019046_20211031_20220118_02_T1 ├── LC09_L1TP_019046_20211031_20220118_02_T1_ANG.txt ├── LC09_L1TP_019046_20211031_20220118_02_T1_B1.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B10.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B11.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B2.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B3.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B4.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B5.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B6.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B7.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B8.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_B9.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_MTL.json ├── LC09_L1TP_019046_20211031_20220118_02_T1_MTL.txt ├── LC09_L1TP_019046_20211031_20220118_02_T1_MTL.xml ├── LC09_L1TP_019046_20211031_20220118_02_T1_QA_PIXEL.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_QA_RADSAT.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_SAA.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_SZA.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_VAA.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_VZA.TIF ├── LC09_L1TP_019046_20211031_20220118_02_T1_stac.json ├── LC09_L1TP_019046_20211031_20220118_02_T1_stac_web3_enriched.json ├── LC09_L1TP_019046_20211031_20220118_02_T1_thumb_large.jpeg └── LC09_L1TP_019046_20211031_20220118_02_T1_thumb_small.jpeg

For this proof of concept app, let's just associate ONE landsat scene with each row/path. Let's not tackle the idea that hundreds of possible landsat scenes could exist for each row/path.

[jsolly]

@matthewnanas the files were small enough, that I just put them in source control: https://github.com/easierdata/web3-geo-dashboard/blob/main/data_processing/landsat_scenes_intersecting_continential_us.geojson

https://github.com/easierdata/web3-geo-dashboard/blob/main/data_processing/continental_us_states.geojson

I suggest using these ones...write your own processing script and then create new files called web3_enriched.geojson or something like that.

[jsolly]

For the PoC we are putting a single band into each scene. We will need to think harder about the best way to place all bands (assets) into each scene.

@matthewnanas once the web3 enriched geojson is in main can you close this one and link to that new geojson in this issue so anyone looking through older issues can find it?

[jsolly]

This is done. A modification is being made in https://github.com/easierdata/web3-geo-dashboard/issues/26

Nice @matthewnanas !