USGS Home
Contact USGS
Search USGS

Metadata Generation and Management (GLIS, Production)

M. Sarges, G. Kluck, C. Moschell, J. Faundeen

Metadata definition/scheme for AVPDB and GLIS.

With minor modification, the existing data bases are serving the project sufficiently well to manage the project.

Capture of the metadata at the time of ingest.

CSB has built a table that contains the CEOS receiving station codes that are used in the ingest process. The CEOS codes are passed as part of the metadata record to the AVPDB and ultimately to GLIS.

Transfer of the metadata to the AVPDB and GLIS.

For the AVPDB system the metadata is sent as the ingesting process is completed. GLIS receives the metadata from the AVPDB multiple times per day from batch jobs.

Assess the impact and data base sizing of loading metadata to AVPDB and GLIS.

The team estimates that the GLIS metadata sizing, based on 70 records per day, will occupied approximately 7.6 meg of disk space through the first 18 months of the Project. That figure is based on 200 characters per record. Similarly, the team estimates that the AVPDB metadata hard disk requirements, based on the same 70 scenes a day ingested, result in 13.5 meg for the 18 month period. That total assumes 350 characters/record. Neither total is thought to be worrisome.

Management of metadata. i.e., AVPDB, GLIS, digital archive, Browse, etc.

Data Management and ISM plotting routines are completed on a weekly basis to validate the received versus the expected data from the LAC recorder scheduler. Coordinate validity and data gaps are also checked on a daily basis for all 1-km data received.

Data Management reports illustrate the volume of the data received by station on daily and monthly increments. The reports also capture duplication and deletion volumes.

Back to 1-KM Homepage