Clearinghouse WG Telecon Agenda and Presentations

1. Clearinghouse WG TeleconAgenda and Presentations January 29, 2002

2. Agenda • Introductions (5 min) • Clearinghouse Node Status (5 min) • Clearinghouse Registration Revision (5 min) • ISO Metadata Software – Enraemed (5 min) • FGDC to ISO Metadata Transition (5 min) • Isite Software Status (10 min) • Canadian Clearinghouse: GeoConnections (15 min) • Integration of Clearinghouse and Web Mapping Services - WebMapCAP (15 min) • Proposed NSDI Technical Workshop, April 29 – May 1, 2002 Denver CO (10 min) • Wrap-up (5 min)

3. Clearinghouse Nodes Status

4. Clearinghouse Nodes Around the World As of January 2002 Minnesota Map Server Online Soon!

5. Clearinghouse Nodes Around the World As of January 2002 Argentina: 1 Australia: 19 Barbados: 2 Bolivia: 1 Brazil: 2 Canada: 42 Chile 1 China: 1 Colombia: 2 Costa Rica: 3 Dominica: 1 Dominican Republic: 1 El Salvador: 2 Guatemala: 2 Honduras: 2 Italy: 2 Japan: 1 Jamaica: 1 Kenya: 2 Mexico: 2 Nicaragua: 2 Peru: 1 South Africa: 2 Trinidad & Tobago: 1 United Kingdom: 5 United States: 177 Uruguay: 3 Venezuela: 1

6. Clearinghouse Node Status • 278 Clearinghouse Servers Registered • 247 – Active Status • Some are down or improperly registered • Reflect Negatively on the Status Page and in Searches • Need to Upgrade Software or GEO Version Information • 31 - Not Active Status • 19 – Pending Status • New Registry Wizard will Resolve

7. New Registry Wizard Functions

8. New Registration System • Develop new registration wizard that .. • Performs immediate online tests of z30.50 server before registration can be completed • Removes support needed by Clearinghouse Admins • Will Automate • IP Address Lookup based on Machine Name • Automate Software Name, Version and GEO Value

9. Registry WizardAdd A New Node • Wizard registration process steps through node registration process • Node cannot be registered until all tests have passed. Completely user controlled. • Replaces Current Method of Being Placed in Pending Database Until Tests are Passed. • Eliminates Duplicate and Bad Node Entries

11. Registry WizardModify An Existing Node • Registry Modify • Currently In Development • Allow User the Ability to Modify Existing Node Information • Performs All Node Tests • Extracts: • Server IP Address, Software Name & Version, Geo Value • Automatically Updates Database • Time Spent in Pending Database is eliminated

12. Registry Battery • Planning a set of tools that will … • Provide the gateways on a daily basis with only those nodes that are UP • Provide a mechanism to alert node administrators when their node ha gone DOWN • Develop a report of all clearinghouse nodes with their status and diagnostics • Currently in Development

13. Server XML Registry Battery Registry Database DBLIST.XML • Battery Tools • Perform a Ping and z39.50 Test • Write a Detailed Status Report • Write the UP/DOWN Report • For all UP Nodes: • Develop new DBLIST.XML • Develop XML metadata ASCII Detail Report HTML Detail Report Mirrored Gateways New DBLIST XML

14. Enraemed Metadata Software

15. Enraemed Metadata Software • Develop by Dutch Donor Agency for the Ethiopian Government • Being used within Ethiopia by all governmental institutions • Willingness to hand over software to FGDC for maintenance

16. Enraemed Metadata SoftwareFeatures • ISO, FGDC, GILS, and DC compliant • Stand Alone or Client–Server • Backend Database • MSDE, MS SQL Server, Access2000 • Globally unique IDs • Element Navigator • Elements of selected standard • Mandatory-optional-mandatory • Jump function

17. Enraemed Logon

18. Enraemed Navigator

19. View – Page - Elements

20. FGDC to ISO Metadata Transition • ISO 19115 Metadata expected to be adopted as IS in July and as ANSI (not FGDC) Standard in November • Two technical amendments will accompany the ANSI Metadata Standard when adopted early 2003 to specify: • Update to FGDC Element obligations • Consideration of community extensions for remote sensing, imagery, intelligence

21. Metadata Status • Contract to Intergraph to build XSLT transformation rules to translate FGDC V2 as XML into ISO 19115 as XML by June • Expert group in ANSI working on an Americas profile with Canada and OAS • Maximize support for legacy FGDC metadata

22. Recent Activity - Isite • Isite 2.08 is available for preliminary testing, including the long-awaited Isearch2 • Numerous bug fixes and several new features • Prerelease available at ftp.awcubed.com • Documentation is being updated now

23. Isearch2 Prerelease • Remote indexing - by URL • Files are retrieved and cached locally for search. • Headlines are stored separately for quick retrieval, original documents may be deleted but will be retrieved on demand • Not all document types support remote indexing - HTML and FGDC for now

24. Isearch-2 architecture ISite supports indexing of remote metadata to provide alternative to remote Z39.50 service Z39.50 zserver Isearch-2 index Remote Webservers with FGDC metadata list of URLs Iindex Internet http Local metadata

25. Isearch2 Prerelease - continued • Full capabilities of Isearch2 require installation of Berkeley DB • Distribution includes zlib (for compression of internal index tables) • Improved (and improving) XML handling • New applications (zsearch, zpresent, Iget) for XML-based interactions, with an Isearch DTD • Isearch-cgi port to Isearch2 nearly done

26. Isearch2 Prerelease - continued • Incorporated Isearch2 into Isite • Users can use either Isearch1 or Isearch2 behind the Z39.50 server • Improved separation of Z39.50 issues from the search engine - we want to make Isearch unaware of Z39.50 at the higher level • Z39.50 use attribute can now be mapped to more than one field • New Makefiles - need testing

27. GeoConnections Discovery Portal Status Report January 2002 Brian.McLeod@geocan.nrcan.gc.ca

28. Introduction • GeoConnections is Canada’s national program to foster the creation of the Canadian Geospatial Data Infrastructure (CGDI) • The GeoConnections Discovery Portal (formerly CEONet) allows for the exploitation of geospatial resources, achieved by providing a framework: • of core reusable services and components • for resource discovery, evaluation, access and monitoring • CGDI is an open peer-peer infrastructure • for the development and integration of geospatial services with the wider community • that provides for consumer and supplier autonomy

29. Provincial/ Marine SDI Other National SDI Discovery Portal Open Scaleable Infrastructure

30. Discover Resource Evaluate Resource Access Resource Browse Suppliers, Data and Services Graphically Display Location Data Service On-line Pricing Interactive Service Search for Suppliers, Data and Services Display Detailed Metadata Invoke Remote Service On-line Ordering Search Remote Supplier Directories Display Browse Data On-line Purchasing Chain and Integrate Service Subscribe to Services of Interest On-line User and Technical Guides On-line Delivery Universal Resource Access

31. Consumer(s) Supplier(s) Administrator Suppliers Catalogue Service Products Services Peer Data Directory e.g. NASA GCMD directory Peer Service Directory e.g. FGDC GEO Service Registry Broker Consumer(s) Consumer(s) Data Service Directory Service

32. Distributed Search Service Consumer Data Supplier Search service sends out several searches to relevant targets Web Browser Service Supplier Peer Directory DistributedSearchService Consumer or Application submits a single search OGC Services Directory Other national SDI Marine SDI Client Application Provincial SDI National Atlas

33. Developer Tool Inventory • MetaManager - Toolkit to enable RDBMS’s for FGDC/GEO distributed search and retrieval without need to modify the database; • Simple Search Toolkit - Allows suppliers to make their catalogue/database searchable through their existing web server (migration to OGC “stateless catalogue); • Earthscape “Family” - Set of simple map and reference components that are available for reuse by suppliers as part of their own web based search interfaces. • WebAPI - Capability for external web sites to invoke any CEONet service (e.g., list entries, search remote databases, …) or content through a web URL.

34. Earthscape II: Java-based map viewer client Place Name Look-up EarthscapeLite: HTML-based map viewer client Postal Code Look-up Free Re-usable Components Components provide for geospatial coordinate specification and map footprint display

35. Operational Statistics

40. V3.0 Features • robust database, faster indexing turnaround • fully bilingual entries • configurable results sorting • enhanced ‘Services’ including OGC support • staged metadata publishing • quality control tracking • “skinny” metadata form • user-based authentication Front-End Back-End Oracle Database V3.0 Alpha Release • includes product advertising, authentication • internal release last week V3.0 Final Release • beta release end of April • roll-out: early May • public release: June V3.0 Discovery Portal Front-End API Browser HTML Back-End API XML

41. Discovery Portal Front-End HTTP/HTML Back-End API Portals... XML Back-End Oracle Database Discovery Portal Post-v3.0 Releases Front-End API Browser HTML • meet high demand for content-only XML output - based on v3.0 architecture • the Front-End is just another portal - it is the GeoConnections Discovery Portal Back-End API XML • flexible metadata import/export via XML • support for CDN profile of ISO metadata profile (when available) • expanded user profiles, authentication schemes • possible Dublin Core alignment

42. Standards Leveraged • Metadata Standards • All directory information stored in XML • FGDC/CSDGM and DIF currently supported • Planned support: ISO 19115 (Canadian profile in development) • Information Retrieval Standards • Z39.50 · GEO Profile · Simple Search Protocol · IMS V0 • Planned support: OGC stateless catalogue specification • Data access • HTTP, FTP, mime-type association • OGC WebMapping specification • Service Model • As no ‘standards’ existed, model is CEONet defined • Planned support for: OGIS WebMapping services catalog (short term), ISO/OGC services work

43. Conclusions • Enabling technology: has brought on-line more than • 2000 organizations • 9000 collections • 300 services and • 250 remote catalogues connected • Open infrastructure: • wide standards support • interoperability demonstrated at national, provincial and international levels • Operational technology: • since May ‘97, frequent releases (every 3 or 4 months) • 24,000 user sessions per month • On-line at: http://www.geoconnections.org

44. CAP Awards 2002 • The contract announcement just went out for this year’s round of CAP awards • There is a category for integrating web mapping and feature access into existing Clearinghouse Nodes • Please read the announcement for more details: http://www.fgdc.gov/funding/cap2002.html

45. WebMap CAP • Special award category for multi-organizational groups that already operate a Clearinghouse Node and have a Web mapping service running • Goal is to provide assistance in integrating the discovery of data services (Z39.50 data catalog) with visualization capabilities (using OGC WMS 1.0) • Week-long training was held in September to provide instructions on extending existing map services and embedding links in metadata

46. Who’s participating? • Projects: • NOAA NGDC • North Carolina • New Mexico • Cornell U., NY • Mifflin Co, PA • MetroGIS, MN • Oregon Presenters: Doug Nebert, FGDC Nicole Soltyka and Tom McCarty, SAIC John Evans, NASA/GST Jeff Harrison, OGC Larry Bouzanne, Compusult • Nevada • Idaho • MIT • Arkansas • Alaska • Vermont • CIA

47. What parts of WebMapCAP are tried-and-true? • The use of OGC Web Map Service Specification Version 1.0 is well understood and deployed. Moreover, it is easy to understand and deploy! • The use of structured metadata to describe information resources, ala FGDC, is accepted and now supported in GIS software. • The use of a distributed search capability to find and deliver spatial information (Clearinghouse) is proven and growing.

48. What parts of WebMapCAP are still experimental? • The ability to encode data access or Web Map URLs in metadata is still at the proof-of-concept stage • The exact interaction of data and services metadata in special related catalogs in unclear. • The ability to locate and invoke services (e.g. Clearinghouse catalogs, Web Map Services, etc.) is still a subject of research and experimentation towards standardization.

49. Web Map CAP Flow edit data metadata load/edit GIS data edit collection metadata OGC Services Catalog index local data metadata set up OGC interface set up map server register node install search/map gateway Web Map Service Catalog Registry Metadata Index/ Server GIS Data which data? which nodes? customize search/map gateway query Search/map Gateway use search/map gateway metadata, map viewer map viewer

50. Where we are today • Data metadata don’t traditionally reference unambiguous invokable services (other than general HTTP and ftp) • Service metadata don’t (shouldn’t) describe data content very well and are not explicitly linked to deep data metadata where they exist. • Service metadata (e.g. capabilities.xml) not yet accessible through OGC Catalog Service interfaces (e.g. Z39.50) • Capabilities for various OGC services differ and must be systematically addressed • A services architecture for OGC is still being defined with conflicting interests: Catalog service approach, UDDI approach, OGC services catalog (Web Registry Service)