NASA-IMPACT / NASA-IMPACT/veda-data
Rename inconsistently named GEOGLAM files
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9
- Forks
- 1
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 1
Description
Three GEOGLAM files in veda-data-store have file names that do not conform to the pattern of the rest (CropMonitor_YYYYMM.tif).
Can we rename them - i.e. copy the files to conformant names and change their STAC entries? This may save users some headache who use S3 instead of STAC to discover items (although STAC is advised).
CropMonitor_2023_01_28.tif->CropMonitor_202301.tifCropMonitor_2023_02_28.tif->CropMonitor_202302.tifCropMonitor_2023_03_28.tif->CropMonitor_202303.tif
aws s3 ls s3://veda-data-store/geoglam/
2024-03-13 17:34:43 6012504 CropMonitor_202001.tif
2024-03-13 17:34:47 6029419 CropMonitor_202002.tif
2024-03-13 17:34:49 6017018 CropMonitor_202003.tif
2024-03-13 17:34:50 6386366 CropMonitor_202004.tif
2024-03-13 17:34:52 6346561 CropMonitor_202005.tif
2024-03-13 17:34:53 6320955 CropMonitor_202006.tif
2024-03-13 17:34:55 4658995 CropMonitor_202007.tif
2024-03-13 17:34:56 4677472 CropMonitor_202008.tif
2024-03-13 17:34:56 4705830 CropMonitor_202009.tif
2024-03-13 17:34:57 4341809 CropMonitor_202010.tif
2024-03-13 17:34:58 5288105 CropMonitor_202011.tif
2024-03-13 17:34:59 5321207 CropMonitor_202101.tif
2024-03-13 17:35:00 5277308 CropMonitor_202102.tif
2024-03-13 17:35:01 5284661 CropMonitor_202103.tif
2024-03-13 17:35:02 5259615 CropMonitor_202104.tif
2024-03-13 17:35:03 5239591 CropMonitor_202105.tif
2024-03-13 17:35:04 4492889 CropMonitor_202106.tif
2024-03-13 17:35:05 4503863 CropMonitor_202107.tif
2024-03-13 17:35:06 3494043 CropMonitor_202108.tif
2024-03-13 17:35:07 5293999 CropMonitor_202109.tif
2024-03-13 17:35:08 5343006 CropMonitor_202110.tif
2024-03-13 17:35:09 5311489 CropMonitor_202111.tif
2024-03-13 17:35:10 5336762 CropMonitor_202201.tif
2024-03-13 17:35:11 5268139 CropMonitor_202202.tif
2024-03-13 17:35:12 5309246 CropMonitor_202203.tif
2024-03-13 17:35:13 5281256 CropMonitor_202204.tif
2024-03-13 17:35:14 4886345 CropMonitor_202205.tif
2024-03-13 17:35:15 4907825 CropMonitor_202206.tif
2024-03-13 17:35:16 4946370 CropMonitor_202207.tif
2024-03-13 17:35:17 3296784 CropMonitor_202208.tif
2024-03-13 17:35:18 4996502 CropMonitor_202209.tif
2024-03-13 17:35:19 5006583 CropMonitor_202210.tif
2024-03-13 17:35:20 5036055 CropMonitor_202211.tif
2024-03-13 17:35:21 4968798 CropMonitor_202304.tif
2024-03-13 17:35:22 4693854 CropMonitor_202305.tif
2024-03-13 17:35:22 5013383 CropMonitor_202306.tif
2024-03-13 17:35:23 5411525 CropMonitor_202307.tif
2024-03-13 17:35:24 5362108 CropMonitor_202308.tif
2024-03-13 17:35:25 4678356 CropMonitor_202309.tif
2024-03-13 17:35:26 4723276 CropMonitor_202310.tif
2024-03-13 17:35:27 4800011 CropMonitor_202311.tif
2024-03-13 17:35:28 4982767 CropMonitor_2023_01_28.tif
2024-03-13 17:35:29 4973021 CropMonitor_2023_02_28.tif
2024-03-13 17:35:30 5016336 CropMonitor_2023_03_28.tif
2024-03-13 17:35:31 5003250 CropMonitor_202401.tif
2024-03-15 20:21:21 4753596 CropMonitor_202402.tif
2024-05-21 20:53:07 4795250 CropMonitor_202403.tif
2024-08-09 20:08:26 4792191 CropMonitor_202404.tif
2024-08-09 20:08:26 4819082 CropMonitor_202405.tif
2024-08-09 20:08:26 4807514 CropMonitor_202406.tif
2024-08-09 20:08:27 4822375 CropMonitor_202407.tif
Acceptance criteria
- All GEOGLAM files are consistently named
- STAC items point to the right files are fixed
- Inconsistently named copies are deleted
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the GEOGLAM objects in veda-data-store and the AWS S3 listing in this issue, then inspect the corresponding STAC entries. Done means the three files use the CropMonitor_YYYYMM.tif names, STAC items point to those files, and the inconsistently named copies are deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100