Process CMR metadata (by project) into tabular and spatial formats for spatial db index.
- contents: list of files included for each project and dataset
- usage: example invocation of python module
cmr
as script - updates: details about update tracking
Each project has the following files (e.g. projects/podaac/ghrsst/
):
projects/podaac/ghrsst/ds.json
: UMM-C records for all datasets (API response as JSON)projects/podaac/ghrsst/ds.csv
: UMM-C records parsed to a tableprojects/podaac/ghrsst/ds.geojson
: UMM-C records table as a GeoJSONprojects/podaac/ghrsst/ds.shp
: UMM-C records table as an ESRI Shapefileprojects/podaac/ghrsst/ds.kml
: UMM-C records table as a KML
And each dataset in a project has the following files (e.g. projects/podaac/ghrsst/GOES13-OSISAF-L3C-v1.0/
):
projects/podaac/ghrsst/GOES13-OSISAF-L3C-v1.0/gr.json
: UMM-G records for all granules (API response as JSON)projects/podaac/ghrsst/GOES13-OSISAF-L3C-v1.0/gr.csv
: UMM-G records parsed to a tableprojects/podaac/ghrsst/GOES13-OSISAF-L3C-v1.0/gr.geojson
: UMM-G records table as a GeoJSONprojects/podaac/ghrsst/GOES13-OSISAF-L3C-v1.0/gr.shp
: UMM-G records table as an ESRI Shapefileprojects/podaac/ghrsst/GOES13-OSISAF-L3C-v1.0/gr.kml
: UMM-G records table as a KML
Optional: update path and query settings in config.json
.
Run as a module by passing a valid project name to cmr/__main__.py
:
python -m cmr ghrsst
This wrapper script calls CMR collections endpoint to retrieve all of the unique project names for the input CMR provider (set __PROVIDER__
in update.py
).
./update.py
Update history is tracked by project in projects/podaac/projects.json
.
The PROVIDER.md (PODAAC.md) is regenerated with every successful run.