Barnessurface: black TIFF file as output

[sbalasub]

OutputBBox is an input to BarnesSurface, a vector feature collection process. It is missing the input field box.

Also missing for Heatmap, PointStacker

[sbalasub]

Also missing input field for Bounds of the grid in vec:Gri, Bounds of clipping rectangle in vec:RectangularClip.

[bartvde]

            <Input maxOccurs="1" minOccurs="1">
                <ows:Identifier>clip</ows:Identifier>
                <ows:Title>clip</ows:Title>
                <ows:Abstract>Bounds of clipping rectangle</ows:Abstract>
                <BoundingBoxData>
                    <Default>
                        <CRS>EPSG:4326</CRS>
                    </Default>
                    <Supported>
                        <CRS>EPSG:4326</CRS>
                    </Supported>
                </BoundingBoxData>
            </Input>

[bartvde]

@eshon any ideas on how to best create an input for a BBOX? Draw on the map, 4 input fields? Both?

[bartvde]

I'll start with the drag rectangle tool on a map

[bartvde]

see also #86

[bartvde]

so the draw rectange tool has been done, if we also need input fields please reopen @eshon

[eshon]

Text input option is necessary, it's too hard to draw precise coordinates on the map.

BBOX input is South, West + North, East? Then 2 input boxes:

East, North: __lon, lat___ West, South: lon, lat__

[bartvde]

also with tabs as used by map / WKT?

[eshon]

Sure

[bartvde]

initial pass is done, can definitely be improved though, but closing for now.

[sbalasub]

@bartvde, getting this in response M*

















�

�
(


B

C

D

�
E

S
�����
`



?���W���ՖY^�@k@C��jt3L?�






��y�� and the result is undefined.

[bartvde]

I had actually only tested with vec:RectangularClip will look into this

[sbalasub]

after saving output BBOX fields (via text) successfully and then returning back to that field, the fields are empty.

[bartvde]

@sbalasub ticketed separately as #117

[bartvde]

I just tried this out again, but it seems very slow on sfmta. Request seems to be okay though:

@dwins if you have time to verify the performance of this as well, it would be appreciated.

<p0:Execute xmlns:p0="http://www.opengis.net/wps/1.0.0" service="WPS" version="1.0.0">
    <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">vec:BarnesSurface</p1:Identifier>
    <p0:DataInputs>
        <p0:Input>
            <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">data</p1:Identifier>
            <p0:Reference xmlns:p3="http://www.w3.org/1999/xlink" p3:href="http://geoserver/wfs"
                method="POST" mimeType="text/xml">
                <p0:Body>
                    <p2:GetFeature xmlns:p2="http://www.opengis.net/wfs" service="WFS"
                        version="1.1.0" outputFormat="GML2">
                        <p2:Query typeName="sf:points" srsName="EPSG:4326"/>
                    </p2:GetFeature>
                </p0:Body>
            </p0:Reference>
        </p0:Input>
        <p0:Input>
            <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">valueAttr</p1:Identifier>
            <p0:Data>
                <p0:LiteralData>VALUE</p0:LiteralData>
            </p0:Data>
        </p0:Input>
        <p0:Input>
            <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">scale</p1:Identifier>
            <p0:Data>
                <p0:LiteralData>1</p0:LiteralData>
            </p0:Data>
        </p0:Input>
        <p0:Input>
            <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">outputBBOX</p1:Identifier>
            <p0:Data>
                <p0:BoundingBoxData crs="EPSG:4326">
                    <p1:LowerCorner xmlns:p1="http://www.opengis.net/ows/1.1">-5.7910994857000615
                        40.201331819433605</p1:LowerCorner>
                    <p1:UpperCorner xmlns:p1="http://www.opengis.net/ows/1.1">-5.6112661668192585
                        40.29746459823189</p1:UpperCorner>
                </p0:BoundingBoxData>
            </p0:Data>
        </p0:Input>
        <p0:Input>
            <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">outputWidth</p1:Identifier>
            <p0:Data>
                <p0:LiteralData>600</p0:LiteralData>
            </p0:Data>
        </p0:Input>
        <p0:Input>
            <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">outputHeight</p1:Identifier>
            <p0:Data>
                <p0:LiteralData>400</p0:LiteralData>
            </p0:Data>
        </p0:Input>
    </p0:DataInputs>
    <p0:ResponseForm>
        <p0:RawDataOutput>
            <p1:Identifier xmlns:p1="http://www.opengis.net/ows/1.1">result</p1:Identifier>
        </p0:RawDataOutput>
    </p0:ResponseForm>
</p0:Execute>

[bartvde]

it just came through actually, but it's all black

@volaya is there anything wrong in the params? I think I used the params you recommended today.

[dwins]

@bartvde It looks to me like we can expect Barnes interpolation to take a while for this request - there are a few thousand points being processed and it is superlinear time. I see that you also do not specify a format for the output - when I run this I get a GeoTiff result. If I open it in QGIS I have an appropriate ramp autogenerated. Apparently the range is only 1403.9 to 1414.5, which I would expect to appear as effectively black when viewed unscaled (the cell type is 32-bit floating point so 1400 is quite close to zero relatively speaking.)

We can probably find a better dataset to test the Barnes surface process with if that's what we want to do. Weather temperatures seem to be the typical use case.

[sbalasub]

@dwins @bartvde I tried with the example on this link http://suite.opengeo.org/4.1/cartography/rt/barnes.html and still get a black output (viewed in Qgis) if you have better data please send it along.

[bartvde]

@volaya do you know of a good dataset to use for Barnes Surface?