[GIS] Waiting for Vector & WFS loading

loadingopenlayers-2wfs

user borrowed from friend

since i use vector layer with wfs protocol, there is a little while before features loaded on the map. So i need to tell user to wait a moment until they load.

what best way to do that ?
i found this http://osgeo-org.1560.n6.nabble.com/Patch-quot-waiting-quot-mouse-cursor-on-WFS-loading-td3961983.html

but not sure if it will work. any body tried it ?

Best Answer

There is the LoadingPanel addin: http://trac.osgeo.org/openlayers/wiki/Addins/LoadingPanel

This could easily be altered to show a "waiting cursor" by altering the "minimizeControl" and "maximizeControl", removing the

this.div.style.display = "none";
this.div.style.display = "block";

lines and adding:

document.body.style.cursor='auto'
document.body.style.cursor='wait'

Related Solutions

[GIS] OpenLayers WFS protocol query after vector layer creation

You should be able to set a defaultFilter, or once the protocol is created you can use mergeWithDefaultFilter.

var protocol = new OpenLayers.Protocol.WFS({
    version: "1.1.0",
    url: MapBase.Configuration.GeoServer.WFS_Service.EndPointURL,
    featurePrefix: MapBase.Configuration.GeoServer.WFS_Service.featurePrefix,
    featureType: MapBase.Configuration.GeoServer.WFS_Service.featureType,
    featureNS: MapBase.Configuration.GeoServer.WFS_Service.featureNS,
    geometryName: MapBase.Configuration.GeoServer.WFS_Service.geometryName,
    srsName: "EPSG:4326",
    defaultFilter: myFilter
});

protocol.mergeWithDefaultFilter(myNewFilter);

For the projection you can add in the following for WFS 1.1.0:

srsName: "EPSG:4326"

A few more details here.

OpenLayers WFS Vector Layer – Verify All Features Returned from Server

Assuming your are using OpenLayers.Protocol.WFS, then you have something like this and you can provide a callback when you call the read operation on the protocol:

The call back has an OpenLayers.Protocol.Response object. This object has an error property that will let you know of any errors.

    var protocol = new OpenLayers.Protocol.WFS({
        version: "1.1.0",
        url: xxx
        featurePrefix: xxx
        featureType: xxx
        featureNS: xxx
        geometryName: xxx
//        defaultFilter: searchFilter,
        srsName: xxx
    });

    var response = protocol.read({
        maxFeatures: 100,
        callback: _CallBack
    });

   function _CallBack (resp) {
        console.log(resp);
        console.log(resp.error);
    });

enter image description here

Update

The problem with supplying the protocol in the layer constructor is that you don't get the chance to call .read() yourself and the opportunity to provide your own callback to monitor the response because the layer does it for you.

So if you want to monitor the results you're going to have to create the layer and protocol separate so you can call the .read() whenever you click the "search" button for example. Then when you get the results you add those features to the layer newEventLayer.addFeatures(resp.features);

var newEventLayer = new OpenLayers.Layer.Vector('test');
map.addLayer(newEventLayer);
var protocol = new OpenLayers.Protocol.WFS({
    version: "1.1.0",
    url: xxx,
    featurePrefix: xxx,
    featureType: xxx,
    featureNS: xxx,
    geometryName: xxx,
    defaultFilter: new OpenLayers.Filter.Logical({
        type: OpenLayers.Filter.Logical.AND,
        filters: getMyFilter()
    }),
    srsName: xxx
});

var response = protocol.read({
    maxFeatures: 100,
    callback: _CallBack
});

function _CallBack (resp) {
    newEventLayer.addFeatures(resp.features);
});

Update 2

Try this if _callBack is not called:

var _CallBack = function (resp) {
    newEventLayer.addFeatures(resp.features);
});
var response = protocol.read({
    maxFeatures: 100,
    callback: _CallBack
});

Filter Strategy

You are right, i have removed the strategy from the layer constructor. You are going to have to specify your filter separately or in the protocol constructor as I have it above. But you're going to have build a search filter anyway if you want to search your WFS service by attributes, date/time, etc. Or did you only want to rely on the BBox Strategy (give me EVERYTHING in the BBOX)? If so then just set up a filter for that and call the protocol.read() on the map extentchange event. After all, that's all the strategy does. But that's seperate question which I, or others can help you with.