From MapbenderWiki

Contents 1 Introduction 1.1 Problems 1.2 TODOs 1.3 User Interface for Testing services 1.3.1 Demo REQUESTs 1.4 Client Interface 1.4.1 Search Interface 1.4.2 Results 1.4.3 Visualization 1.5 Admin Interface

Introduction

The OGC Catalogue Service is a service which can used to search or adminstrate geospatial metadata. There exists one abstract specification which defines a low level (minimum) interoporability between different communities who deal with geospatial information. On base of this Spec there are many different profiles which specify some further functionality and which are based on own information models. The problem is, that a search Interface which will be implemented in Mapbender should modular work with different profiles of the base OGC CAT 2.0.2. The first thing is to support some parts of the base functionality wich is documented in http://portal.opengeospatial.org/files/?artifact_id=20555. The most relevant pages are:1-65 & 115-176 (base concept and http binding). The specification allow different kinds of bindings and different ways of defining the search filter (like sql's where clause). For the implementation in mapbender the http binding and the Filter Encoding for defining the Query should be used. Beside the abstract spec there is a profil which will be used be some european authorities to exchange metadata for the european sdi. This profil can be found here: http://portal.opengeospatial.org/files/?artifact_id=21460. With this profile it should be easier to create a search interface with defined categories, cause the information model is hardly defined. This profil should be supported too. Supporting different profiles should be possible after implementation. Therefor the database structure shouldn't be hardcoded to the ISO Profil. Maybe someone could think after collecting xslt files which transform one metadata set into another one which has another profile. Could be used for transforming CAT 2.0.2 or CSW AP ISO 1.0 metadata into a so called mapbender-view.

Problems

• There are not many Implementation of CSW 2.0.2 in the world!
• The different profiles make it difficult to make a harmonized search interface.
• Many Servers don't fully support the complex Specification - somewhat buggy!!
• Some Operations are not available through http get - tests become more time consuming!
• The complex functionality makes it difficult to create a database schema for administrate them in the mapbender-db.

TODOs

1. Find different Implementations of CAT 2.0.2
   1. CAT 2.0.2 - not AP ISO 1.0
      1. http://apollo.erdas.com/apollo-catalog/wrs/WRS?request=GetCapabilities&version=2.0.2&service=CSW
      2. http://geomatics.nlr.nl/excat/csw?request=GetCapabilities&service=CSW&version=2.0.2
      3. http://geossregistries.info:1090/GEOSSCSW202/discovery?Request=GetCapabilities&Service=CSW&Version=2.0.2
      4. http://www.geodata.alterra.nl/excat/csw?request=GetCapabilities&service=CSW
      5. http://gesg.gmu.edu:8082/aq202/srv/en/csw?request=GetCapabilities&service=CSW&version=2.0.2
      6. http://geonovum.nitg.tno.nl:8080/geonetwork/srv/en/csw?request=GetCapabilities&service=CSW&version=2.0.2
      7. http://geossregistries.info:1090/GEOSSCSW202/discovery?Request=GetCapabilities&Service=CSW&Version=2.0.2
      8. http://enviroinfo.enviroportal.sk/csw/index.php?service=CSW&request=GetCapabilities&VERSION=2.0.2&typeNames=service
      9. Possible AP ISO 1.0 too? -- http://www.gdi-rp-dienste3.rlp.de/geonetwork/srv/en/csw?request=GetCapabilities&VERSION=2.0.2&service=CSW
         • Problem: There is no POST operation defined for getrecords in geonetwork242!!!! This must defined by hand in the mb_database
      10. http://grid1.cos.gmu.edu/geonetwork/srv/csw?SERVICE=CSW&REQUEST=GetCapabilities - OneGeology Project - found by Google inurl:geonetwork/srv/en/csw out of the box - geonetwork trunk?
   2. CAT 2.0.2 - AP ISO 1.0
      1. http://gdi-de.sdisuite.de/soapServices/CSWStartup?request=GetCapabilities&service=CSW&VERSION=2.0.2 - SOAP 1.2, Conterra TestCatalog - Is the <csw:ElementSetName>brief</csw:ElementSetName> tag really mandatory??
      2. http://213.144.28.209/csw - SOAP 1.2, PortalU DE Test-interface
      3. http://78.46.82.146:80/csw/services - SOAP 1.2, BBSR
      4. http://www.portalu.de/csw202?REQUEST=GetCapabilities&VERSION=2.0.2&SERVICE=CSW - USE THIS SERVICE FOR TESTING
      5. ...
2. Define the use cases for distributed search out of mapbender
   1. Resource Types
      1. dataset
      2. WMS
      3. WFS?
      4. dataseries
      5. ...
   2. How to handle the different founded resource types
      1. Load WMS
      2. View extent (bbox) on map
      3. ...
3. Define the most needed operations:
   1. GetCapabilities
   2. GetRecords
   3. DescribeRecord?
   4. GetRecordById
4. Example urls for the operations
   1. GetRecords
      1. http://geomatics.nlr.nl/excat/csw?request=GetRecords&service=CSW&version=2.0.2&ResultType=results&TypeName=csw:Record&TYPENAMES=csw:dataset
   2. GetRecordById
      1. http://geomatics.nlr.nl/excat/csw?request=GetRecordById&service=CSW&version=2.0.2&Id={48DA6486-5BD3-4B23-8658-C7E93CCEE535}&ElementSetName=full
5. Define typeName to support
   1. csw:Record - Standard
   2. gmd:MD_Metadata - If catalogue supports Profil ISO AP 1.0 too
6. Create a definition of a internal storage format (information model) for external metadate for mapbender.
7. Mapbender database schema
   1. Draft for table cat
      1. CREATE TABLE cat ( cat_id serial NOT NULL, cat_version character varying(50) NOT NULL DEFAULT ''::character varying, --cat_name character varying(255), cat_title character varying(255) NOT NULL DEFAULT ''::character varying, cat_abstract text, --cat_keywords do we need them? There maybe a special table? --Relevant Operations Metadata Sections in XML cat_op_getcapabilities text NOT NULL DEFAULT ''::text, cat_op_describerecord text, cat_op_getrecords text, cat_op_getrecordbyid text, --UploadUrl cat_upload_url character varying(255), fees character text, accessconstraints text, --ServiceProvider providername character varying(255), providersite character varying(255), --ServiceContact individualname character varying(255), positionname character varying(255), --ContactInfo --Phone voice character varying(255), facsimile character varying(255), --Address deliverypoint character varying(255), city character varying(255), administrativearea character varying(255), postalcode character varying(255), country character varying(255), electronicmailaddress character varying(255), --Whole Cap-doc cat_getcapabilities_doc text, --Information about Owner cat_owner integer, --Actuality cat_timestamp integer, CONSTRAINT pk_cat_id PRIMARY KEY (cat_id) ) WITHOUT OIDS;
   2. Create db tables to administrate the content of the capabilities in the mapbender-db. There are 3 ways:
      1. Put the whole XML in one field.
      2. Convert the capabilities schema to a complex relational schema.
      3. Do a mix of both, like it is done for wms and wfs.
8. Create the functions/classes to access the relevant information out of the services
   1. First only http-get and http-post after the base specification table 54 page 123 (mandatory operations):
      1. GetCapabilities: GET-KVP
      2. GetRecords: POST-XML
      3. GetRecordById: GET-KVP
      4. DescribeRecord: POST-XML
9. Client Interface
   1. Define different filter possibilities for CAT 2.0.2 and CSW AP ISO 1.0.0
      1. Filters for abstract CAT csw:Record type, Common queryable elements (page 20 Table 1)
         1. Subject-dc:subject
         2. Title-dc:title
         3. Abstract-dct:abstract
         4. AnyText
         5. Format-dc:format
         6. Identifier-dc:identifier
         7. Modified-dct:modified
         8. Type-dc:type
         9. BoundingBox-ows:BoundingBox
         10. CRS
         11. Association-compound element
      2. Filters for CSW AP ISO 1.0.0

User Interface for Testing services

http://www.gdi-rp-dienste3.rlp.de/mapbender/tools/send_post_curl.php ask for username and password: armin.retterath(at)lvermgeo.rlp.de

or download (and install php5-curl)

https://svn.osgeo.org/mapbender/trunk/mapbender/tools/send_post_curl.php

Demo REQUESTs

1. Conterra Ref Implementation for CSW 2.0.2 AP ISO 1.0
   • SOAP URL: http://gdi-de.sdisuite.de/soapServices/services/CSWDiscovery, POST XML URL: http://gdi-de.sdisuite.de/soapServices/CSWStartup
   1. GetRecords(via SOAP or POST):<GetRecords xmlns="http://www.opengis.net/cat/csw/2.0.2" xmlns:gmd="http://www.isotc211.org/2005/gmd" maxRecords="5" outputFormat="application/xml" outputSchema="http://www.isotc211.org/2005/gmd" resultType="results" service="CSW" startPosition="1" version="2.0.2"> <csw:Query typeNames="gmd:MD_Metadata"> <csw:ElementSetName>brief</csw:ElementSetName> </csw:Query> </GetRecords>
   2. <GetRecords xmlns="http://www.opengis.net/cat/csw/2.0.2" xmlns:gmd="http://www.isotc211.org/2005/gmd" maxRecords="10" outputFormat="application/xml" outputSchema="http://www.opengis.net/cat/csw/2.0.2" resultType="results" service="CSW" startPosition="1" version="2.0.2"> <csw:Query typeNames="csw:Record"> <csw:ElementSetName>full</csw:ElementSetName> </csw:Query> </GetRecords>

Client Interface

Search Interface

• Fields
  • Mandatory Fields
    • Single Text Field
  • Optional Fields
    • Spatial Restriction/Extent/Bounding Box - use MB's current extent
      • Constraints Configurable: Anywhere, Intersects, Within
      • Allow to change values???
    • INSPIRE metadata profile
• Constraints
  • Pickup current extent and use it - allow to change extent?
  • Only show metadata of data displayable on a map
    • WMS, Layers, GML...
    • Show this as an option?

Results

• Fields
  • List result sets
  • Various icons for various types of result sets (applications, services, metadata, optional: WMC, OWS Context)
• Constraints
  • Results returned as JSON
  • map result sets to catalogs ??
  • (o) load individual layers as WMS (some WMS have 1000+ layers)

Visualization

• Display results in map
  • Zoom to extent
  • Features with metadata in JS (Usemap)

Admin Interface