Changes between Version 4 and Version 5 of proposals/SOSHarvester


Ignore:
Timestamp:
May 18, 2011, 7:39:17 PM (13 years ago)
Author:
craigj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • proposals/SOSHarvester

    v4 v5  
    1313This proposal is to add the option to harvest service and observation offering metadata from the GetCapabilities document returned from an SOS server to the OGC WxS Harvester.
    1414
    15 This proposal also adds the ability to specify schema specific mappings for OGC WxS harvesters including plugin profiles (this harvester was originally designed for the iso19139.mcp profile).
     15This proposal also adds the ability to specify schema specific mappings for OGC WxS harvesters including plugin schemas (this harvester was originally designed for the iso19139.mcp profile).
    1616
    1717=== Proposal Type ===
     
    3131
    3232== Motivations ==
    33 The marine community in Australia is increasingly looking to make use of OGC Sensor Observation services to publish marine data with many services already being made available.  The addition of an SOS harvesting option to geonetwork will facilitate the discovery and access of these services via the Australian Oceans Data Network (AODN) by making it a simple process to publish service details to the AODN's service/dataset catalog (the ANZ-MEST/geonetwork).
     33The marine community in Australia is increasingly looking to make use of OGC Sensor Observation services to publish marine data with many services already being made available.  The addition of an SOS harvesting option to geonetwork will facilitate the discovery and access of these services via the Australian Oceans Data Network (AODN) by making it a simple process to publish service details to the AODN's service/dataset catalog (the ANZ-MEST/geonetwork) or to contributing catalogs.
    3434
    3535== Proposal ==
     
    7070When a particular OGC Service type is selected in the OGC WxS harvester, all registered schema directories will be scanned to determine which schemas support harvesting metadata for that particular type and the user will be able to select the target schema to use in the harvester:
    7171
    72 [[Image(target-schema.png)]
     72[[Image(target-schema.png)]]
     73
     74=== SOS GetCapabilities Harvester ===
     75
     76This proposal also adds the option to harvest metadata from an OGC Sensor Observation Service GetCapabilities response to the OGC WxS Harvester, in particular an OGC Sensor Observation Service compliant with version 1.0.0 of the specification.
     77
     78Under this proposal "OGC Sensor Observation service (1.0.0)" will be added to list of possible OGC WxS service types that can be harvested using this harvester:
     79
     80When this option is selected, the harvester will harvest service metadata from the GetCapabilities statement returned from the specified SOS endpoint using the service metadata stylesheet for the selected target schema. 
     81
     82Additionally, if the "Create metadata for layer elements using GetCapabilities information" option is selected, the harvester will harvest resource metadata for each Observation Offering listed in the GetCapabilities response using the resource metadata stylesheet for the selected target schema.
     83
     84An iso19119/iso19139 service metadata stylsesheet and a sample iso19115/iso19139 resource metadata stylesheet is included with this proposal (we will be using the iso19139.mcp mapping to be made available in the schema plugin for this profile).   
     85
     86The mappings for these transformations are as follows:
     87
     88
     89
     90
     91
    7392
    7493=== Backwards Compatibility Issues ===