Presentation is loading. Please wait.

Presentation is loading. Please wait.

Clearinghouse WG Telecon Agenda and Presentations January 29, 2002.

Similar presentations


Presentation on theme: "Clearinghouse WG Telecon Agenda and Presentations January 29, 2002."— Presentation transcript:

1 Clearinghouse WG Telecon Agenda and Presentations January 29, 2002

2 Agenda zIntroductions (5 min) zClearinghouse Node Status (5 min) zClearinghouse Registration Revision (5 min) zISO Metadata Software – Enraemed (5 min) zFGDC to ISO Metadata Transition (5 min) zIsite Software Status (10 min) zCanadian Clearinghouse: GeoConnections (15 min) zIntegration of Clearinghouse and Web Mapping Services - WebMapCAP (15 min) zProposed NSDI Technical Workshop, April 29 – May 1, 2002 Denver CO (10 min) zWrap-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 z278 Clearinghouse Servers Registered y247 – Active Status xSome are down or improperly registered Reflect Negatively on the Status Page and in Searches Need to Upgrade Software or GEO Version Information y 31 - Not Active Status y 19 – Pending Status xNew Registry Wizard will Resolve

7 New Registry Wizard Functions

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

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

10

11 Registry Wizard Modify An Existing Node zRegistry Modify yCurrently In Development xAllow User the Ability to Modify Existing Node Information Performs All Node Tests Extracts: –Server IP Address, Software Name & Version, Geo Value xAutomatically Updates Database Time Spent in Pending Database is eliminated

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

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

14 Enraemed Metadata Software

15  Develop by Dutch Donor Agency for the Ethiopian Government z Being used within Ethiopia by all governmental institutions z Willingness to hand over software to FGDC for maintenance

16 Enraemed Metadata Software Features  ISO, FGDC, GILS, and DC compliant z Stand Alone or Client–Server y Backend Database xMSDE, MS SQL Server, Access2000 zGlobally unique IDs zElement Navigator y Elements of selected standard y Mandatory-optional-mandatory y Jump function

17 Enraemed Logon

18 Enraemed Navigator

19 View – Page - Elements

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

21 Metadata Status zContract to Intergraph to build XSLT transformation rules to translate FGDC V2 as XML into ISO as XML by June zExpert group in ANSI working on an Americas profile with Canada and OAS zMaximize support for legacy FGDC metadata

22 Recent Activity - Isite zIsite 2.08 is available for preliminary testing, including the long-awaited Isearch2 zNumerous bug fixes and several new features zPrerelease available at ftp.awcubed.com zDocumentation is being updated now

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

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

25 Isearch2 Prerelease - continued zFull capabilities of Isearch2 require installation of Berkeley DB zDistribution includes zlib (for compression of internal index tables) zImproved (and improving) XML handling zNew applications (zsearch, zpresent, Iget) for XML-based interactions, with an Isearch DTD zIsearch-cgi port to Isearch2 nearly done

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

27 Status Report January 2002 GeoConnections Discovery Portal

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

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

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

31 Directory Service ProductsProductsServicesServices SuppliersSuppliersConsumer(s)Administrator Supplier(s) Catalogue Service Broker Peer Service Directory e.g. FGDC GEO Service Registry Peer Service Directory e.g. FGDC GEO Service Registry Consumer(s) Peer Data Directory e.g. NASA GCMD directory Peer Data Directory e.g. NASA GCMD directory Consumer(s) DataService

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

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

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

35 Operational Statistics

36

37

38

39

40 V3.0 Discovery Portal Back-End Back- End API XML Browser Oracle Database Front-End API 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 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 HTML

41 Browser Post-v3.0 Releases 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 Front-End HTML Front-End API 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 Discovery Portal Back-End XML Oracle Database Back- End API Discovery Portal Portals... Back-End API XML HTTP/ HTML

42 Standards Leveraged zMetadata Standards yAll directory information stored in XML yFGDC/CSDGM and DIF currently supported yPlanned support: ISO (Canadian profile in development) zInformation Retrieval Standards yZ39.50 · GEO Profile · Simple Search Protocol · IMS V0 yPlanned support: OGC stateless catalogue specification zData access yHTTP, FTP, mime-type association yOGC WebMapping specification zService Model yAs no ‘standards’ existed, model is CEONet defined yPlanned support for: OGIS WebMapping services catalog (short term), ISO/OGC services work

43 Conclusions zEnabling technology: has brought on-line more than y2000 organizations y9000 collections y300 services and y250 remote catalogues connected zOpen infrastructure: ywide standards support yinteroperability demonstrated at national, provincial and international levels zOperational technology: ysince May ‘97, frequent releases (every 3 or 4 months) y24,000 user sessions per month zOn-line at:

44 CAP Awards 2002 z The contract announcement just went out for this year’s round of CAP awards z There is a category for integrating web mapping and feature access into existing Clearinghouse Nodes z Please read the announcement for more details:

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

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

47 What parts of WebMapCAP are tried-and-true? zThe use of OGC Web Map Service Specification Version 1.0 is well understood and deployed. Moreover, it is easy to understand and deploy! zThe use of structured metadata to describe information resources, ala FGDC, is accepted and now supported in GIS software. zThe 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? zThe ability to encode data access or Web Map URLs in metadata is still at the proof-of- concept stage zThe exact interaction of data and services metadata in special related catalogs in unclear. zThe 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 collection metadata edit data metadata register node index local data metadata install search/map gateway customize search/map gateway use search/map gateway Metadata Index/ Server Web Map Service Catalog Registry Search/map Gateway which nodes? which data? metadata, map viewer query OGC Services Catalog map viewer set up OGC interface set up map server load/edit GIS data GIS Data

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

51 Where we want to be this year In the life of these CAP projects we intend to: zClarify the relationship between data and services metadata management at the service node (your mapserver/metadata server) zEstablish a registry of eligible WMS capabilities among the CAP and other projects for general use zExperiment with a broker gateway that will match data content and service requests for the client zStand up OGC WMS services at all CAP projects zEstablish WMS viewer portals at all CAP project community portals that include search and display of local and national data sources

52 NSDI Technical Workshop z Objectives: y to demonstrate and discuss how the various elements of NSDI, its standards and practices can work together y to document a vision for building a coordinated NSDI for all participants z When: April 29 – May 1, 2002 (3 days) z Where: Denver Federal Center, Lakewood, Colorado

53 Suggested Content zIntroduction to standard spatial services from OGC, ISO, the Web zUse of common thesauri and gazetteers in NSDI zMetadata tutorial zSDI solutions exhibition zResource Discovery z Framework and GeoData Models for all participants z Geospatial One-Stop z Data Access and Service over the Web z Infrastructure support for models and applications

54 Request your participation z Are looking for presentation and facilitation volunteers or ideas of what information you’d want to learn about z Can support up to 160 participants with a large presentation room, a break-out room, and a training room available z Please contact me with your interests and questions:

55 Wrap Up Items z


Download ppt "Clearinghouse WG Telecon Agenda and Presentations January 29, 2002."

Similar presentations


Ads by Google