Conflation Rules 52North implementation and scenario

34 Copyright © 2014 Open Geospatial Consortium. An example taken from the scenario: { mappings: { address:address, name:geoNameCollection.memberGeoName.fullName }, fixedAttributeValues: { featureFunction-1:firefighting, restriction.securityAttributesGroup_resClassification :U } } The developed concept covers currently only simple rules for conflation scenarios, in which all features from the target dataset that do not exist in the source dataset are added to the result. It can be extended to allow more complex conflation scenarios, e.g. updating of source featuresattributes based on rules. Figure 20 — PYXIS interface to create and edit conflation rules.

8.2.1.4 Example execute request

The following is an example of a Execute request to execute the conflation process. In it you can see the 3 inputs source, target and rules, and the two elements of the requested response conflated_result and provenance: ?xml version=1.0 encoding=UTF-8 standalone=yes? wps:Execute service=WPS version=1.0.0 xmlns:wps=http:www.opengis.netwps1.0.0 xmlns:ows=http:www.opengis.netows1.1 xmlns:ogc=http:www.opengis.netogc xmlns:xlink=http:www.w3.org1999xlink xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:www.opengis.netwps1.0.0 http:schemas.opengis.netwps1.0.0wpsExecute_request.xsd ows:Identifierorg.n52.wps.server.algorithm.conflation.Kinda_Generic _ConflationProcessows:Identifier wps:DataInputs wps:Input Copyright © 2014 Open Geospatial Consortium. 35 ows:IdentifierSourceows:Identifier wps:Reference mimeType=textxml schema=http:schemas.opengis.netgml3.2.1gml.xsd xlink:href= http:services.interactive- instruments.dexsprojectsows10servicetds- dgiwgwfs?service=WFSamp;version=2.0.0amp;request=GetFeatureamp;name spaces=xmlnstds,http:metadata.dod.milmdrnsGSIP3.0tds3.0amp;t ypenames=tds:BuildingGeopointamp;FILTER=3CFilter20xmlns3D22http3A 2F2Fwww.opengis.net2Fogc2220xmlns3Atds3D22http3A2F2Fmetadata .dod.mil2Fmdr2Fns2FGSIP2F3.02Ftds2F3.0223E3CPropertyIsEqualTo 3E3CValueReference3Etds3AfeatureFunction- 13C2FValueReference3E3CLiteral3Efirefighting3C2FLiteral3E3C2F PropertyIsEqualTo3E3C2FFilter3E wps:Reference wps:Input wps:Input ows:IdentifierTargetows:Identifier wps:Reference mimeType=textxml schema=http:schemas.opengis.netgml3.1.1basegml.xsd xlink:href=http:portal.cubewerx.comcubewerxprojectsows9c ubeserv.cgi?service=WFSamp;datastore=OWS9amp;request=GetFeatureamp;t ypename=usgs:fireStationEmsStationamp;bbox=36.464,-122.003,36.714,- 121.667 wps:Input wps:Input ows:IdentifierRulesows:Identifier wps:Data wps:LiteralData{ mappings: { address:address, name:geoNameCollection.memberGeoName.fullName }, fixedAttributeValues: { featureFunction-1:firefighting, restriction.securityAttributesGroup_resClassification :U } }wps:LiteralData wps:Data wps:Input wps:DataInputs wps:ResponseForm wps:ResponseDocument wps:Output mimeType=textxml schema=http:schemas.opengis.netgml3.2.1gml.xsd ows:Identifierconflated_resultows:Identifier wps:Output wps:Output mimeType=textturtle ows:Identifierprovenanceows:Identifier wps:Output wps:ResponseDocument wps:ResponseForm wps:Execute In this execute request, the source and target datasets are specified by WFS HTTP GetFeature requests. Note that a FILTER= parameters is used to only request the fire stations see Figure 21. The rules are specified in the JSON format described in Subsection 8.2.1.3. As outputs the conflated dataset and the provenance are requested.