Opened 3 years ago

Closed 3 years ago

#807 closed defect (fixed)

ps_extra_metadata for ows type metadata incorrectly inserted into GetCapabilities (v9.0.3)

Reported by: jpass Owned by: pcampalani
Priority: critical Milestone: 9.0.x
Component: petascope Version: 9.0.0
Keywords: metadata ows coveragesummary Cc:
Complexity: Medium

Description

I've inserted multiple ows type metadata into the ps_extra_metadata table for example like the below code:

INSERT INTO ps_extra_metadata (coverage_id,metadata_type_id,value) VALUES (
(SELECT id FROM ps_coverage WHERE name = 'glasgow_bhse_b'),
(SELECT id FROM ps_extra_metadata_type WHERE type='ows'),
'<ows:Metadata
  xmlns:ows="http://www.opengis.net/ows/2.0"
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xlink:href="http://data.bgs.ac.uk/doc/Lexicon/NamedRockUnit/bhse.html"
  about="http://data.bgs.ac.uk/doc/Lexicon.html"/>');

This works and inserts the following record:

select * from ps_extra_metadata
where metadata_type_id = 1
and coverage_id = (SELECT id FROM ps_coverage WHERE name = 'glasgow_bhse_b');

 id | coverage_id | metadata_type_id | value
----+-------------+------------------+---------------------
 39 |         192 |                1 | <ows:Metadata\r
                                     :   xmlns:ows="http://www.opengis.net/ows/2.0"\r
                                     :   xmlns:xlink="http://www.w3.org/1999/xlink"\r
                                     :   xlink:href="http://data.bgs.ac.uk/doc/Lexicon/NamedRockUnit/bhse.html"\r
                                     :   about="http://data.bgs.ac.uk/doc/Lexicon.html"/>

The metadata that gets inserted into the GetCapabilities? response (rasdaman 9.0.3 rpm) is:

    <CoverageSummary>
      <CoverageId>glasgow_bhse_b</CoverageId>
      <CoverageSubtype>RectifiedGridCoverage</CoverageSubtype>
      <CoverageSubtypeParent>
        <CoverageSubtype>AbstractDiscreteCoverage</CoverageSubtype>
        <CoverageSubtypeParent>
          <CoverageSubtype>AbstractCoverage</CoverageSubtype>
        </CoverageSubtypeParent>
      </CoverageSubtypeParent>
      <BoundingBox xmlns="http://www.opengis.net/ows/2.0"
        crs="http://www.opengis.net/def/crs/EPSG/0/27700" dimensions="2">
        <LowerCorner>254750 659824.9</LowerCorner>
        <UpperCorner>265250 670024.9</UpperCorner>
      </BoundingBox>
      <Metadata xmlns="http://www.opengis.net/ows/2.0">
        <ows:Metadata 
          xlink:href="http://data.bgs.ac.uk/doc/Lexicon/NamedRockUnit/bhse.html" 
          about="http://data.bgs.ac.uk/doc/Lexicon.html"/>
      </Metadata>
    </CoverageSummary>

Unfortunately, this is invalid.

Change History (3)

comment:1 Changed 3 years ago by pcampalani

  • Status changed from new to accepted

True, thanks for this use case: I'll add a guard to let users insert either ows:Metadata sub-elements (like now is allowed) or directly including the root ows:Metadata.

comment:2 Changed 3 years ago by pcampalani

Fixed in changeset:8e3b54a. Now direct ows:Metadata can also be inserted in petascopedb::ps_extra_metadata.
Let me know James, thanks.

Last edited 3 years ago by pcampalani (previous) (diff)

comment:3 Changed 3 years ago by dmisev

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.