Loading...
 
ESA > Join & Share > Forums > WebMapViewer Forum > Problem with Catalogue Interface: OGC 06-079r2 , EO Application Profile for CSW 2.0

WebMapViewer Forum

Help

Show posts:
Jump to forum:

Problem with Catalogue Interface: OGC 06-079r2 , EO Application Profile for CSW 2.0

Hi,

I registered a service with the following wizard:
Catalogue Interface: OGC 06-079r2 , EO Application Profile for CSW 2.0
This interface provides access to Earth observation product catalogues and was defined and prototyped in the HMA project.

My problem is that the polygon results are not displayed on the MapViewer, namely the corresponding polygons are not displayed with the blue line on the Viewer screen. The SSE gets the following reply message from the BPEL workflow.

I think the embeddedResult element contains the correct Feature/GML representation. I copied the "featureCollection" part from the result an tested it with the http://services-test.eoportal.org/portal/DownloadExternalUtil.jsp?pageName=mapTools test tool and it displayed correctly.

What message should my service respond with in order to be displayed on the MapViewer?
Thanks,
Akos

<portalSearchOutputMessage>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="parameters">
<multiCataloguesSearchOutputMsg xmlns="http://www.esa.int/sse_hma">
<portal:statusInfo xmlns:portal="http://www.esa.int/mass">
<portal:statusId>0</portal:statusId>
<portal:statusMsg>successful</portal:statusMsg>
</portal:statusInfo>
<searchOutput>
<sse:statusInfo xmlns:sse="http://www.esa.int/mass">
<sse:statusId>0</sse:statusId>
<sse:statusMsg>successful</sse:statusMsg>
</sse:statusInfo>
<hits>1</hits>
<cursor>1</cursor>
<sse:parentId xmlns:sse="http://www.esa.int/mass">urn:HMA:PHR_catalog:PHR</sse:parentId>
<retrievedData presentation="summary">
<portalMetadata>
<sse:id xmlns:sse="http://www.esa.int/mass">urn:HMA:PHR_catalog:PHR:DS_2044263010822</sse:id>
<sse:parentId xmlns:sse="http://www.esa.int/mass">urn:HMA:PHR_catalog:PHR</sse:parentId>
<hma:EarthObservationProduct xmlns:hma="http://earth.esa.int/hma" xmlns="http://earth.esa.int/XML/eoli" xmlns:eoli="http://earth.esa.int/XML/eoli" xmlns:gml="http://www.opengis.net/gml" xmlns:ows="http://www.opengis.net/ows" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" gml:id="DS_2044263010822">
<hma:identifier>urn:HMA:PHR_catalog:PHR:DS_2044263010822</hma:identifier>
<hma:parentIdentifier>urn:HMA:PHR_catalog:PHR</hma:parentIdentifier>
<hma:acquisitionType>NOMINAL</hma:acquisitionType>
<hma:productType>productTypeValue</hma:productType>
<hma:status>ACQUIRED</hma:status>
<hma:startDate>2001-08-22T11:02:47.000</hma:startDate>
<hma:completionDate>2001-08- 22T11:02:47.999</hma:completionDate>
<gml:extentOf>
<gml:Polygon srsName="EPSG:4326">
<gml:exterior>
<gml:LinearRing>
<gml:posList>50.496645 30.510485 50.496645 10.184483 10.098868 10.184438 10.098868 30.510485 50.496645 30.510485</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</gml:extentOf>
<hma:acquiredBy>
<hma:Platform>
<hma:shortName>SPOT</hma:shortName>
<hma:serialIdentifier>2</hma:serialIdentifier>
</hma:Platform>
<hma:Instrument>
<hma:shortName>PHR</hma:shortName>
</hma:Instrument>
</hma:acquiredBy>
</hma:EarthObservationProduct>
</portalMetadata>
</retrievedData>
<sse:viewEmbeddedResult xmlns:sse="http://www.esa.int/mass" xmlns:hma="http://earth.esa.int/hma" xmlns:csw="http://www.opengis.net/cat/csw" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<sse:embeddedResult>
<featureCollection xmlns="http://www.esa.int/xml/schemas/mass/serviceresult">
<gml:boundedBy xmlns:gml="http://www.opengis.net/gml">
<gml:Box srsName="EPSG:4326">
<gml:coordinates>-180,-90 180,90</gml:coordinates>
</gml:Box>
</gml:boundedBy>
<gml:featureMember xmlns:gml="http://www.opengis.net/gml">
<Feature>
<id>urn:HMA:PHR_catalog:PHR:DS_2044263010822</id>
<tooltip>HMA:urn:HMA:PHR_catalog:PHR:DS_2044263010822</tooltip>
<attribute12>Product Status,ACQUIRED</attribute12>
<attribute13>Start Date,2001-08-22T11:02:47.000</attribute13>
<attribute14>End Date,2001-08- 22T11:02:47.999</attribute14>
<Geometry>
<gml:Polygon srsName="EPSG:4326">
<gml:outerBoundaryIs>
<gml:LinearRing>
<gml:coordinates>30.510485,50.496645 10.184483,50.496645 10.184438,10.098868 30.510485,10.098868 30.510485,50.496645</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</Geometry>
</Feature>
</gml:featureMember>
</featureCollection>
</sse:embeddedResult>
<sse:embeddedType>GML</sse:embeddedType>
</sse:viewEmbeddedResult>
<sse:viewEmbeddedResult xmlns:sse="http://www.esa.int/mass">
<sse:embeddedResult>
<Folder xmlns="http://www.esa.int/mass">
<open>1</open>
<name>urn:HMA:PHR_catalog:PHR</name>
<Placemark xmlns="http://earth.google.com/kml/2.0">
<styleUrl>#sse</styleUrl>
<description>
<html>
<table>
<tr>
<td>
<table>
<tr>
<td>Start Date</td>
<td>2001-08-22T11:02:47.000</td>
</tr>
<tr>
<td>End Date</td>
<td>2001-08- 22T11:02:47.999</td>
</tr>
</table>
</td>
<td/>
</tr>
</table>
</html>
</description>
<name>urn:HMA:PHR_catalog:PHR:DS_2044263010822</name>
<GeometryCollection>
<Point>
<coordinates>NaN,NaN</coordinates>
</Point>
<LinearRing>
<coordinates>30.510485,50.496645 10.184483,50.496645 10.184438,10.098868 30.510485,10.098868 30.510485,50.496645</coordinates>
</LinearRing>
</GeometryCollection>
</Placemark>
</Folder>
</sse:embeddedResult>
<sse:embeddedType>KML</sse:embeddedType>
</sse:viewEmbeddedResult>
</searchOutput>
</multiCataloguesSearchOutputMsg>
</part>
</portalSearchOutputMessage>


Re: Problem with Catalogue Interface: OGC 06-079r2 , EO Application Profile for CSW 2.0

Hi Akos.

A few tips:

- you have two sse:viewEmbeddedResult elements in your message, one for GML and one for KML. According to the schemas this is valid, but I'm not sure how the SSE behaves in these cases. Anyway, I suggest to include only one of them in the message to isolate the problem (GML, KML or both). You should also be aware that we are investigating a similar problem related to displaying KML. But GML should work without any problems.

- a common reason why footprints are not displayed is the presence of line breaks (CR, LF) or other problematic characters inside the embeddedResult element. This doesn't work because the content of the element is passed as a parameter to a Javascript function. The content should be all on the same line. See page 41 of the ICD, section 3.2.3.10 for the explanation. You can either make sure that no line breaks are generated from your backend or add <xsl:strip-space elements="*"/> to the beginning of your stylesheet.

- Your KML has embedded HTML. Possibly you will need to use CDATA sections to wrap it.

If you still have problems, let us know the name of the service so we can take a closer look.

Paulo



Show posts:
Jump to forum: