Download presentation
Presentation is loading. Please wait.
Published byBeatrix Golden Modified over 9 years ago
1
Page 1 CSISS Center for Spatial Information Science and Systems CWIC Development Team Meeting, 2014 Adding more ECHO datasets to CWIC Lingjun Kang lkang3@masonlive.gmu.edu Center for Spatial Information Science and Systems (CSISS) George Mason University CWIC Workshop, Jan 28-30, 2014 Greenbelt, MD
2
Page 2 CSISS Center for Spatial Information Science and Systems Key issues Key issue 1: ECHO dataset ID ECHO dataset ID can not be identified once new datasets were registered in IDN. This defers many new dataset from being tested and added to CWIC. –CWIC can not retrieve ECHO dataset ID from IDN. Cause ECHO dataset ID was not input in DIF during registration. (incoming IDN mapping table will include this info) –CWIC can not retrieve ECHO dataset ID for every new dataset from ECHO API based on IDN entry ID. Cause entry ID is not a mandatory field in ECHO metadata. –Identifying ECHO dataset ID was still based on e-mail exchange. This accounts for the time lagging before new ECHO datasets can be served in CWIC.
3
Page 3 CSISS Center for Spatial Information Science and Systems Key issues Key issue 2: Incorrect ECHO dataset ID In some cases, ECHO dataset ID from data provider was incorrect (e.g. mistakenly formatted as all upper cases). CWIC correct this by comparing with ECHO dataset holding list (validation module). This produces nearly 60 false ‘0 granule’ datasets.
4
Page 4 CSISS Center for Spatial Information Science and Systems Key issues Recommended dataset registration protocol to prevent this situation –For incoming IDN mapping table, an interface could be granted to data provider for ECHO dataset ID registration. An query interface could also be granted to CWIC for ECHO dataset ID identification. –On CWIC side, ECHO dataset ID validation module will be embedded to synchronization procedure to prevent unexpected errors.
5
Page 5 CSISS Center for Spatial Information Science and Systems Key issues Key issue 3: Datasets with updated entry ID For some ASTER and MODIS datasets from LPDAAC and NSIDC, entry ID will be appended with a version number. (example: MCD12Q2 MCD12Q25). Following situations deter dataset testing and updating in CWIC. –Some datasets with old entry ID still exits in IDN (should be deleted or at least untagged with CWIC) –Some datasets with updated entry IDs are not added to IDN. –Error was found in entry ID update: “e.g. Two datasets (MYD13A1 and MYD11C3) sharing the same new entry ID (MYD11C35) were found in spreadsheet.”
6
Page 6 CSISS Center for Spatial Information Science and Systems Key issues Recommended protocol for IDN dataset entry ID update –Remove old entry ID (without version) from both IDN TEST and PROD and notify CWIC with removal confirmation. –Identify both new entry ID and corresponding ECHO dataset ID before they are tagged with ‘CWIC’. –Add datasets with updated entry ID to IDN TEST. –Migrate new datasets to IDN PROD once it passes testing.
7
Page 7 CSISS Center for Spatial Information Science and Systems Question & Discussion
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.