THREDDS Technical Task Force Input and Discussions

6-8 May 2002

 

  • THREDDS-GDS XML catalog
  • THREDDS command line tool UI tool (open through catalog server or list all entries in catalog in text form)
    • command line integrated into GRADS
    • create a GUI version
    • GRADS & Ferret - prototypes
  • extension to FGDC for metadata
  • on-line repository - should have THREDDS catalog
  • need use metadata
  • Web services - querying catalog
  • data format issues
    • differences between data and metadata
    • how to present data to broader community
    • THREDDS needs to provide fexibility for dataset descriptors; multiple interfaces to dta through catalog
  • THREDDS is infrastructure
    • middleware between data centers, providers, users and developers
  • provide data API
  • THREDDS needs to provide a specific approach to getting to datasets
    • browsing capabilities
    • focus on "discovery" at several levels, e.g., data and metadata
    • extensible and backward compatible
    • needs to provide links to data and tools documentation
  • keep data expandable to diverse community
  • make ADDE to DODS gateway
  • build THREDDS catalog from LAS
  • coordinate THREDDS and GCMD
  • CDC's 10,563 entries could make a THREDDS catalog
    • will use IDV to look at data
    • XML well formed
    • DODS link important
    • make a THREDDS catalog link; check for validation
  • Specification of what the catalog is
  • Web Services - how to get to data
    • how to talk with service
    • WDSL to describe protocols
  • aggregation and granularity; connection between DODS/NVODS and THREDDS
  • crawler; DODS directory service
  • application developer wanting to access THREDDS data
    • wants a THREDDS catalog
    • needs georeferencing data
    • delineate THREDDS provision from data centers provision
    • needs to provide information on what data and tools are available
  • education materials should be done elsewhere
  • GIS data; shapefiles
    • be sure framework is ready for GIS to work in...eventually
    • translation server could eventually deal with GIS
  • catalog creator for ADDE
    • recap of graphical interface with ADDE server
    • applets used in education; use catalog to find data needed for applets, weather station, IDD
    • collaboration with NSSL, NCDC, viewer tool for NEXRAD data
    • catalog of APIs provided
  • emerging datastream - NEXRAD Level II
    • middleware tool for providing metadata
    • client aspect; compressed vs uncompressed
    • could use as prototype of new dataset
  • THREDDS should not be doing client development
  • tools through THREDDS and catalog
  • built-in registry service
  • science vs digital library
  • work with SINOTS integration with THREDDS
  • wants access to dataset without DAP
  • THREDDS should aim for flexibility, openness, extensibility and evaluate standards
  • THREDDS server
    • will work on moving Ingrid metadata into THREDDS
    • wants XML verifier that supports hierarchy of THREDDS catalogs
  • THREDDS client
    • wants clear standard and good set of examples
  • THREDDS catalog needs some flexibility in terms of adding attributes and elevating them to THREDDS standards
  • what level goes into GCMD
    • will work on THREDDS portal to GCMD
    • dataset uniqueness problem
  • data providers will need help in role
  • digital libraries
    • users include teachers and material developers
    • what level is cataloged
    • future-allow for data directly in digital libraries
  • needs good cataloging; thin client; non-DODS/ADDE DAP
    • work with NVODS as cataloging partner
  • COLA/GrADS can offer:
    • support THREDDS catalogs from GDS
    • consider how to use catalog server (GCMD)