Changes between Version 15 and Version 16 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
06/11/09 10:22:07 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v15 v16  
    145145    author contains "lawrence" 
    146146}}} 
     147 
     148=== Spatial searching : <spatialOperator> and <boundingBox> === 
     149The search may incorporate a spatial query to restrict results to those metadata records having spatial coverage(s) matching the search criteria defined by the <boundingBox> elements <limitNorth>, <limitEast>, <limitSouth>, <limitWest>. Coordinates should be in decimal lat/lon (* although an optional element <spatialReferenceSystem> may be populated with an entry from the [#spatialReferenceSystem spatialReferenceSystem] list to specify the spatial reference system (SRS) of the bounding box coordinates. (*Note : this feature is included for future development e.g. ability to supply spatial search coordinates in British National Grid coordinates. Currently the only supported SRS is EPSG:4326 (WGS84 lat/lon). 
     150An optional <spatialOperator> may be included, populated with a term from the [#spatialOperatorList spatialOperatorList], defining the method by which the search should be compared to spatial coverage(s) related to metadata records. Note that in the discovery index database, metadata records may contain several spatial coverages, so a match can occur if any of the spatial coverages related to the metadata item match the criteria specified in the search. 
     151 
     152If <spatialOperator> is omitted, but a valid <boundingBox> is supplied, the default operator applied is overlaps. Values for <limitNorth>, <limitSouth>, <limitEast> and <limitWest> should be given in decimal degrees latitude and longitude. <limitNorth> and <limitSouth> must be in the range -90.0 to +90.0, with <limitNorth> greater than <limitSouth>. <limitWest> and <limitEast> must be in the range -180.0 to 180.0 and <limitEast> should be greater than <limitWest>. Bounding boxes that span the -180 degree meridian, or the poles, are not currently supported. 
     153 
     154Spatial searches (as a further restriction of "term" searches) are currently implemented by obtaining a resultset from the term search, obtaining a result set from the spatial search, then returning the intersection of the two result sets. 
     155 
     156=== Temporal searching : <DateRange> === 
     157Full-text, author or parameter searches my optionally be combined with a further restriction that the temporal coverage ovelaps the specified <DateRange>. Both <DateRangeStart> and <DateRangeEnd> must be specified and must be valid dates of the form YYYY-MM-DD. TODO: it is planned to implement a choice of <temporalOperator> in a similar manner to <spatialOperator>. 
    147158 
    148159=== Paging : <start> and <howMany> ===  
     
    178189If <scope> is omitted, the search is not restricted in this way. 
    179190 
    180 === Spatial searching : <spatialOperator> and <boundingBox> === 
    181 Full-text, author or parameter searches, as described above, may optionally be combined with a further restriction that the spatial coverage described in the metadata records match, according to the specified <spatialOperator>, the specified spatial <boundingBox>. <spatialOperator> may be populated with any of the values from the spatialOperatorList accessible via the getList operation. Currently, supported values are: 
    182  
    183   overlaps (default):: 
    184  
    185   doesNotOverlap:: 
    186  
    187   within:: 
    188  
    189 If <spatialOperator> is omitted, but a valid <boundingBox> is supplied, the default operator applied is overlaps. Values for <limitNorth>, <limitSouth>, <limitEast> and <limitWest> should be given in decimal degrees latitude and longitude. <limitNorth> and <limitSouth> must be in the range -90.0 to +90.0, with <limitNorth> greater than <limitSouth>. <limitWest> and <limitEast> must be in the range -180.0 to 180.0 and <limitEast> should be greater than <limitWest>. Bounding boxes that span the -180 degree meridian, or the poles, are not currently supported. 
    190  
    191 Spatial searches (as a further restriction of "term" searches) are currently implemented by obtaining a resultset from the term search, obtaining a result set from the spatial search, then returning the intersection of the two result sets. 
    192  
    193 === Temporal searching : <DateRange> === 
    194 Full-text, author or parameter searches my optionally be combined with a further restriction that the temporal coverage ovelaps the specified <DateRange>. Both <DateRangeStart> and <DateRangeEnd> must be specified and must be valid dates of the form YYYY-MM-DD. TODO: it is planned to implement a choice of <temporalOperator> in a similar manner to <spatialOperator>. 
    195  
    196191== Search results == 
    197192The doSearchResponse message is defined in the WSDL as shown below: 
     
    309304 
    310305=== spatialOperatorList === 
     306  overlaps (default):: 
     307 
     308  doesNotOverlap:: 
     309 
     310  within:: 
     311 
     312 
    311313=== spatialReferenceSystemList === 
     314  EPSG:4326:: 
     315 
    312316=== dateRangeTargetList === 
    313317=== temporalOperatorList ===